> I just wanted to take a moment to step back from the code and
> take stock of where the whole application is at and see what
> we've got left to do before 1830 is "working" well enough to
> release for wider public consumption.
>
> Here's the things that I can see are left to do:
>
> 1. Fix tile rotation bug. Hex F20 (the double town north of
> NYC) doesn't allow all legal tile rotations.
Which tile does that apply to? I can't find any misfits here.
2. Add tile upgrade restrictions. Currently there's nothing
> stopping upgrading to green tiles before the first 3-train
> has been purchased.
> 3. Add private purchasing limits. Similar to #2, there's
> nothing stopping purchasing of privates before the first
> 3-train has been purchased.
> 4. Finish off the token playing UI. As we've discussed over
> the last day or two.
> 5. Finish token drawing code. Relies on #4. We currently only
> handle single tokens in a hex.
> 6. Add token blocking. We're not currently checking for space
> in a station before playing a token.
>
> I'm not sure what the status of the private company's special
> abilities are, so that's a possible #7.
This is done, except for the special token lays and the M&H/NYC swap.
> Right now route counting requires looking at the tooltips of
> each hex to see the city's value. While cumbersome, it's not
> something that needs fixing just yet.
Restricting tile lays to extend existing routes also depends on that.
However, I could pretty easily add a restriction that a new tile should
connect to some existing track, except on a home base.
Route determination is the biggest issue still left. Next year!
Erik.
|
