Are you, in fact, a pregnant lady who lives in the apartment next door to Superdeath's parents? - Commodore

Create an account  

 
RBP3 IT Office - Email and technical issues

Sorry for being interruptive but I think a golden rule of RB is about to be broken (if not, feel free to delete this post).

From reading several teams threads, some teams are feeling 'liberal' about replaying the turn in the same way as before.

My understanding as a lurker in the other games (where the situation had happned) and my experience at RB are telling me than you are obliged to replay exactly in the same way as correctly as possible if facing the same situation (especially if the reload gave you extra infos)
[of course RNG could be different so a few variations might be tolerate : ie - no need to suicide your charriot against a barb if it turns to be an spear instead of a warrior]

At worst, when in doubt, the teams should be asking about the proper rule.
Reply

Jabah Wrote:you are obliged to replay exactly in the same way as correctly as possible if facing the same situation

Yup, that's the rule. The only exception might be if you made a misclick of your own too minor to ask for a reload. In that case it would IMO be okay to fix it.

Darrell
Reply

We had a barb warrior on our border. We moved a warrior of our own on a forest, hoping the barb warrior would suicide against it.
The first time around, the barb moved around the warrior to threaten the city.
After replaying, allthough I had moved the units in exactly the same way, the barb warrior suicided against our warrior.
Anything I could have done to prevent that from happening?
Reply

Ilios Wrote:Anything I could have done to prevent that from happening?

No, you did exactly what you were supposed to and got lucky thumbsup.

Darrell
Reply

Actually, it was probably directed at us.

Our team was undecided on how to approach this situation. We did ask for lurker comments on the subject and hadn't committed on moving differently. In hindsight maybe we should have asked here.

Anyway, we've decided just to live with it and keep going. Sorry for appearing to be in bad faith.
Reply

WarriorKnight Wrote:Actually, it was probably directed at us.

Our team was undecided on how to approach this situation. We did ask for lurker comments on the subject and hadn't committed on moving differently. In hindsight maybe we should have asked here.

Anyway, we've decided just to live with it and keep going. Sorry for appearing to be in bad faith.

It was not directed to you only (otherwise I would have just comment there).
Your decision was a relatively minor change compare to what other(s) team(s) has been considering doing (not saying they did)
Reply

darrelljs Wrote:The only exception might be if you made a misclick of your own too minor to ask for a reload. In that case it would IMO be okay to fix it.

Darrell

Really? "Misclick" needs to be a very narrow definition of misclick, otherwise it allows a team to correct mistakes that they made the first time around.

Examples of mistakes:
For the T68 reload, we goofed the first time played and gave a worker of ours commands in the wrong order from our plans, costing us 2 worker turns. This was not a misclick; when I moved the worker, he did what I was thinking he should be doing at the time. When the turn was reloaded, we could have corrected that mistake, but that crossed the line and so we never considered playing it differently.

This time around, on the original T72 we realized that we could make a micro improvement that would have been useful on T71 as well, but again didn't; we'd made that error on T71 originally, and aren't going back to correct it. The reload was to correct a bug in the software, not my oversight in our possibilities.

If a barbarian takes a different action in the reload, though, I would support reacting to the new situation. However, as soon as is reasonable (say, if now your unit has to heal, after the heal), any tiles scouted in the original T72 should be scouted.
Reply

When I say misclick, I mean something along the lines of "I meant to move my Worker NE but the game was laggy and he went E".

Darrell
Reply

Ok, that would be fine IMO.
Reply

Very sorry, we've moved a warrior the wrong way after the reload.

Can we have another reload please.
Reply



Forum Jump: