Posts: 15,136
Threads: 111
Joined: Apr 2007
(January 3rd, 2013, 09:18)novice Wrote: Goto command?
I find that hard to believe because the unit was moved before I logged in. I've used goto with Pitboss before, and it doesn't execute so quickly that you don't see it happen. Also, I definitely wouldn't have queued up that move - especially not in that direction. I'm a little confused. I sent a message to Commodore asking where the Impi was when he played his turn (an hour or so before me).
Posts: 15,136
Threads: 111
Joined: Apr 2007
Lurker opinion requested - do we ask for a reload or eat this? I don't want to be a hassle or set a bad precedent, but this one does matter a good bit more than missing a worker turn or something.
Posts: 23,408
Threads: 132
Joined: Jun 2009
Go To commands execute after you've moved all other units that are awaiting orders, so if you logged in and had no other units awaiting orders, the impi would have moved automatically with no way to stop it.
Current games (All): RtR: PB80 Civ 6: PBEM23
Ended games (Selection): BTS games: PB1, PB3, PBEM2, PBEM4, PBEM5B, PBEM50. RB mod games: PB5, PB15, PB27, PB37, PB42, PB46, PB71. FFH games: PBEMVII, PBEMXII. Civ 6: PBEM22 Games ded lurked: PB18
Posts: 15,136
Threads: 111
Joined: Apr 2007
(January 3rd, 2013, 09:46)Krill Wrote: Go To commands execute after you've moved all other units that are awaiting orders, so if you logged in and had no other units awaiting orders, the impi would have moved automatically with no way to stop it.
Ok. So I had 1 warrior to my north that still had to move and 3 workers that did not have orders. Also, the new axe which you can even see in the screenshot is selected and unmoved. It should not executed immediately then, right?
Posts: 12,510
Threads: 61
Joined: Oct 2010
(January 3rd, 2013, 09:30)scooter Wrote: Lurker opinion requested - do we ask for a reload or eat this? I don't want to be a hassle or set a bad precedent, but this one does matter a good bit more than missing a worker turn or something.
I think you're within your rights to ask for a reload, but...
If I read the tech thread correctly, a reload can't happen for another 36 hours minimum because Sunrise is out of town. Only because of that, I would suggest you eat the bug. It didn't lose you a unit, just caused your tactical position to deteriorate, while a reload would cost everyone two days.
That said, if you lose the war, clearly this was the sole reason and you're can blame sunrise for it .
EitB 25 - Perpentach
Occasional mapmaker
Posts: 15,136
Threads: 111
Joined: Apr 2007
Ok, I heard back from Commodore. He said it was on that tile 1N of the archer when he logged in - so the move happened before he logged in (when nobody on our team logged in - I checked on Civstats to verify).
Goto definitely does NOT execute when you are not logged in - I specifically remember ASM being disappointed that it didn't work that way in PB7. So I think this is a bug. Crappy part about this is like Mardoc said - I believe sunrise is out of town. I'm not sure how to react to this, then. It would have changed Commodore's moves I imagine - that Impi actually double-moved him to get to there. So... thinking this over. This is odd.
Update: Commodore said yes, he definitely would have played differently if I was there. So it affects him too.
Posts: 15,136
Threads: 111
Joined: Apr 2007
Pindicator - I'd like to hear your opinion whenever you get a chance. My feeling is now that if sunrise was around, I'd probably ask for a reload... Commodore says he won't be back until later on Friday, so I don't want to hold the game up for 36 hours for this. Commodore is OK with play-on too. In case you were wondering, he did say he would not have attacked our Impi (since that would have been very impactful had the glitch not happened), but he would have played differently - whatever that means. The main thing that sucks for us is if he uses this to put another unit on that hill, but that's the extent of the loss for us. We also lose the ability to pressure him for a couple turns and we lose position on that forest. This is a bummer, but I'm apt to say let's eat it.
Also, I'd really like to figure out what happened here, so input is welcome. Upon logging in to check again, it does look like a stray goto happened - it was on goto way up northeast. No idea how that happened. Anyways, it still should not have executed before Commodore played, let alone before I played (and I would have moved the Impi first, seen it, and canceled it). So something happened that should not have happened here, and I'd like it to figure out the cause.
Commodore noted that random events can throw things like this out of whack, and noted slowcheetah's 3 point jump at EoT is odd - could possibly be an event. Any more ideas from the lurker braintrust?
January 3rd, 2013, 10:39
(This post was last modified: January 3rd, 2013, 10:42 by Ceiliazul.)
Posts: 4,831
Threads: 12
Joined: Jul 2010
Can't help with why, but automatic moves suck. A similar incident caused me to lose two of my first three workers in Pb5: both workers auto-moved before any commands were given. I've never trusted the Pitboss engine since.
I'm not sure why I didn't request a reload for that, actually... I probably should have. Here though, I agree it's not worth the delay.
Posts: 13,214
Threads: 25
Joined: Oct 2010
So, I think you accidentally put the impi on automatic exploration. Fucking Pitboss.
January 3rd, 2013, 10:55
(This post was last modified: January 3rd, 2013, 10:55 by scooter.)
Posts: 15,136
Threads: 111
Joined: Apr 2007
(January 3rd, 2013, 10:39)Ceiliazul Wrote: Can't help with why, but automatic moves suck. A similar bug (auto-mov e before commands are done) caused me to lose two of my first three workers in Pb5... I've never trusted the Pitboss engine since.
I'm not sure why I didn't request a reload for that, actually... Probably should have.
Seriously?? First, that's definitely reload-worthy. Second, that explains a lot. I have no idea how I missed that in the post-game thread reads. Anyways, I always wondered during that game why your team's start seemed slow compared to what I would have expected. I just attributed it to your relatively low amount of forests to chop, but I really wasn't sure what the answer was. Anyways, I feel less bad for myself now, this wasn't as significant as even losing 1 worker.
|