All reports
tashkalar_displayed reports
#36279: "Confusing behaviour with Void Summoner"
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.
Move 53: I summoned Void Summoner and then Gates of Oblivion. There were 2 different orientations from which the Gates could be summoned. The interface behaved oddly and a little confusingly--it first asked me to select a piece (only offering one common with highlighting); and then asked me to select another piece (a ring around the pattern, presumably to destroy). I'm not sure what the first selection was about.• What is your browser?
Google Chrome v89
Report history
15. Mar 2021 21:53 • nandblock • Bug has not been reproduced by delopers yet:
Possibly the interface could be improved simply by indicating WHY you're being asked to select a piece (e.g. to destroy, move, upgrade, etc).
15. Mar 2021 22:39 • Quinarbre • This suggestion has not been analyzed by delopers yet:
It has very little to do with Void Summoner actually.
Since you had two orientations for the Gate, you had to choose which "purple" piece to destroy (and then which "red" piece to destroy).
The prompts are very generic because the same code is run for a lot of distinct effects, if I begin writing different messages I'll lose a lot of code factoring (in a place where my code is already quite bloated). The colors of the highlighted squares are visual clues to what will happen to the selected pieces (red to destroy, blue to move, golden to place or upgrade, green to convert, black to downgrade).
Since you had two orientations for the Gate, you had to choose which "purple" piece to destroy (and then which "red" piece to destroy).
The prompts are very generic because the same code is run for a lot of distinct effects, if I begin writing different messages I'll lose a lot of code factoring (in a place where my code is already quite bloated). The colors of the highlighted squares are visual clues to what will happen to the selected pieces (red to destroy, blue to move, golden to place or upgrade, green to convert, black to downgrade).
15. Mar 2021 22:39 • Quinarbre • This suggestion has not been analyzed by delopers yet:
It has very little to do with Void Summoner actually.
Since you had two orientations for the Gate, you had to choose which "purple" piece to destroy (and then which "red" piece to destroy).
The prompts are very generic because the same code is run for a lot of distinct effects, if I begin writing different messages I'll lose a lot of code factoring (in a place where my code is already quite bloated). The colors of the highlighted squares are visual clues to what will happen to the selected pieces (red to destroy, blue to move, golden to place or upgrade, green to convert, black to downgrade).
Since you had two orientations for the Gate, you had to choose which "purple" piece to destroy (and then which "red" piece to destroy).
The prompts are very generic because the same code is run for a lot of distinct effects, if I begin writing different messages I'll lose a lot of code factoring (in a place where my code is already quite bloated). The colors of the highlighted squares are visual clues to what will happen to the selected pieces (red to destroy, blue to move, golden to place or upgrade, green to convert, black to downgrade).
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.
