From: Erik V. <eri...@hc...> - 2008-11-29 22:42:04
|
Stumbled on the bug I updated in City class when I was testing out placing a Token in 1851 for L&N on the 2nd City of L&N Home Hex. The code allowed it to happen, although the rules specifically state: No more than one Station Marker of any Corporation may be placed in any hex. Note, in 1851 it asks which city you want to place the token on BEFORE it then responds with "Tile {X} already has a base token of company {Y}". When it should really state this before it gives you a choice of cities. Sure. The goal is to gave the game engine select the hexes where tokens can be laid and pass that list to the UI. But that requires route awareness, which we don't yet have. It would be possible now to pass a list of all hexes with open cities, excluding ones that already have a token of the same company. So far I have thought we could better wait with setting limitations until we can do it right. Is there any 18xx Game that allows one company to place multiple Tokens/Stations on the same Hex? If so, there will need some more updates to accommodate. Yes, in 18EU separate stations (a.k.a. cities) on one hex may have tokens of the same company (Paris, Berlin, Vienna). [BTW in this game it is pretty clear that these slots do not represent separate cities but separate stations in one city. One reason why I prefer the term "station" above "city" for one or more connected token slots]. Also still see the ability for a Token to be placed on a hex that has "no tile" placed on it. Still the background color. In 1830 this should of course not be possible (except home tokens), but I doubt if this applies to all games. Some games have off-board (red) hexes with token slots. Many games have preprinted yellow, green or grey hexes with tokenable cities. In 1841 you can select any open token slot as a home base for a new (non-historic) company, even if it is an unconnected city on background colour. Too many exceptions IMHO. The problems you mention will disappear once we have routes. As long as we don't have route awareness players have to be honest in tile and token placement anyway. I'm not too much in favour of partial fixes unless these are generic and really simple. Erik. Mark On Sat, Nov 29, 2008 at 3:15 PM, Erik Vos <eri...@hc...> wrote: I have (finally) done the main remaining unimplemented 1830 feature: selecting the Erie home base while upgrading to green. To trigger the selection I could have written code to detect the need for it, but for now I have chosen to add a special attribute in TileSet.xml for the preprinted (while/yellow) tile -20. During the upgrade, the same request will pop up as already occurs when laying a token on a multi-station tile. This new feature requires some extra non-transient attributes of LayTile. Normally such an extension makes existing saved files unreadable, as these contain serialized versions of LayTile objects. This time I have tried to achieve backwards compatibility by writing special deserialization code in this class. It seems to work nicely. (Although Erie did not appear in the bug list, I tend to consider it as such, if only for justifying submitting this change during the new features freeze we now have...). Erik ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100 <http://moblin-contest.org/redirect.php?banner_id=100&url=/> &url=/ _______________________________________________ Rails-devel mailing list Rai...@li... https://lists.sourceforge.net/lists/listinfo/rails-devel |