-
Notifications
You must be signed in to change notification settings - Fork 0
/
TODO.txt
33 lines (33 loc) · 2.51 KB
/
TODO.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
- game.cpp: An end game screen should be created
- game.cpp: Restrict keyboard focus to the bounding rectangle of all possible bridge building points, not the map size
this allows maps containing 'islands' going outside the screen and covering the entire edge ("mainland")
or maybe just set that manually in the map, so I won't need to mess with generator giving noncentered maps, or level 1 having an edge
- game.cpp: The pop_welldone_kb message needs k_confirm named (and spaces to recenter it)
- game.cpp: I believe keybol <http://www.notdoppler.com/kingofbridges.php> is not the sole author of the original game.
This suspicion is mostly based on how the original King of Bridges puts all tutorials in the first five levels,
but the first five levels only need the 'right number of bridges' rule, and 'all must be connected' isn't needed until the 11th.
I want to know who this other author is, so I can provide proper credit.
- game.cpp: In-game level editor
- maps.cpp: Need to design some levels containing the new objects
generator isn't enough, I want a few mainlands
make sure to introduce the new objects in a reasonable way
ideally, there should be three new worlds with three tilesets; one can be sandy, fg5 can be same as fg0, and the last one is undecided
ideas:
- map where the entire edge is islands, interior is blank (which direction do they run?)
- map that's a checkerboard of islands, except the middle is a plus-shaped island
- map with only even-numbered bridges - maybe even only 2s
- map with a 7 in the middle, connecting to 4s and 5s at the edges
- solver.cpp: Implement hint system (remove all incorrect bridges?)
- solver.cpp: Maps should be considered unambiguous if all solutions have the same number of bridges between islands A and B,
to avoid handing out "this one is either 0 or 4" hints to people who know how generator works
for example, this map should be unambiguous
2 2
^ ^
to do that, make solver always move same-island-pair bridges up/left, if possible
only if both edges are straight, to avoid issues with L-shaped islands where the bridge in the hole must go the other way
alternatively, ban generator from creating maps where the situation shows up
alternatively, just leave it like this, generator will never be perfect
- resources/kbfocus.png: Needs to be redrawn
- resources/castle.png: Needs to be redrawn
- resources/reef.png: Needs to be redrawn, and applicable help messages adjusted
- ui-libretro.cpp: Should be created