Scenario on small map
Posted: Sun Jul 18, 2010 8:30 am
Note:
There is alternate code that runs for small versus full map.
The Full Map code is triggered by the rightmost X hex 231 or lower most Y hex 204. This is simplistic and doesn't really count for maps that don't start at 0,0.
The Downfall scenario is triggering the full map code because it has the rightmost hex column defined as 231.
If using a small map, don't go for the extreme hex columns. If need you need to use the far right, use one hex less than the full width.
I suggest changing the map co-ordinates for Downfall to use 230 rather 231 to ensure that the proper code is used. What caused me to look at this was the 'go to home port' button, which stop of SF and would not go any further.
[edit]
I will change this next time to calculate the difference between the left and right X, and call it a full map is the difference is 231 (231-0). This way will treat less wide maps as small and the current Downfall co-ordinates (45,45) to (231,112) would be okay (231-45 < 231 = small).
There is alternate code that runs for small versus full map.
The Full Map code is triggered by the rightmost X hex 231 or lower most Y hex 204. This is simplistic and doesn't really count for maps that don't start at 0,0.
The Downfall scenario is triggering the full map code because it has the rightmost hex column defined as 231.
If using a small map, don't go for the extreme hex columns. If need you need to use the far right, use one hex less than the full width.
I suggest changing the map co-ordinates for Downfall to use 230 rather 231 to ensure that the proper code is used. What caused me to look at this was the 'go to home port' button, which stop of SF and would not go any further.
[edit]
I will change this next time to calculate the difference between the left and right X, and call it a full map is the difference is 231 (231-0). This way will treat less wide maps as small and the current Downfall co-ordinates (45,45) to (231,112) would be okay (231-45 < 231 = small).