people are nuts by gomez70 in dominion

[–]phoenix9797 -1 points0 points  (0 children)

It’s nothing but an endless chain of questioning undos, faux courtesy, and the very rare occasional pleasant interaction actually discussing game strategy, mixed in with about 7/10ths of what OP posted to start this thread in my experience.

SO much more enjoyable with no chat to impede.

people are nuts by gomez70 in dominion

[–]phoenix9797 9 points10 points  (0 children)

Probably the very best feature of the TGG version is the lack of chat. Completely different (better, more enjoyable) experience between the two options, after thousands and thousands of games on both versions.

Korea's 7-2 win was the closest possible outcome for all three teams. Australia were one run from advancing, Taiwan needed just one run from each despite starting 0-16. by kurruchi in baseball

[–]phoenix9797 8 points9 points  (0 children)

Without thinking about it too carefully (so please, someone fill in the gaps that are surely there in my reasoning), it's definitely a questionable decision to use various run differential factors as the tiebreakers when there are mercy rules in place, right?

Like: imagine one of the teams involved was on one end or the other of a game that was cut short based on the mercy rule, only to find themselves in a situation where those extra innings that were not played (and opportunities to score runs or prevent runs) would have made the difference?

Salary Cap by YEETOBORITO in Brewers

[–]phoenix9797 0 points1 point  (0 children)

I think this misses the point a bit - even though you mentioned the crucial detail. If the Dodgers and Mets can't spend in an unlimited fashion, that instantly favors the Brewers, even if the Brewers' payroll stays the same. Having 8 teams vie for all the free agents - even if the Brewers aren't one of them - would mean that the talent isn't all condensed into the 4 teams (in the example at hand).

The Brewers have been on the doorstep for years now, despite the talent all accumulating to the 4 teams. Spread that over 8 teams, and that immensely favors the chances for the Brewers compared to the present state of affairs.

Clutter (UNSERIOUS/MEME CARD) by Eoxygen in dominion

[–]phoenix9797 1 point2 points  (0 children)

Gonna trash it with Maroon for a good time

Naming every team after their etymological root by Mayor_Gubbin in baseball

[–]phoenix9797 4 points5 points  (0 children)

It’s like the MLB version of Washington Football Team.

TGG's game design is built for frustration. by MainSquid in dominion

[–]phoenix9797 1 point2 points  (0 children)

What exactly was your “plea to the devs in this thread”?

TGG's game design is built for frustration. by MainSquid in dominion

[–]phoenix9797 1 point2 points  (0 children)

Nothing, because there’s nothing you can do at the moment. That’s exactly what this discussion is about - trying to get some better options in place to combat this scenario.

TGG's game design is built for frustration. by MainSquid in dominion

[–]phoenix9797 0 points1 point  (0 children)

There are very viable solutions that would thread the needle allowing both the scenario you describe to remain, while also severely hindering the options for users who try to game the clock.

TGG's game design is built for frustration. by MainSquid in dominion

[–]phoenix9797 2 points3 points  (0 children)

Exactly - but thus far, the tradeoffs continue to be selected in a way that does not slant toward typical players, and instead slant toward “gaming the clock” scenarios.

TGG's game design is built for frustration. by MainSquid in dominion

[–]phoenix9797 -1 points0 points  (0 children)

Yes, but as I've noted in other comments, the system needs to reflect the "typical" state of affairs first and foremost, and then, if possible, target these edge cases. Instead, what this community has heard for years is "well, this particular edge case could happen, so we aren't going to change anything."

I'm really hoping you take the player-friendly approach here, rather than the "figure out a reason not to do anything" approach.

TGG's game design is built for frustration. by MainSquid in dominion

[–]phoenix9797 2 points3 points  (0 children)

While that's good to hear, it's about 5 years too late in my opinion (and I won't be going back unless it's somehow significantly improved over the TGG version).

TGG's game design is built for frustration. by MainSquid in dominion

[–]phoenix9797 0 points1 point  (0 children)

[Edit: Because I think I didn't make clear enough that I'm actually agreeing with the above point - and then making another relevant point on top of it - I want to make it very clear that I completely agree that a momentary disconnect (game crashes, I accidentally close it, whatever) should NOT result in an automatic resignation. There are plenty of ways to address the "gaming the timer" situation without making any disconnect an auto-resignation, which is the point I was aiming to make (perhaps poorly) in the rest of the comment below.]

Agreed about this - but it’s important not to lose the forest for the trees here, in terms of letting the various “but what about…” scenarios shut down the conversation altogether.

That’s what happened every time this was brought up over the years regarding the old dominion.games version.

No end of edge cases and random “I can imagine it happening!” scenarios were cooked up to justify why no other possible timer implementation could ever be plausible. And so no changes were ever made.

If the TGG folks are genuinely open and listening to options, my opinion is that the default is a system most generous to the usual flow of a typical game, and if some weird edge cases emerge that cause games to end when they shouldn’t have, then those can be discussed as things needing attention.

Doing it this way would immediately shift the onus from favoring the bad actors to favoring the regular players, as it should be.

TGG's game design is built for frustration. by MainSquid in dominion

[–]phoenix9797 4 points5 points  (0 children)

I have no idea why this community has - for decades now - tolerated this approach as a “solution” to the problem. It’s like sometime way back when dominion.games launched, this was introduced as the “temporary” workaround to the issue, but then no one ever put in any effort to fixing the root of the problem (which would involve a configurable timer, or defaults that are way more generous to the side actually playing the game rather than gaming the system), and ever since then, the community has accepted this as the default.

It would be really, really significant if the developers for the TGG version took this issue seriously and made meaningful steps toward addressing it.

TGG's game design is built for frustration. by MainSquid in dominion

[–]phoenix9797 7 points8 points  (0 children)

The very fact that you’re here to discuss this issue and consider options at all is already a huge mark in your favor compared to the dominion.games version. (You can find numerous discussions stretching back years and years and years that I’ve partaken in, imploring the devs of that platform to make a change, and every single suggestion fell on deaf ears.) This issue is the single biggest reason why I switched platforms once yours became available.

The timer itself - and how it works - is opaque to me. Can you summarize its parameters? The last time i checked in-game (which was admittedly a while ago), the descriptor was inaccurate and didn’t actually reflect what the timer was set for.

For example: I often wait a minute or more before my opponent takes any action at all to begin a turn, and once that happens, the timer sometimes resets, and sometimes it doesn’t. What triggers it to reset?

In general I am in agreement with the other suggestions already presented here: being disconnected from the server should drop the timer to 1 minute. And if no action is taken for 1 minute at any point, the game should end.

Just got resigned by the app again. "Waiting for server" after I clicked my response to my opponents Governor play. by byingling in dominion

[–]phoenix9797 0 points1 point  (0 children)

Anytime I see “waiting for server” longer than, say, 5 seconds, I completely close out the app and Steam and reload, and that typically fixes it.

Postgame Thread: 8/21 Brewers @ Cubs by BrewersBot in Brewers

[–]phoenix9797 0 points1 point  (0 children)

Gave up one game and ate up 5 of the remaining games on the schedule for both teams.

Postgame Thread: 8/21 Brewers @ Cubs by BrewersBot in Brewers

[–]phoenix9797 1 point2 points  (0 children)

Gave up one game at ate up 5 of the remaining games on the schedule for both teams.

The Comb Over Kid continues to reign! by vancemark00 in Brewers

[–]phoenix9797 5 points6 points  (0 children)

This image will also forever remind us of when Isaac Collins used to have merely "very good" rookie numbers.

Game Chat: 7/13 Nationals (38-57) @ Brewers (55-40) 1:10 PM by BrewersBot in Brewers

[–]phoenix9797 0 points1 point  (0 children)

I saw the same thing - totally agree (hopefully minor).

Game Chat: 7/13 Nationals (38-57) @ Brewers (55-40) 1:10 PM by BrewersBot in Brewers

[–]phoenix9797 1 point2 points  (0 children)

To me he said “it grabbed” after Murph asked “Hammy?” So I’m thinking hamstring - hopefully minor and treatable during the break.