Wargroove Auto End Turn feature does not consider for blocked deployment

Channel:

Master Knight DH

Subscribers:

1,960

Published on September 1, 2019 5:25:42 PM ● Video Link: https://www.youtube.com/watch?v=QPRzYTDAsk0

Game:

Wargroove (2019)

Duration: 0:46

56 views

0

For relevance:
https://www.youtube.com/watch?v=tGWu74mdcUk

And no, I haven't forgotten about the unpaid worker allegations against Chucklefish. I'm actually posting this as further evidence against Chucklefish in general in fact.

This is something I labbed on suspicion just now thinking about a point I'm writing about. I had a gut feeling that the bright idea Chucklefish had to make sure the Auto End Turn only triggered for deployment properties being invalid was simply to treat deployment properties as as units to move. It would explain why the AET doesn't trigger from insufficient funds to purchase anything regardless of any other circumstances.

This, obviously, doesn't work. The only way to "end" a deployment building's turn is to actually build a unit from it. The player can't always do that and that's the case if either the player lacks the funds to build ANY unit at all, or if the building is blocked off from building the unit. I link to my AET hack of GBW3 to showcase how I'm able to account for deployment ability and then some, and I did so a over a year before Wargroove's release, without the benefit of easier programming languages than Z80, OR the blessing of a company as big as Nintendo.

I *MIGHT* get that managing the coding for deeming a deployment building invalid to force the AET might get complicated because of the 4 deployment sides point, but the insufficient funds issue is already blatant enough that all of this should have come up in playtesting. Even then, I think the only way RAM could possibly get strained by checking each deployment point for usability after all units had moved, would be because of a *RIDICULOUS* number of deployment points on the map to begin with. And even then, it need only be done once by involving the use of headcounts for each type of building to then check for further deployment, as well as a flag to stop the game from checking the deployment property count again.

But nah, let's not consider ideas from me. Apparently, I'm "toxic", because some smear campaigners said so, please ignore that they threw stones in their little glass house.

Chucklefish, you're found guilty of arrogance.

Other Statistics