Tutti i resoconti
Tash-Kalar resoconto
#36279: "Confusing behaviour with Void Summoner"
awaiting: Questo suggerimento non è stato ancora analizzato dagli sviluppatori
A che riguardo è la segnalazione?
Cos'è successo? Prego, seleziona tra le seguenti
Suggerimento: a mio parere, quanto di seguito migliorerebbe notevolmente l'implementazione del gioco
Descrizione dettagliata
• Spiega il tuo suggerimento in modo preciso e conciso in modo che sia il più semplice possibile per capire cosa intendi.
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.• Qual è il tuo browser?
Google Chrome v89
Storico dei resoconti
15 mar 2021 21:53 • nandblock • L'errore non è stato ancora riprodotto dagli sviluppatori:
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 • Questo suggerimento non è stato ancora analizzato dagli sviluppatori:
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 • Questo suggerimento non è stato ancora analizzato dagli sviluppatori:
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).
Aggiungi qualcosa a questo report
Aggiungi qui tutto ciò che sembra pertinente per riprodurre questo bug o capire il tuo suggerimento:
- Un altro ID tavolo / ID mossa
- F5 ha risolto il problema?
- Il problema si verifica spesso? Ogni volta? Casualmente?
- Se hai una schermata di questo errore (cosa buona e giusta), puoi usare Imgur.com per caricarla e fare copia/incolla del link qui.
