03-05-2021, 11:33 AM
(This post was last modified: 03-05-2021, 11:41 AM by slimy_asparagus.)
(02-22-2021, 02:36 PM)Eric Piette Wrote: Talking about your description, I am not sure about why you are using waves pieces. That should be just something to do in the graphics and the waves pieces do not seem necessary for that game.
Okay I am ready to return to this issue. The basic mechanics of the game are in place and I just need to make sure I am conveying enough information to the users (without relying on "show legal moves" and "show last move" which I am doing at the moment).
For the home area, the player needs to know what the opponent hit (water or ship) and where. It does not affect game play but it is part of the experience: seeing how close they came, knowing how much you have left etc.
For the attack area, the player needs to know what he hit (water, ship, size of ship) and where. This does affect game play.
So I am proposing to use the waves svg for a miss and the rubble svg for a hit. This convention should work in both attack and defence areas so they are set up as sites are revealed.
If we really hold to the principle that I should not have Waves pieces, then I need a graphical meta-data way of saying place a waves symbol on an empty site if that site has such and such a state. I think it would be simpler to have a Shared Waves piece and simply place one in the event of a miss, but it does not matter to me.
To achieve the rubble I am trying to do the following
Code:
(piece Rename piece:"Carrier" "square" state:0)
(piece Rename piece:"Battleship" "square" state:0)
(piece Rename piece:"Destroyer" "square" state:0)
(piece Rename piece:"Submarine" "square" state:0)
(piece Rename piece:"PatrolBoat" "square" state:0)
(piece Rename piece:"Carrier" "rubble" state:("Hit"))
(piece Rename piece:"Battleship" "rubble" state:("Hit"))
(piece Rename piece:"Destroyer" "rubble" state:("Hit"))
(piece Rename piece:"Submarine" "rubble" state:("Hit"))
(piece Rename piece:"PatrolBoat" "rubble" state:("Hit"))