Turn Discussion

[Joshua368]

Well how severe was it? Ours was just a scout running off in the wrong direction for a turn, without running into any barbs.

 

[peter grimes]

Wait a second, everybody. Let's not start jumping to conclusions before we all know exactly what the problem was.

if the game was lagging, and the turnplayer clicked, which the game then registered as a move, that's one thing. But if the game froze, CTD, or something along those lines, that's a different issue altogether.

Before we all get to the point where it's more important to win the argument than it is to keep the game running smoothly, I advise that we all just wait to hear what Ginger_Ale has to say after investigating.

 

[Provolution]

Peter is right. There is no need to get political, be inquisitive or toss out inflammatory statements as well as externally working the in-game diplomacy from non-game events. I have seen the quality of other MTDGs be diminished due to such processes.

We already got a series of systems in place to handle this, and there is no need for "volunteers" to obfuscate and rig the process, as we already have Daveshack to pause the game (as long as individual players show the courtesy to NOT unfreeze the game) and Ginger Ale to look into it. Let these gentlemen do their things, and we can play again.

 

[Memphus]

So we can asume then that G_A has been pm'd and we arn't just waiting on him here?

 

[Provolution]

Ginger Ale has been in our forum, saw him today.

 

[cav scout]

I would rate this situation as much more severe than a wayward scout.

The misclick wasn't due to operator error. We have already had a couple of those incidents actually and haven't said a thing, just sucked it up and lived with it as we should have.

This case is different- our turn player experienced a severe bout of lag which caused a string of clicks going to the wrong place on the screen. This was a technical malfunction since the error occured because of the lag.

The effects were substantial enough for us to ask for the pause and the reload. Please understand that we wouldn't make this request lightly.

 

[Krill]

We need to consider the precident that we would be setting by allowing a reload though; if during war lag occured, which is very likely due to large numbers of units being present, and some units were moved differently to how the team originally wanted but revealed new map infomation that otherwise would not have been available, would we allow a reload?

 

[Provolution]

I think the precedent would the fairness that each team will be allowed to be considered for one bad session of lag each during peacetime.

 

[Joshua368]

We need to consider the precident that we would be setting by allowing a reload though; if during war lag occured, which is very likely due to large numbers of units being present, and some units were moved differently to how the team originally wanted but revealed new map infomation that otherwise would not have been available, would we allow a reload?

In a situation like that you could have the lagged player not post screenshots or repeat what he saw, reload, and have a new turnplayer make the next few moves.

Or just have the turnplayer agree to not share the info with anyone and then not alter any previous strategics because of it.

 

[Provolution]

Ginger Ale is looking into this, and would make a ruling on this.

 

[Krill]

In a situation like that you could have the lagged player not post screenshots or repeat what he saw, reload, and have a new turnplayer make the next few moves.

Or just have the turnplayer agree to not share the info with anyone and then not alter any previous strategics because of it.

Now you are getting into dangerous territory; how can we decide how long they must not participate in the game for? Does it depend on what they see? How can you police this issue? What if someone "claimed" a misclick to get a reload after something important becomes apparent to them?

It would be simpler, and safer, if no reloads were allowed for the issue of lagged moves, IMO.

 

[Niklas]

This is why we have moderators, so we don't need to worry about what's a precedent and what isn't. And now GA has ruled in favor of a reload, so a reload it is.

But I think we can all agree to be very careful with doing anything at all while we experience lag. Better to immediately log out and log in at a later time, if at all possible.

Now let's get moving again!

 

[Renata]

I don't even know what MP lag is. How can you tell it's happening?

 

[oyzar]

Things doesn't move when you tell them too, the game is slow that sort of thing... Just waiting fixes it more often than not though... It should be mentioned that every time someone else logs in the game freezes.

 

[Memphus]

oyzar said it perfectly. when people log in stop touching things...if not units tend to do weird things...

 

[Krill]

Not weird things; the orders are saved in teh game and don't carry out until the joiner has finished joining, when all of the orders that were given (like pressing the mine button 5 times) are carried out; it happens alot when you play MP and have random people joining unpassworded games.

 

[DaveShack]

GA has ruled that a reload is allowed. See the turn tracker thread.

 

[Lord Parkin]

Considering that this is a one-time event (and an accident, too, that was due to some technical lag) with a pretty harmless remedy, I think a reload is fine.

Hmm, Saturn's original misclick was also due to lag (accidentally clicking while the screen was blank and loading, then having that click "count" as a move). But whatever.

I'm just trying to make sure we're consistent with the rules, that's all. I'd be saying the exact same stuff if it was any other team. It's just that if we keep playing for one team's misclick and reload for another's, it's not particularly fair and balanced.

Now obviously our Scout misclick may not have been as serious as Kazakhstan's misclick(s). However, we have to be careful to set specific rules to deal with things like mistaken unit moves, and apply them consistently. Otherwise (worst case scenario) we might end up with teams frequently claiming "misclicks" during wartime and requesting reloads when they shouldn't. (That's really unlikely, and I doubt that it would happen in this game. But we should still plan ahead to avoid trouble, that's what I'm getting at. )

 

[Provolution]

Well, I was getting on not affecting diplomacy and the ruling by lobbying through volunteerism here. But thank you for your concern.

 

[Lord Parkin]

Uh... lobbying? The purpose of these forums is for discussion, you know.

I'm not trying to affect the ruling. I'm just trying to make sure we smooth out an approach to any potential future issues before they occur.