I posted this in the design help and did not get any help so I am assuming its a bug.
If an invisible piece is in the same location as a visible piece two undesirable behaviors can occur. I
If the visible counter is on top of the invisible counter, the owner of the invisible counter cannot access the invisible counter. Selecting the stack does not give access to the underlying invisible counter. Double clicking does not expand the stack and a ‘move fixed distance’ key will not move the piece. If the invisible piece is on top of the visible counter or later moved below the visible counter this does not occur.
The owner of the visible counter cannot move his piece with the mouse. Double clicking the visible piece does then allow him to move his piece (I assume because then he is not restricted by the invisible pieces restrictions). Also a ‘move fixed distance’ keystroke seems to always work also.
This appears to be an ‘ownership’ vs ‘invisible’ interaction where by the top counter on the stack is not offset to the invisible player and the stack is not expandable and on the non-visible side the invisible counter is selected in some way.
- Operating System: Windows
- CPU: ?
- Memory: ?
- Video Card: ?
- Vassal version. 3.1.15
- Java version. Get it here
- Vassal module name and version : Email me at pcoons&swbell.net with your email and I will enable access on google docs. Replace & with @ in emial address.
- See above