Alla rapporter
Tash-Kalar rapporter
#36279: "Confusing behaviour with Void Summoner"
Vad handlar denna rapport om?
Vad hände? Välj från alternativen nedan
Förslag: Enligt min åsikt så skulle följande förbättra spelimplementationen mycket
Detaljerad beskrivning
• Vänligen förklara ditt förslag exakt och koncist så att det är så enkelt som möjligt att förstå vad du menar.
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.• Vad har du för webbläsare?
Google Chrome v89
Rapporthistorik
15 mar 2021 21:53 • nandblock • Buggen har inte kunnat återupprepas av utvecklarna än:
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 • Detta förslag har inte analyserats av utvecklarna ännu :
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 • Detta förslag har inte analyserats av utvecklarna ännu :
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).
Lägg till något till denna rapport
Lägg till här allt som verkar relevant för att reproducera det här felet eller förstå ditt förslag:
- Ett annat spelbords-ID / drag-ID
- Löste F5 problemet?
- Uppträdde problemet flera gånger? Varje gång? Slumpmässigt?
- Om du har en skärmdump av denna buggen (vilket är bra), så kan du använda Imgur.com för att ladda upp den och kopiera/klistra in länken här.
