All reports
spaceempires_displayed reports
#72018: "Player should have option of moving Doomsday Machine when two colonies are equidistant"
acknowledged: Developers agree that it is a good idea and intend to work on it
What is this report about?
What happened ? Please select from below
Suggestion: in my opinion, the following would greatly improve the game implementation
Detailed description
-
• Please explain your suggestion precisely and concisely so that it's as easy as possible to understand what you mean.
See last sentence:
MOVEMENT GUIDELINES: DMs always move toward the closest
player colony. If two colonies are equidistant, then a DM will
always move toward the colony that is larger (in CPs). If more
than one equidistant colonies are the same size, then the DM will
move toward the colony that brings it closest to the player’s home
planet. If it is still tied, then it is the player’s choice. • What is your browser?
Google Chrome v105
Report history
17. Sep 2022 5:00 • NateGtrMan • Bug has not been reproduced by delopers yet:
Because both Orion and Rigel were two hexes away, both at 5 CP, and both equidistant from my Homeworld, I should have the option of which colony the Doomsday Machine should attack.
17. Sep 2022 22:52 • Lunalol • This suggestion has not been analyzed by delopers yet:
Not implemented, changed to suggestion.
19. Sep 2022 7:13 • NateGtrMan • This suggestion has not been analyzed by delopers yet:
I don't understand why this isn't considered a rules violation? The whole point of the rule is to allow players to know which colony the DM will attack, but in this implementation I didn't know. Again, the rule states "If it is still tied, then it is the player's choice."
I think it would be ok to lock in the choice when the DM has the choice and not allow the player to change their mind, though.
I think it would be ok to lock in the choice when the DM has the choice and not allow the player to change their mind, though.
26. Sep 2022 22:22 • Lunalol • Developers agree that it is a good idea and intend to work on it:
OK, you're right it is a RULE but I though it was not necessary to implement it (really time consuming to code that). But I should not change game.
So I let player vote and will ask Jim an advice.
So I let player vote and will ask Jim an advice.
Add something to this report
Please add here anything that seems relevant to reproduce this bug or understand your suggestion:
- Another table ID / move ID
- Did F5 solve the problem?
- Did the problem appears several time? Everytime? Randomly?
- If you have a screenshot of this bug (good practice), you can use Imgur.com to upload it and copy/paste the link here.
