|
rlm@7
|
1 #+TITLE: Best-First Search for Effective Pokemon Types
|
|
rlm@0
|
2 #+AUTHOR: Robert McIntyre & Dylan Holmes
|
|
rlm@0
|
3 #+EMAIL: rlm@mit.edu
|
|
rlm@7
|
4 #+description: Finding interesting pokemon type combinations through Best-First search in clojure.
|
|
rlm@10
|
5 #+keywords: Pokemon, clojure, best-first search, optimization
|
|
rlm@4
|
6 #+SETUPFILE: ../../aurellem/org/setup.org
|
|
rlm@4
|
7 #+INCLUDE: ../../aurellem/org/level-0.org
|
|
rlm@0
|
8
|
|
rlm@0
|
9 * The Pok\eacute{}mon Type System
|
|
rlm@0
|
10
|
|
rlm@0
|
11 The Pok\eacute{}mon type system consists of seventeen different
|
|
rlm@9
|
12 /types/ (Rock, Grass, Ice, Psychic, Ground, Bug, Flying, Fire,
|
|
rlm@9
|
13 Fighting, Dark, Dragon, Poison, Water, Ghost, Normal, Electric, and
|
|
rlm@9
|
14 Steel) that interact like an extended version of Rock-Paper-Scissors:
|
|
rlm@9
|
15 for example, the Fire type is strong against the Grass type but weak
|
|
rlm@9
|
16 against the Water type. In the table below, we've recorded the
|
|
rlm@9
|
17 relative strengths of each of the types in the Pok\eacute{}mon type
|
|
rlm@9
|
18 system; the number in each cell indicates how effective an attack of
|
|
rlm@9
|
19 the type in the row is against a Pok\eacute{}mon of the type in the
|
|
rlm@9
|
20 column. We call these numbers /susceptibilities/.
|
|
rlm@0
|
21
|
|
rlm@0
|
22 In the Pok\eacute{}mon games, only four susceptibility values (two,
|
|
rlm@0
|
23 one, one-half, and zero) occur. These numbers indicate particularly
|
|
rlm@0
|
24 high susceptibility, average susceptibility, particularly low
|
|
rlm@5
|
25 susceptibility, and no susceptibility (immunity).
|
|
rlm@0
|
26
|
|
rlm@10
|
27 - The susceptibility of Flying types /against/ Ground is 0, because Ground
|
|
rlm@5
|
28 attacks cannot hurt Flying pok\eacute{}mon at all. The damage that
|
|
rlm@5
|
29 a Ground type attack normally does is /multiplied/ by 0 when it is
|
|
rlm@10
|
30 used against a Flying type pok\eacute{}mon.
|
|
rlm@0
|
31
|
|
rlm@10
|
32 - The susceptibility of Fire types against Water attacks
|
|
rlm@5
|
33 is 2, because Water type attacks are strong against Fire type
|
|
rlm@5
|
34 Pok\eacute{}mon. The damage that a Water type attack normally does
|
|
rlm@5
|
35 is doubled when it is used against a Fire type pok\eacute{}mon.
|
|
rlm@0
|
36
|
|
rlm@10
|
37 - The susceptibility of Water types against Water attacks is
|
|
rlm@5
|
38 $\frac{1}{2}$, because Water type attacks are strong against Water
|
|
rlm@5
|
39 type Pok\eacute{}mon. The damage that a Water type attack normally
|
|
rlm@5
|
40 does is halved when it is used against a Water type
|
|
rlm@5
|
41 pok\eacute{}mon.
|
|
rlm@5
|
42
|
|
rlm@5
|
43 There are two pok\eacute{}mon type systems in use. The first is the
|
|
rlm@5
|
44 classic system which was used for the very first pok\eacute{}mon
|
|
rlm@5
|
45 games, Red, Yellow, and Blue. This old system was used from 1998 to
|
|
rlm@5
|
46 2000 in America, and is known as the /Generation I Type System/. The
|
|
rlm@5
|
47 modern pok\eacute{}mon type system was introduced in 2000 with the
|
|
rlm@5
|
48 introduction of pok\eacute{}mon Gold and Silver, and has been in use
|
|
rlm@5
|
49 ever since. It is called the /Generation II Type System/.
|
|
rlm@5
|
50
|
|
rlm@9
|
51 The definitions of the two Type Systems are included below.
|
|
rlm@5
|
52
|
|
rlm@7
|
53 * Generation I and II Type System Data
|
|
rlm@0
|
54
|
|
rlm@6
|
55 ** Generation II Type System
|
|
rlm@0
|
56 #+label: pokemon-matchups
|
|
rlm@0
|
57 #+tblname: pokemon-table-gen-two
|
|
rlm@0
|
58 | | normal | fire | water | electric | grass | ice | fighting | poison | ground | flying | psychic | bug | rock | ghost | dragon | dark | steel |
|
|
rlm@0
|
59 |----------+--------+------+-------+----------+-------+-----+----------+--------+--------+--------+---------+-----+------+-------+--------+------+-------|
|
|
rlm@0
|
60 | normal | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | .5 | 0 | 1 | 1 | .5 |
|
|
rlm@0
|
61 | fire | 1 | .5 | .5 | 1 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 2 | .5 | 1 | .5 | 1 | 2 |
|
|
rlm@0
|
62 | water | 1 | 2 | .5 | 1 | .5 | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 2 | 1 | .5 | 1 | 1 |
|
|
rlm@0
|
63 | electric | 1 | 1 | 2 | .5 | .5 | 1 | 1 | 1 | 0 | 2 | 1 | 1 | 1 | 1 | .5 | 1 | 1 |
|
|
rlm@0
|
64 | grass | 1 | .5 | 2 | 1 | .5 | 1 | 1 | .5 | 2 | .5 | 1 | .5 | 2 | 1 | .5 | 1 | .5 |
|
|
rlm@0
|
65 | ice | 1 | .5 | .5 | 1 | 2 | .5 | 1 | 1 | 2 | 2 | 1 | 1 | 1 | 1 | 2 | 1 | .5 |
|
|
rlm@0
|
66 | fighting | 2 | 1 | 1 | 1 | 1 | 2 | 1 | .5 | 1 | .5 | .5 | .5 | 2 | 0 | 1 | 2 | 2 |
|
|
rlm@0
|
67 | poison | 1 | 1 | 1 | 1 | 2 | 1 | 1 | .5 | .5 | 1 | 1 | 1 | .5 | .5 | 1 | 1 | 0 |
|
|
rlm@0
|
68 | ground | 1 | 2 | 1 | 2 | .5 | 1 | 1 | 2 | 1 | 0 | 1 | .5 | 2 | 1 | 1 | 1 | 2 |
|
|
rlm@0
|
69 | flying | 1 | 1 | 1 | .5 | 2 | 1 | 2 | 1 | 1 | 1 | 1 | 2 | .5 | 1 | 1 | 1 | .5 |
|
|
rlm@0
|
70 | psychic | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 1 | 1 | .5 | 1 | 1 | 1 | 1 | 0 | .5 |
|
|
rlm@0
|
71 | bug | 1 | .5 | 1 | 1 | 2 | 1 | .5 | .5 | 1 | .5 | 2 | 1 | 1 | .5 | 1 | 2 | .5 |
|
|
rlm@0
|
72 | rock | 1 | 2 | 1 | 1 | 1 | 2 | .5 | 1 | .5 | 2 | 1 | 2 | 1 | 1 | 1 | 1 | .5 |
|
|
rlm@0
|
73 | ghost | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 2 | 1 | .5 | .5 |
|
|
rlm@0
|
74 | dragon | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | .5 |
|
|
rlm@0
|
75 | dark | 1 | 1 | 1 | 1 | 1 | 1 | .5 | 1 | 1 | 1 | 2 | 1 | 1 | 2 | 1 | .5 | .5 |
|
|
rlm@0
|
76 | steel | 1 | .5 | .5 | .5 | 1 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 1 | .5 |
|
|
rlm@0
|
77
|
|
rlm@6
|
78 The rows are attack types, while the columns are defense types. To
|
|
rlm@8
|
79 see the multiplier for a pok\eacute{}mon attack against a certain type, follow
|
|
rlm@6
|
80 the row for the attack type to the column of the defending type.
|
|
rlm@6
|
81
|
|
rlm@6
|
82 ** Generation I Type System
|
|
rlm@7
|
83 #+label: pokemon-matchups-gen-1
|
|
rlm@7
|
84 #+tblname: pokemon-table-gen-one
|
|
rlm@0
|
85 | | normal | fire | water | electric | grass | ice | fighting | poison | ground | flying | psychic | bug | rock | ghost | dragon |
|
|
rlm@0
|
86 |----------+--------+------+-------+----------+-------+-----+----------+--------+--------+--------+---------+-----+------+-------+--------|
|
|
rlm@0
|
87 | normal | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | .5 | 0 | 1 |
|
|
rlm@0
|
88 | fire | 1 | .5 | .5 | 1 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 2 | .5 | 1 | .5 |
|
|
rlm@0
|
89 | water | 1 | 2 | .5 | 1 | .5 | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 2 | 1 | .5 |
|
|
rlm@0
|
90 | electric | 1 | 1 | 2 | .5 | .5 | 1 | 1 | 1 | 0 | 2 | 1 | 1 | 1 | 1 | .5 |
|
|
rlm@0
|
91 | grass | 1 | .5 | 2 | 1 | .5 | 1 | 1 | .5 | 2 | .5 | 1 | .5 | 2 | 1 | .5 |
|
|
rlm@0
|
92 | ice | 1 | 1 | .5 | 1 | 2 | .5 | 1 | 1 | 2 | 2 | 1 | 1 | 1 | 1 | 2 |
|
|
rlm@0
|
93 | fighting | 2 | 1 | 1 | 1 | 1 | 2 | 1 | .5 | 1 | .5 | .5 | .5 | 2 | 0 | 1 |
|
|
rlm@0
|
94 | poison | 1 | 1 | 1 | 1 | 2 | 1 | 1 | .5 | .5 | 1 | 1 | 2 | .5 | .5 | 1 |
|
|
rlm@0
|
95 | ground | 1 | 2 | 1 | 2 | .5 | 1 | 1 | 2 | 1 | 0 | 1 | .5 | 2 | 1 | 1 |
|
|
rlm@0
|
96 | flying | 1 | 1 | 1 | .5 | 2 | 1 | 2 | 1 | 1 | 1 | 1 | 2 | .5 | 1 | 1 |
|
|
rlm@0
|
97 | psychic | 1 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 1 | 1 | .5 | 1 | 1 | 1 | 1 |
|
|
rlm@0
|
98 | bug | 1 | .5 | 1 | 1 | 2 | 1 | .5 | 2 | 1 | .5 | 2 | 1 | 1 | 0 | 1 |
|
|
rlm@0
|
99 | rock | 1 | 2 | 1 | 1 | 1 | 2 | .5 | 1 | .5 | 2 | 1 | 2 | 1 | 1 | 1 |
|
|
rlm@0
|
100 | ghost | 0 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 0 | 1 | 1 | 2 | 1 |
|
|
rlm@0
|
101 | dragon | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 2 |
|
|
rlm@0
|
102
|
|
rlm@6
|
103
|
|
rlm@6
|
104 This is the old table from Generation I. The differences from
|
|
rlm@6
|
105 Generation II are:
|
|
rlm@7
|
106 - Dark and Steel types are missing (these were introduced in
|
|
rlm@7
|
107 Generation II).
|
|
rlm@7
|
108 - Bug is super-effective against Poison (not-very-effective in
|
|
rlm@7
|
109 Generation II).
|
|
rlm@7
|
110 - Poison is super-effective against Bug (normal in Generation II).
|
|
rlm@7
|
111 - Bug is regularly effective against Ghost (super-effective in
|
|
rlm@7
|
112 Generation II).
|
|
rlm@7
|
113 - Ice is normally effective against Fire, (not-very-effective in
|
|
rlm@6
|
114 Generation II).
|
|
rlm@9
|
115 - Ghost is completely ineffective against Psychic, even though the
|
|
rlm@9
|
116 pok\eacute{}mon anime ran [[http://bulbapedia.bulbagarden.net/wiki/EP022][a three-part series]] about how Ghost
|
|
rlm@9
|
117 pok\eacute{}mon are the best way to defeat Psychic pok\eacute{}mon,
|
|
rlm@9
|
118 and the Red, Blue, and Yellow games each have a character who
|
|
rlm@9
|
119 states "The only thing Psychic pok\eacute{}mon fear are Bugs and
|
|
rlm@10
|
120 Ghosts!" This is considered to be a programming glitch. Ghost is
|
|
rlm@9
|
121 super-effective against Psychic in Generation II.
|
|
rlm@6
|
122
|
|
rlm@0
|
123 * Representing the Data
|
|
rlm@0
|
124
|
|
rlm@7
|
125 After creating the Pok\eacute{}mon types namespace, we store the
|
|
rlm@7
|
126 tables of susceptibilities above in =pokemon-table-gen-one= and
|
|
rlm@0
|
127 =pokemon-table-gen-two=, each of which is a simple vector of
|
|
rlm@0
|
128 vectors. Because a vector of vectors can be cumbersome, we do not
|
|
rlm@0
|
129 access the tables directly; instead, we use the derivative structures
|
|
rlm@0
|
130 =attack-strengths= and =defense-strengths=, which are functions which
|
|
rlm@0
|
131 return hash-maps associating each row (respectively column) of the
|
|
rlm@0
|
132 table with its corresponding Pok\eacute{}mon type.
|
|
rlm@0
|
133
|
|
rlm@0
|
134
|
|
rlm@0
|
135 #+srcname: header
|
|
rlm@0
|
136 #+begin_src clojure :results silent
|
|
rlm@0
|
137 (ns pokemon.types
|
|
rlm@7
|
138 (:use clojure.set)
|
|
rlm@7
|
139 (:use clojure.contrib.combinatorics)
|
|
rlm@7
|
140 (:use clojure.contrib.math)
|
|
rlm@7
|
141 (:use clojure.contrib.def)
|
|
rlm@13
|
142 (:use rlm.rlm-commands)
|
|
rlm@13
|
143 (:require rlm.map-utils))
|
|
rlm@0
|
144 #+end_src
|
|
rlm@0
|
145
|
|
rlm@7
|
146 #+srcname: data
|
|
rlm@0
|
147 #+begin_src clojure :results silent
|
|
rlm@0
|
148 (in-ns 'pokemon.types)
|
|
rlm@0
|
149 ;; record type strengths as a vector of vectors
|
|
rlm@7
|
150 ;; the variables pokemon-table-gen-one and pokemon-table-gen-two
|
|
rlm@7
|
151 ;; are replaced with the tables above when this file is tangled.
|
|
rlm@0
|
152 (def pokemon-gen-one pokemon-table-gen-one)
|
|
rlm@0
|
153 (def pokemon-gen-two pokemon-table-gen-two)
|
|
rlm@0
|
154
|
|
rlm@0
|
155 (defn type-names [] (vec (doall (map (comp keyword first) pokemon-gen-two))))
|
|
rlm@0
|
156
|
|
rlm@0
|
157 (defn attack-strengths []
|
|
rlm@0
|
158 (zipmap
|
|
rlm@0
|
159 (type-names)
|
|
rlm@0
|
160 (map (comp vec rest) pokemon-gen-two)))
|
|
rlm@0
|
161
|
|
rlm@0
|
162 (defn defense-strengths []
|
|
rlm@0
|
163 (zipmap (type-names)
|
|
rlm@0
|
164 (map
|
|
rlm@0
|
165 (apply juxt (map (attack-strengths) (type-names)))
|
|
rlm@0
|
166 (range (count (type-names))))))
|
|
rlm@0
|
167 #+end_src
|
|
rlm@0
|
168
|
|
rlm@7
|
169 The two statements
|
|
rlm@7
|
170
|
|
rlm@7
|
171 #+begin_src clojure :exports code
|
|
rlm@7
|
172 (def pokemon-gen-one pokemon-table-gen-one)
|
|
rlm@7
|
173 (def pokemon-gen-two pokemon-table-gen-two)
|
|
rlm@7
|
174 #+end_src
|
|
rlm@7
|
175
|
|
rlm@7
|
176 probably look weird. When the actual source file is created, those
|
|
rlm@7
|
177 variables are replaced with the data from the tables above.
|
|
rlm@7
|
178
|
|
rlm@7
|
179 See [[../src/pokemon/types.clj][types.clj]] to look at the final tangled output.
|
|
rlm@7
|
180
|
|
rlm@7
|
181
|
|
rlm@0
|
182 #+begin_src clojure :results output :exports both
|
|
rlm@0
|
183 (clojure.pprint/pprint pokemon.types/pokemon-gen-two)
|
|
rlm@0
|
184 #+end_src
|
|
rlm@0
|
185
|
|
rlm@0
|
186 #+results:
|
|
rlm@0
|
187 #+begin_example
|
|
rlm@0
|
188 (("normal" 1 1 1 1 1 1 1 1 1 1 1 1 0.5 0 1 1 0.5)
|
|
rlm@0
|
189 ("fire" 1 0.5 0.5 1 2 2 1 1 1 1 1 2 0.5 1 0.5 1 2)
|
|
rlm@0
|
190 ("water" 1 2 0.5 1 0.5 1 1 1 2 1 1 1 2 1 0.5 1 1)
|
|
rlm@0
|
191 ("electric" 1 1 2 0.5 0.5 1 1 1 0 2 1 1 1 1 0.5 1 1)
|
|
rlm@0
|
192 ("grass" 1 0.5 2 1 0.5 1 1 0.5 2 0.5 1 0.5 2 1 0.5 1 0.5)
|
|
rlm@0
|
193 ("ice" 1 0.5 0.5 1 2 0.5 1 1 2 2 1 1 1 1 2 1 0.5)
|
|
rlm@0
|
194 ("fighting" 2 1 1 1 1 2 1 0.5 1 0.5 0.5 0.5 2 0 1 2 2)
|
|
rlm@0
|
195 ("poison" 1 1 1 1 2 1 1 0.5 0.5 1 1 1 0.5 0.5 1 1 0)
|
|
rlm@0
|
196 ("ground" 1 2 1 2 0.5 1 1 2 1 0 1 0.5 2 1 1 1 2)
|
|
rlm@0
|
197 ("flying" 1 1 1 0.5 2 1 2 1 1 1 1 2 0.5 1 1 1 0.5)
|
|
rlm@0
|
198 ("psychic" 1 1 1 1 1 1 2 2 1 1 0.5 1 1 1 1 0 0.5)
|
|
rlm@0
|
199 ("bug" 1 0.5 1 1 2 1 0.5 0.5 1 0.5 2 1 1 0.5 1 2 0.5)
|
|
rlm@0
|
200 ("rock" 1 2 1 1 1 2 0.5 1 0.5 2 1 2 1 1 1 1 0.5)
|
|
rlm@0
|
201 ("ghost" 0 1 1 1 1 1 1 1 1 1 2 1 1 2 1 0.5 0.5)
|
|
rlm@0
|
202 ("dragon" 1 1 1 1 1 1 1 1 1 1 1 1 1 1 2 1 0.5)
|
|
rlm@0
|
203 ("dark" 1 1 1 1 1 1 0.5 1 1 1 2 1 1 2 1 0.5 0.5)
|
|
rlm@0
|
204 ("steel" 1 0.5 0.5 0.5 1 2 1 1 1 1 1 1 2 1 1 1 0.5))
|
|
rlm@0
|
205 #+end_example
|
|
rlm@0
|
206
|
|
rlm@7
|
207 =pokemon-gen-two= is a simple list-of-lists data structure.
|
|
rlm@0
|
208
|
|
rlm@0
|
209 #+begin_src clojure :results output :exports both
|
|
rlm@0
|
210 (clojure.pprint/pprint (pokemon.types/defense-strengths))
|
|
rlm@0
|
211 #+end_src
|
|
rlm@0
|
212
|
|
rlm@0
|
213 #+results:
|
|
rlm@0
|
214 #+begin_example
|
|
rlm@0
|
215 {:water [1 0.5 0.5 2 2 0.5 1 1 1 1 1 1 1 1 1 1 0.5],
|
|
rlm@0
|
216 :psychic [1 1 1 1 1 1 0.5 1 1 1 0.5 2 1 2 1 2 1],
|
|
rlm@0
|
217 :dragon [1 0.5 0.5 0.5 0.5 2 1 1 1 1 1 1 1 1 2 1 1],
|
|
rlm@0
|
218 :fire [1 0.5 2 1 0.5 0.5 1 1 2 1 1 0.5 2 1 1 1 0.5],
|
|
rlm@0
|
219 :ice [1 2 1 1 1 0.5 2 1 1 1 1 1 2 1 1 1 2],
|
|
rlm@0
|
220 :grass [1 2 0.5 0.5 0.5 2 1 2 0.5 2 1 2 1 1 1 1 1],
|
|
rlm@0
|
221 :ghost [0 1 1 1 1 1 0 0.5 1 1 1 0.5 1 2 1 2 1],
|
|
rlm@0
|
222 :poison [1 1 1 1 0.5 1 0.5 0.5 2 1 2 0.5 1 1 1 1 1],
|
|
rlm@0
|
223 :flying [1 1 1 2 0.5 2 0.5 1 0 1 1 0.5 2 1 1 1 1],
|
|
rlm@0
|
224 :normal [1 1 1 1 1 1 2 1 1 1 1 1 1 0 1 1 1],
|
|
rlm@0
|
225 :rock [0.5 0.5 2 1 2 1 2 0.5 2 0.5 1 1 1 1 1 1 2],
|
|
rlm@0
|
226 :electric [1 1 1 0.5 1 1 1 1 2 0.5 1 1 1 1 1 1 0.5],
|
|
rlm@0
|
227 :ground [1 1 2 0 2 2 1 0.5 1 1 1 1 0.5 1 1 1 1],
|
|
rlm@0
|
228 :fighting [1 1 1 1 1 1 1 1 1 2 2 0.5 0.5 1 1 0.5 1],
|
|
rlm@0
|
229 :dark [1 1 1 1 1 1 2 1 1 1 0 2 1 0.5 1 0.5 1],
|
|
rlm@0
|
230 :steel [0.5 2 1 1 0.5 0.5 2 0 2 0.5 0.5 0.5 0.5 0.5 0.5 0.5 0.5],
|
|
rlm@0
|
231 :bug [1 2 1 1 0.5 1 0.5 1 0.5 2 1 1 2 1 1 1 1]}
|
|
rlm@0
|
232 #+end_example
|
|
rlm@0
|
233
|
|
rlm@7
|
234 =defense-strengths= is a more convenient form of =pokemon-gen-two=,
|
|
rlm@7
|
235 with key/value pair access.
|
|
rlm@0
|
236
|
|
rlm@0
|
237 * Interfacing with the Data
|
|
rlm@7
|
238
|
|
rlm@7
|
239 In the pok\eacute{}mon games, a pok\eacute{}mon can have up to two
|
|
rlm@9
|
240 types at the same time. For example, [[http://bulbapedia.bulbagarden.net/wiki/Zapdos][Zapdos]], the fearsome legendary
|
|
rlm@9
|
241 bird that can control lightning, has both the Electric and Flying
|
|
rlm@9
|
242 types. A pok\eacute{}mon with more than one type gains the advantages
|
|
rlm@10
|
243 and disadvantages of both types. The susceptibilities of each type are
|
|
rlm@7
|
244 multiplied together to produce the hybrid type's susceptibilities. For
|
|
rlm@7
|
245 example, Electric is weak to Ground (susceptibility of 2), but Flying
|
|
rlm@10
|
246 is immune to Ground (susceptibility of 0). [[http://bulbapedia.bulbagarden.net/wiki/Zapdos][Zapdos']] type,
|
|
rlm@10
|
247 Electric/Flying, is immune to Ground because $2 \times 0 = 0$.
|
|
rlm@7
|
248
|
|
rlm@0
|
249 #+srcname: types
|
|
rlm@0
|
250 #+begin_src clojure :results silent
|
|
rlm@0
|
251 (in-ns 'pokemon.types)
|
|
rlm@0
|
252
|
|
rlm@0
|
253 (defn multitypes "All combinations of up to n types" [n]
|
|
rlm@0
|
254 (vec
|
|
rlm@0
|
255 (map vec
|
|
rlm@0
|
256 (reduce concat
|
|
rlm@0
|
257 (map (partial combinations (type-names))
|
|
rlm@0
|
258 (range 1 (inc n)))))))
|
|
rlm@0
|
259
|
|
rlm@7
|
260 (defn susceptibility
|
|
rlm@0
|
261 "Hash-map of the susceptibilities of the given type combination
|
|
rlm@0
|
262 to each type of attack"
|
|
rlm@0
|
263 [pkmn-types]
|
|
rlm@0
|
264 (rlm.map-utils/map-vals
|
|
rlm@0
|
265 clojure.core/rationalize
|
|
rlm@0
|
266 (apply hash-map
|
|
rlm@0
|
267 (interleave (type-names)
|
|
rlm@0
|
268 (apply (partial map *)
|
|
rlm@0
|
269 (map (defense-strengths) pkmn-types))))))
|
|
rlm@0
|
270
|
|
rlm@7
|
271 (defn susceptance
|
|
rlm@0
|
272 "The cumulative susceptibility of the given type combination"
|
|
rlm@0
|
273 [types]
|
|
rlm@7
|
274 (reduce + (map #(expt % 2) (vals (susceptibility types)))))
|
|
rlm@0
|
275 #+end_src
|
|
rlm@0
|
276
|
|
rlm@10
|
277 Now we can work out the susceptibility of [[http://bulbapedia.bulbagarden.net/wiki/Zapdos][Zapdos]] automatically.
|
|
rlm@7
|
278
|
|
rlm@7
|
279 Electric is weak to Ground.
|
|
rlm@7
|
280 #+begin_src clojure :exports both
|
|
rlm@7
|
281 (:ground (pokemon.types/susceptibility [:electric]))
|
|
rlm@7
|
282 #+end_src
|
|
rlm@7
|
283
|
|
rlm@7
|
284 #+results:
|
|
rlm@7
|
285 : 2
|
|
rlm@7
|
286
|
|
rlm@7
|
287 Flying is immune to Ground.
|
|
rlm@7
|
288 #+begin_src clojure :exports both
|
|
rlm@7
|
289 (:ground (pokemon.types/susceptibility [:flying]))
|
|
rlm@7
|
290 #+end_src
|
|
rlm@7
|
291
|
|
rlm@7
|
292 #+results:
|
|
rlm@7
|
293 : 0
|
|
rlm@7
|
294
|
|
rlm@7
|
295 Together, they are immune to Ground.
|
|
rlm@7
|
296 #+begin_src clojure :exports both
|
|
rlm@7
|
297 (:ground (pokemon.types/susceptibility [:electric :flying]))
|
|
rlm@7
|
298 #+end_src
|
|
rlm@7
|
299
|
|
rlm@7
|
300 #+results:
|
|
rlm@7
|
301 : 0
|
|
rlm@7
|
302
|
|
rlm@7
|
303
|
|
rlm@7
|
304
|
|
rlm@7
|
305
|
|
rlm@0
|
306 * Best-First Search
|
|
rlm@0
|
307
|
|
rlm@0
|
308 I'd like to find type combinations that are interesting, but the total
|
|
rlm@0
|
309 number of combinations gets huge as we begin to consider more
|
|
rlm@0
|
310 types. For example, the total possible number of type combinations
|
|
rlm@7
|
311 given just 8 possible types is: 17^{8} = 6,975,757,441 combinations.
|
|
rlm@0
|
312 Therefore, it's prudent to use search.
|
|
rlm@0
|
313
|
|
rlm@0
|
314 These functions are a simple implementation of best-first search in
|
|
rlm@15
|
315 clojure. The idea is to start off with a collection of nodes and some
|
|
rlm@15
|
316 way of finding the best node, and to always expand the best node at
|
|
rlm@15
|
317 every step.
|
|
rlm@0
|
318
|
|
rlm@0
|
319 #+srcname: search
|
|
rlm@0
|
320 #+begin_src clojure :results silent
|
|
rlm@0
|
321 (in-ns 'pokemon.types)
|
|
rlm@0
|
322
|
|
rlm@0
|
323 (defn comparatize
|
|
rlm@0
|
324 "Define a comparator which uses the numerical outputs of fn as its criterion.
|
|
rlm@0
|
325 Objects are sorted in increasing numerical order. Objects with the same fn-value
|
|
rlm@0
|
326 are further compared by clojure.core/compare."
|
|
rlm@0
|
327 [fun]
|
|
rlm@0
|
328 (fn [a b]
|
|
rlm@0
|
329 (let [val-a (fun a)
|
|
rlm@0
|
330 val-b (fun b)]
|
|
rlm@0
|
331 (cond
|
|
rlm@0
|
332 ;; if the function cannot differentiate the two values
|
|
rlm@0
|
333 ;; then compare the two values using clojure.core/compare
|
|
rlm@0
|
334 (= val-a val-b) (compare a b)
|
|
rlm@0
|
335 true
|
|
rlm@0
|
336 ;; LOWER values of the function are preferred
|
|
rlm@0
|
337 (compare (- val-a val-b) 0)))))
|
|
rlm@0
|
338
|
|
rlm@0
|
339 (defn-memo best-first-step [successors [visited unvisited]]
|
|
rlm@0
|
340 (cond (empty? unvisited) nil
|
|
rlm@0
|
341 true
|
|
rlm@0
|
342 (let [best-node (first unvisited)
|
|
rlm@0
|
343 visited* (conj visited best-node)
|
|
rlm@0
|
344 unvisited*
|
|
rlm@0
|
345 (difference
|
|
rlm@0
|
346 (union unvisited (set (successors best-node)))
|
|
rlm@0
|
347 visited*)]
|
|
rlm@0
|
348 (println best-node)
|
|
rlm@0
|
349 [visited* unvisited*])))
|
|
rlm@0
|
350
|
|
rlm@0
|
351 ;; memoize partial from core so that for example
|
|
rlm@0
|
352 ;; (= (partial + 1) (partial + 1))
|
|
rlm@0
|
353 ;; this way, best first search can take advantage of the memoization
|
|
rlm@0
|
354 ;; of best-first step
|
|
rlm@0
|
355 (undef partial)
|
|
rlm@0
|
356 (def partial (memoize clojure.core/partial))
|
|
rlm@0
|
357
|
|
rlm@0
|
358 (defn best-first-search
|
|
rlm@0
|
359 "Searches through a network of alternatives, pursuing
|
|
rlm@0
|
360 initially-promising positions first. Comparator defines which
|
|
rlm@0
|
361 positions are more promising, successors produces a list of improved
|
|
rlm@0
|
362 positions from the given position (if any exist), and initial-nodes is
|
|
rlm@0
|
363 a list of starting positions. Returns a lazy sequence of search results
|
|
rlm@0
|
364 [visited-nodes unvisited-nodes], which terminates when
|
|
rlm@0
|
365 there are no remaining unvisited positions."
|
|
rlm@0
|
366 [comparator successors initial-nodes]
|
|
rlm@0
|
367 (let [initial-nodes
|
|
rlm@0
|
368 (apply (partial sorted-set-by comparator) initial-nodes)
|
|
rlm@0
|
369 initial-visited-nodes (sorted-set-by comparator)
|
|
rlm@0
|
370 step (partial best-first-step successors)]
|
|
rlm@0
|
371 (take-while
|
|
rlm@0
|
372 (comp not nil?)
|
|
rlm@0
|
373 (iterate step [initial-visited-nodes initial-nodes]))))
|
|
rlm@0
|
374
|
|
rlm@0
|
375 #+end_src
|
|
rlm@0
|
376
|
|
rlm@0
|
377
|
|
rlm@0
|
378 Now that we have a basic best-first-search, it's convenient to write a
|
|
rlm@8
|
379 few pok\eacute{}mon-type specific convenience functions.
|
|
rlm@0
|
380
|
|
rlm@0
|
381 #+srcname: pokemon-search
|
|
rlm@0
|
382 #+begin_src clojure :results silent
|
|
rlm@0
|
383 (in-ns 'pokemon.types)
|
|
rlm@0
|
384 (defvar type-compare (comparatize susceptance)
|
|
rlm@10
|
385 "compare two type combinations W.R.T. their susceptibilities")
|
|
rlm@0
|
386
|
|
rlm@0
|
387 (defn type-successors
|
|
rlm@0
|
388 "Return the set of types that can be made by appending a single type
|
|
rlm@0
|
389 to the given combination."
|
|
rlm@0
|
390 [type]
|
|
rlm@0
|
391 (if (nil? type) '()
|
|
rlm@0
|
392 (set (map (comp vec sort (partial into type)) (multitypes 1)))))
|
|
rlm@0
|
393
|
|
rlm@0
|
394 (defn immortal?
|
|
rlm@0
|
395 "A type combo is immortal if it is resistant or invulnerable to
|
|
rlm@0
|
396 every pokemon type. This is because that set of types can just be
|
|
rlm@0
|
397 repeated to achieve as low a susceptance as desired"
|
|
rlm@0
|
398 [type]
|
|
rlm@0
|
399 (every? (partial > 1) (vals (susceptibility type))))
|
|
rlm@0
|
400
|
|
rlm@0
|
401 (defn type-successors*
|
|
rlm@0
|
402 "Stop expanding a type if it's immortal, or if it is longer than or
|
|
rlm@0
|
403 equal to limit-size. Also, only return type additions that are
|
|
rlm@0
|
404 strictly better than the initial type."
|
|
rlm@0
|
405 [limit-size type]
|
|
rlm@0
|
406 (if (or (<= limit-size (count type)) (immortal? type)) '()
|
|
rlm@0
|
407 (set (filter #(< 0 (type-compare type %)) (type-successors type)))))
|
|
rlm@0
|
408
|
|
rlm@0
|
409 (defn pokemon-type-search
|
|
rlm@0
|
410 "Search among type-combos no greater than length n, limited by limit
|
|
rlm@0
|
411 steps of best-first-search."
|
|
rlm@0
|
412 ([n] (pokemon-type-search n Integer/MAX_VALUE))
|
|
rlm@0
|
413 ([n limit]
|
|
rlm@0
|
414 (first (last
|
|
rlm@0
|
415 (take
|
|
rlm@0
|
416 limit
|
|
rlm@0
|
417 (best-first-search
|
|
rlm@0
|
418 type-compare
|
|
rlm@0
|
419 (partial type-successors* n)
|
|
rlm@0
|
420 (multitypes 1)))))))
|
|
rlm@0
|
421
|
|
rlm@0
|
422 (defvar immortals
|
|
rlm@0
|
423 (comp (partial filter immortal?) pokemon-type-search)
|
|
rlm@0
|
424 "find all the immortal pokemon types ")
|
|
rlm@0
|
425
|
|
rlm@0
|
426 #+end_src
|
|
rlm@0
|
427
|
|
rlm@0
|
428 Because there are so many type combinations, it's important to narrow
|
|
rlm@0
|
429 down the results as much as possible. That is why =type-successors*=
|
|
rlm@0
|
430 only returns types that are actually better than the type it is given.
|
|
rlm@0
|
431
|
|
rlm@0
|
432 Best-first search can get caught optimizing a single type forever, so
|
|
rlm@0
|
433 it's also important to limit the search space to be finite by setting
|
|
rlm@0
|
434 an upper bound on the length of a type combo.
|
|
rlm@0
|
435
|
|
rlm@0
|
436 * Results
|
|
rlm@0
|
437 ** The best dual-type combo
|
|
rlm@0
|
438
|
|
rlm@0
|
439 #+begin_src clojure :results cache verbatim :exports both
|
|
rlm@0
|
440 (first (pokemon.types/pokemon-type-search 2))
|
|
rlm@0
|
441 #+end_src
|
|
rlm@0
|
442
|
|
rlm@0
|
443 #+results:
|
|
rlm@0
|
444 : [:dark :ghost]
|
|
rlm@0
|
445
|
|
rlm@0
|
446 Dark and Ghost, which additionally has the property of having no
|
|
rlm@9
|
447 weaknesses to any other type, is the best type combo in terms of
|
|
rlm@9
|
448 susceptance.
|
|
rlm@0
|
449
|
|
rlm@0
|
450 The Dark and Steel types were introduced many years after
|
|
rlm@0
|
451 pok\eacute{}mon started. In addition to the additional types, the
|
|
rlm@0
|
452 pok\eacute{}mon games gained a few new rules concerning some of the
|
|
rlm@9
|
453 matchups of the original types. Therefore, it's also interesting to
|
|
rlm@9
|
454 see what type combination was most powerful before those types and new
|
|
rlm@9
|
455 rules were introduced.
|
|
rlm@0
|
456
|
|
rlm@0
|
457 The easiest way to do this with my setup is to just rebind the
|
|
rlm@0
|
458 =pokemon-gen-two= table to the =pokemon-gen-one= table. Since
|
|
rlm@0
|
459 everything that references this variable is a function and we're not
|
|
rlm@0
|
460 doing anything too crazy with lazy-sequences and late-binding, this
|
|
rlm@0
|
461 simple macro will do the job.
|
|
rlm@0
|
462
|
|
rlm@0
|
463 #+srcname: old-school
|
|
rlm@0
|
464 #+begin_src clojure :results silent
|
|
rlm@0
|
465 (in-ns 'pokemon.types)
|
|
rlm@0
|
466
|
|
rlm@0
|
467 (defmacro old-school
|
|
rlm@0
|
468 [& forms]
|
|
rlm@0
|
469 `(binding [pokemon-gen-two pokemon-gen-one] ~@forms))
|
|
rlm@0
|
470 #+end_src
|
|
rlm@0
|
471
|
|
rlm@0
|
472 Using the =old-school= macro, it's easy to find answers for the
|
|
rlm@0
|
473 original 15 pokemon types as well as the expanded pokemon types
|
|
rlm@0
|
474 introduced later.
|
|
rlm@0
|
475
|
|
rlm@0
|
476 #+begin_src clojure :results verbatim :exports both :cache yes
|
|
rlm@0
|
477 (pokemon.types/old-school (first (pokemon.types/pokemon-type-search 2)))
|
|
rlm@0
|
478 #+end_src
|
|
rlm@0
|
479
|
|
rlm@0
|
480 #+results[f43470fdf460ed546e9c57879abc9eda56da129f]:
|
|
rlm@0
|
481 : [:ghost :psychic]
|
|
rlm@0
|
482
|
|
rlm@0
|
483 Ghost and Psychic also manages to have no weaknesses to any of the original
|
|
rlm@8
|
484 types, using the old Generation I rules.
|
|
rlm@0
|
485
|
|
rlm@0
|
486 #+begin_src clojure :results output :exports both
|
|
rlm@0
|
487 (clojure.pprint/pprint
|
|
rlm@0
|
488 (pokemon.types/old-school
|
|
rlm@0
|
489 (pokemon.types/susceptibility [:ghost :psychic])))
|
|
rlm@0
|
490 #+end_src
|
|
rlm@0
|
491
|
|
rlm@0
|
492 #+results:
|
|
rlm@0
|
493 #+begin_example
|
|
rlm@0
|
494 {:water 1,
|
|
rlm@0
|
495 :psychic 1/2,
|
|
rlm@0
|
496 :dragon 1,
|
|
rlm@0
|
497 :fire 1,
|
|
rlm@0
|
498 :ice 1,
|
|
rlm@0
|
499 :grass 1,
|
|
rlm@0
|
500 :ghost 0,
|
|
rlm@0
|
501 :poison 1/2,
|
|
rlm@0
|
502 :flying 1,
|
|
rlm@0
|
503 :normal 0,
|
|
rlm@0
|
504 :rock 1,
|
|
rlm@0
|
505 :electric 1,
|
|
rlm@0
|
506 :ground 1,
|
|
rlm@0
|
507 :fighting 0,
|
|
rlm@0
|
508 :bug 0}
|
|
rlm@0
|
509 #+end_example
|
|
rlm@0
|
510
|
|
rlm@0
|
511 ** An Immortal Type
|
|
rlm@0
|
512 It's possible to quickly find an immortal type by giving the search
|
|
rlm@0
|
513 a long enough maximum type length. 50 rounds of search with a max
|
|
rlm@0
|
514 type limit of 10 is enough to find an immortal type.
|
|
rlm@0
|
515
|
|
rlm@0
|
516 #+begin_src clojure :results scalar :exports both
|
|
rlm@0
|
517 (first (pokemon.types/pokemon-type-search 10 50))
|
|
rlm@0
|
518 #+end_src
|
|
rlm@0
|
519
|
|
rlm@0
|
520 #+results:
|
|
rlm@0
|
521 : [:dragon :fire :flying :ghost :grass :ground :steel :steel :water :water]
|
|
rlm@0
|
522
|
|
rlm@0
|
523
|
|
rlm@0
|
524 #+begin_src clojure :results output :exports both
|
|
rlm@0
|
525 (clojure.pprint/pprint
|
|
rlm@0
|
526 (pokemon.types/susceptibility
|
|
rlm@0
|
527 [:dragon :fire :flying :ghost :grass :ground :steel :steel :water :water]))
|
|
rlm@0
|
528 #+end_src
|
|
rlm@0
|
529
|
|
rlm@0
|
530 #+results:
|
|
rlm@0
|
531 #+begin_example
|
|
rlm@0
|
532 {:water 1/4,
|
|
rlm@0
|
533 :psychic 1/4,
|
|
rlm@0
|
534 :dragon 1/2,
|
|
rlm@0
|
535 :fire 1/2,
|
|
rlm@0
|
536 :ice 1/2,
|
|
rlm@0
|
537 :grass 1/8,
|
|
rlm@0
|
538 :ghost 1/2,
|
|
rlm@0
|
539 :poison 0,
|
|
rlm@0
|
540 :flying 1/2,
|
|
rlm@0
|
541 :normal 0,
|
|
rlm@0
|
542 :rock 1/2,
|
|
rlm@0
|
543 :electric 0,
|
|
rlm@0
|
544 :ground 0,
|
|
rlm@0
|
545 :fighting 0,
|
|
rlm@0
|
546 :dark 1/2,
|
|
rlm@0
|
547 :steel 1/32,
|
|
rlm@0
|
548 :bug 1/16}
|
|
rlm@0
|
549 #+end_example
|
|
rlm@0
|
550
|
|
rlm@0
|
551 ** Explanations for Common Pok\eacute{}mon Strategies
|
|
rlm@0
|
552
|
|
rlm@8
|
553 Many people start out a battle with either a Normal pok\eacute{}mon or an
|
|
rlm@8
|
554 Electric pok\eacute{}mon. Here's some justification for that choice.
|
|
rlm@0
|
555
|
|
rlm@0
|
556 #+srcname: weaknesses
|
|
rlm@0
|
557 #+begin_src clojure :results silent
|
|
rlm@0
|
558 (in-ns 'pokemon.types)
|
|
rlm@0
|
559 (defn critical-weaknesses [type]
|
|
rlm@0
|
560 (count (filter #(> % 1) (vals (susceptibility type)))))
|
|
rlm@0
|
561 #+end_src
|
|
rlm@0
|
562
|
|
rlm@0
|
563 #+begin_src clojure :exports both :results output
|
|
rlm@0
|
564 (clojure.pprint/pprint
|
|
rlm@0
|
565 (sort-by pokemon.types/critical-weaknesses (pokemon.types/multitypes 1)))
|
|
rlm@0
|
566 #+end_src
|
|
rlm@0
|
567
|
|
rlm@0
|
568 #+results:
|
|
rlm@0
|
569 #+begin_example
|
|
rlm@0
|
570 ([:normal]
|
|
rlm@0
|
571 [:electric]
|
|
rlm@0
|
572 [:water]
|
|
rlm@0
|
573 [:fighting]
|
|
rlm@0
|
574 [:poison]
|
|
rlm@0
|
575 [:ghost]
|
|
rlm@0
|
576 [:dragon]
|
|
rlm@0
|
577 [:dark]
|
|
rlm@0
|
578 [:fire]
|
|
rlm@0
|
579 [:ground]
|
|
rlm@0
|
580 [:flying]
|
|
rlm@0
|
581 [:psychic]
|
|
rlm@0
|
582 [:bug]
|
|
rlm@0
|
583 [:steel]
|
|
rlm@0
|
584 [:ice]
|
|
rlm@0
|
585 [:grass]
|
|
rlm@0
|
586 [:rock])
|
|
rlm@0
|
587 #+end_example
|
|
rlm@0
|
588
|
|
rlm@0
|
589 Electric and Normal are among the best types with which to start the
|
|
rlm@0
|
590 game, since they have the fewest weaknesses among all the types.
|
|
rlm@0
|
591
|
|
rlm@9
|
592 At the beginning of the pok\eacute{}mon games, players are given a
|
|
rlm@9
|
593 choice between the Fire pok\eacute{}mon [[http://bulbapedia.bulbagarden.net/wiki/Charmander][Charmander]], the Water
|
|
rlm@9
|
594 pok\eacute{}mon [[http://bulbapedia.bulbagarden.net/wiki/Squirtle][Squirtle]], or the Grass/Poison pok\eacute{}mon
|
|
rlm@9
|
595 [[http://bulbapedia.bulbagarden.net/wiki/Bulbasaur][Bulbasaur]].
|
|
rlm@0
|
596
|
|
rlm@0
|
597 #+begin_src clojure :exports both :results verbatim
|
|
rlm@0
|
598 (sort-by pokemon.types/susceptance [[:fire] [:water] [:grass :poison]])
|
|
rlm@0
|
599 #+end_src
|
|
rlm@0
|
600
|
|
rlm@0
|
601 #+results:
|
|
rlm@0
|
602 : ([:water] [:fire] [:grass :poison])
|
|
rlm@0
|
603
|
|
rlm@9
|
604 As can be seen, the Water pok\eacute{}mon [[http://bulbapedia.bulbagarden.net/wiki/Squirtle][Squirtle]] is the most solid
|
|
rlm@0
|
605 choice starting out, insofar as susceptance is concerned.
|
|
rlm@0
|
606
|
|
rlm@0
|
607 ** The Worst Pok\eacute{}mon Types
|
|
rlm@0
|
608
|
|
rlm@0
|
609 #+srcname: weak-types
|
|
rlm@0
|
610 #+begin_src clojure :results silent
|
|
rlm@0
|
611 (in-ns 'pokemon.types)
|
|
rlm@0
|
612
|
|
rlm@0
|
613 (defn type-compare-weak
|
|
rlm@0
|
614 "compare first by total number of critical-weaknesses,
|
|
rlm@0
|
615 then by overall susceptance, favoring weaker types."
|
|
rlm@0
|
616 [type-1 type-2]
|
|
rlm@0
|
617 (let [measure (memoize (juxt critical-weaknesses susceptance))]
|
|
rlm@0
|
618 (if (= (measure type-2) (measure type-1))
|
|
rlm@0
|
619 (compare type-2 type-1)
|
|
rlm@0
|
620 (compare (measure type-2) (measure type-1)))))
|
|
rlm@0
|
621
|
|
rlm@0
|
622 (defn resistant?
|
|
rlm@0
|
623 "might as well get rid of types that are resistant to any type"
|
|
rlm@0
|
624 [type]
|
|
rlm@0
|
625 (not (every? #(< 0 %) (vals (susceptibility type)))))
|
|
rlm@0
|
626
|
|
rlm@0
|
627 (defn type-successors-weak
|
|
rlm@8
|
628 "Generate ways to weaken the given type combination. Discard type
|
|
rlm@8
|
629 combinations that either strengthen the given type combination or
|
|
rlm@8
|
630 that make it stronger"
|
|
rlm@0
|
631 [limit type]
|
|
rlm@0
|
632 (set (if (<= limit (count type)) '()
|
|
rlm@0
|
633 (filter #(< 0 (type-compare-weak type %))
|
|
rlm@0
|
634 (remove resistant? (type-successors type))))))
|
|
rlm@0
|
635
|
|
rlm@0
|
636 (defn pokemon-type-search-weak
|
|
rlm@0
|
637 "Search among type-combos no greater than length n, limited by limit
|
|
rlm@8
|
638 steps of best-first-search. Find the weakest type combination
|
|
rlm@8
|
639 possible in terms of susceptance."
|
|
rlm@0
|
640 ([n] (pokemon-type-search-weak n Integer/MAX_VALUE))
|
|
rlm@0
|
641 ([n limit]
|
|
rlm@0
|
642 (first (last
|
|
rlm@0
|
643 (take
|
|
rlm@0
|
644 limit
|
|
rlm@0
|
645 (best-first-search
|
|
rlm@0
|
646 type-compare-weak
|
|
rlm@0
|
647 (partial type-successors-weak n)
|
|
rlm@0
|
648 (multitypes 1)))))))
|
|
rlm@0
|
649 #+end_src
|
|
rlm@0
|
650
|
|
rlm@0
|
651
|
|
rlm@0
|
652 #+begin_src clojure :results scalar :exports both
|
|
rlm@0
|
653 (first (pokemon.types/pokemon-type-search-weak 1))
|
|
rlm@0
|
654 #+end_src
|
|
rlm@0
|
655
|
|
rlm@0
|
656 #+results:
|
|
rlm@0
|
657 : [:rock]
|
|
rlm@0
|
658
|
|
rlm@0
|
659 Poor Rock. It's just not that good a type. Maybe this is why Brock
|
|
rlm@0
|
660 (who has rock pok\eacute{}mon) is the first gym leader in the games.
|
|
rlm@0
|
661
|
|
rlm@0
|
662 #+begin_src clojure :results scalar cache :exports both
|
|
rlm@0
|
663 (first (pokemon.types/pokemon-type-search-weak 2))
|
|
rlm@0
|
664 #+end_src
|
|
rlm@0
|
665
|
|
rlm@0
|
666 #+results:
|
|
rlm@0
|
667 : [:grass :ice]
|
|
rlm@0
|
668
|
|
rlm@0
|
669 # ;;bonus convergently immortal type combo
|
|
rlm@0
|
670 # (susceptance (vec (concat (repeat 150 :water) (repeat 50 :poison) (repeat 50 :steel) [:ghost :normal :flying :ground :dark])))
|
|
rlm@0
|
671
|
|
rlm@0
|
672 #+begin_src clojure :results output :exports both
|
|
rlm@0
|
673 (clojure.pprint/pprint
|
|
rlm@0
|
674 (pokemon.types/susceptibility [:grass :ice]))
|
|
rlm@0
|
675 #+end_src
|
|
rlm@0
|
676
|
|
rlm@0
|
677 #+results:
|
|
rlm@0
|
678 #+begin_example
|
|
rlm@0
|
679 {:water 1/2,
|
|
rlm@0
|
680 :psychic 1,
|
|
rlm@0
|
681 :dragon 1,
|
|
rlm@0
|
682 :fire 4,
|
|
rlm@0
|
683 :ice 1,
|
|
rlm@0
|
684 :grass 1/2,
|
|
rlm@0
|
685 :ghost 1,
|
|
rlm@0
|
686 :poison 2,
|
|
rlm@0
|
687 :flying 2,
|
|
rlm@0
|
688 :normal 1,
|
|
rlm@0
|
689 :rock 2,
|
|
rlm@0
|
690 :electric 1/2,
|
|
rlm@0
|
691 :ground 1/2,
|
|
rlm@0
|
692 :fighting 2,
|
|
rlm@0
|
693 :dark 1,
|
|
rlm@0
|
694 :steel 2,
|
|
rlm@0
|
695 :bug 2}
|
|
rlm@0
|
696 #+end_example
|
|
rlm@0
|
697
|
|
rlm@0
|
698 This miserable combination is weak to 6 types and double-weak to
|
|
rlm@0
|
699 Fire. No pok\eacute{}mon in the games actually has this type.
|
|
rlm@0
|
700
|
|
rlm@0
|
701 * Conclusion
|
|
rlm@0
|
702
|
|
rlm@0
|
703 Searching for a type that is weak to everything takes a very long time
|
|
rlm@0
|
704 and fails to reveal any results. That's the problem with a search
|
|
rlm@0
|
705 over this large problem space --- if there's an easy solution, the
|
|
rlm@0
|
706 search will find it quickly, but it can be very hard to determine
|
|
rlm@0
|
707 whether there is actually a solution.
|
|
rlm@0
|
708
|
|
rlm@0
|
709 In the [[./lpsolve.org][next installment]], I'll use =lp_solve= to solve this problem in
|
|
rlm@0
|
710 a different way.
|
|
rlm@0
|
711
|
|
rlm@0
|
712 * COMMENT main program
|
|
rlm@0
|
713 #+begin_src clojure :noweb yes :tangle ../src/pokemon/types.clj :exports none
|
|
rlm@0
|
714 <<header>>
|
|
rlm@0
|
715 #+end_src
|
|
rlm@0
|
716
|
|
rlm@0
|
717 ## this is necessary to define pokemon-table inside the source code.
|
|
rlm@0
|
718
|
|
rlm@0
|
719 #+begin_src clojure :noweb yes :tangle ../src/pokemon/types.clj :var pokemon-table-gen-one=pokemon-table-gen-one :var pokemon-table-gen-two=pokemon-table-gen-two :exports none
|
|
rlm@0
|
720 <<data>>
|
|
rlm@0
|
721 #+end_src
|
|
rlm@0
|
722
|
|
rlm@0
|
723 #+begin_src clojure :noweb yes :tangle ../src/pokemon/types.clj :exports none
|
|
rlm@0
|
724 <<types>>
|
|
rlm@0
|
725 <<search>>
|
|
rlm@0
|
726 <<pokemon-search>>
|
|
rlm@0
|
727 <<old-school>>
|
|
rlm@0
|
728 <<weaknesses>>
|
|
rlm@0
|
729 <<weak-types>>
|
|
rlm@0
|
730 #+end_src
|
|
rlm@0
|
731
|
|
rlm@0
|
732
|
|
rlm@0
|
733
|
|
rlm@0
|
734
|
|
rlm@0
|
735
|
|
rlm@0
|
736
|
|
rlm@0
|
737
|
|
rlm@0
|
738
|
|
rlm@0
|
739
|
|
rlm@0
|
740
|
|
rlm@0
|
741
|
|
rlm@0
|
742
|
|
rlm@0
|
743
|
|
rlm@0
|
744
|
|
rlm@0
|
745
|
|
rlm@0
|
746
|
|
rlm@0
|
747
|
|
rlm@0
|
748
|
