Alle Meldungen
Diamant Meldungen
#48800: "Skip player choice to return to camp until at least one artifact or hazard is drawn"
awaiting: Dieser Vorschlag wurde von den Entwicklern noch nicht untersucht
Worum geht es bei dieser Meldung?
Was ist passiert? Bitte wähle unten aus
Vorschlag: meiner Meinung nach würde das Folgende die Umsetzung des Spiels erheblich verbessern
Detaillierte Beschreibung
• Bitte erkläre deinen Vorschlag so präzise und genau wie möglich, damit er leicht zu verstehen ist.
There is no reason to ask players whether they want to return to camp or not when there have been no artifacts or hazards drawn.
Example: if the first four draws in a round are all gem cards, all it does is postpone any actual gameplay by asking players whether they want to return to camp for each card drawn.
At the very least, add a toggle we can use for the option.• Welchen Browser benutzt du?
Google Chrome v91
Meldungshistorie
19. Sep 2021 16:10 • Tybus913 • Dieser Vorschlag wurde von den Entwicklern noch nicht untersucht:
N/A
21. Sep 2021 15:27 • Tybus913 • Dieser Vorschlag wurde von den Entwicklern noch nicht untersucht:
I'd like to amend my report, as I was not clear on the rules. I was not aware that those who returned to camp split the leftover gems for that round. However, if not already implemented, my suggestion could still be helpful for those same situations, but only if there are no leftover gems.
10. Nov 2021 18:26 • Bryant • Dieser Vorschlag wurde von den Entwicklern noch nicht untersucht:
I voted this up, but with the amendment that we can have a player preference to autoskip if there are no gems or artifacts out. For instance, the first draw or two of a round are hazards, it would automatically explore as there is nothing to gain by returning to camp.
22. Jan 2022 19:13 • FSKFSK • Dieser Vorschlag wurde von den Entwicklern noch nicht untersucht:
I thought this was a different proposal. If the first card draw is a hazard, there is no reason to ask players if they want to return to camp (as they would score zero).
Players should not be asked to return to camp until the first non-hazard is draw. It even says in the rules to skip the "return to camp" phase if a hazard is drawn first.
Players should not be asked to return to camp until the first non-hazard is draw. It even says in the rules to skip the "return to camp" phase if a hazard is drawn first.
9. Sep 2023 12:31 • bananasplay • Dieser Vorschlag wurde von den Entwicklern noch nicht untersucht:
The implementation should never decide for players, but a player toggle for this functionality would be very welcome.
24. Jul 2024 18:09 • JCase16 • Dieser Vorschlag wurde von den Entwicklern noch nicht untersucht:
There should be a temporary toggle to say "stay in temple until next gem/artifact card is drawn". When it is drawn then the toggle gets deselected and you would have to toggle it again. There should also be one that says "stay in temple until a hazard card is drawn". So if you have no plans to leave until a bad card is drawn then you can toggle that.
The game SHOULD decide for you if only hazards have been drawn in a round. It should auto play until a good card is flipped. Not having this is simply a waste of time and really can drag games in turn based mode.
The game SHOULD decide for you if only hazards have been drawn in a round. It should auto play until a good card is flipped. Not having this is simply a waste of time and really can drag games in turn based mode.
16. Feb 2025 14:25 • itsmercury • Dieser Vorschlag wurde von den Entwicklern noch nicht untersucht:
This is not a good rule. Especially when playing with a large number of players. A lot of times there will be plenty of gems on the table without any hazard/artifacts even showing up. A player could potentially gamble and risk leaving early with a high number of gems while the others try to stay and split between smaller numbers. This would take the power of choice from players.
Ergänze diese Meldung
Bitte erwähne hier alles, was bedeutsam sein könnte, um diesen Fehler nachzuvollziehen oder deinen Vorschlag zu verstehen:
- Eine weitere Tisch-ID/Zug-ID
- Konnte F5 das Problem lösen?
- Trat das Problem öfter auf? Jedes Mal? Zufällig?
- Falls du einen Screenshot dieses Fehlers hast (optimale Vorgehensweise), kannst du ihn bei Imgur.com hochladen, den Link kopieren und hier einfügen.
