the change from the first prototype to the second was technological, moving from canvas to pure css+html, with react below.
task #20 demands a lot of changes that may not be feasible after all, making the commitment to the task unpredictable. so another prototype is welcome, although with the lowest priority.
this issue is more of a project management one: to do wha's proposed in the title, first it may be necessary to move svg-related or major interface changes to another milestone, that must be created. with this, game features like online play, or even the easier ones, like time travel, can be moved to this new milestone as well, helping to downgrade their current priority.
then, left with what's really necessary to play the game, create new labels for the issues that must still be prioritized:
mechanics for the changes in game mechanics
interface for issues that may improve the game playability (and still be used in the next prototype) - the obvious candidate here is the implementation of the player tableau
and so on.
the change from the first prototype to the second was technological, moving from canvas to pure css+html, with react below.
task #20 demands a lot of changes that may not be feasible after all, making the commitment to the task unpredictable. so another prototype is welcome, although with the lowest priority.
this issue is more of a project management one: to do wha's proposed in the title, first it may be necessary to move svg-related or major interface changes to another milestone, that must be created. with this, game features like online play, or even the easier ones, like time travel, can be moved to this new milestone as well, helping to downgrade their current priority.
then, left with what's really necessary to play the game, create new labels for the issues that must still be prioritized: