Hi, Bluz here.

Locked Battles~ You can enable, disable Locked battles.

How? Simple, if you enable locked matches, your opponents will be unable to quit the match.

That's all, pretty short huh?

So any who, I am suggesting this because I really hate quitters because:

1. It spoils my fun
2. I have decreased rewards
3. If someone quits my match, it would trigger a bug that would make me stuck on the battle. Where the timer would stop at 00 and everything is frozen.

While I understand (and appreciate) the idea, it just isn't IMO something we can do.

I mean - they can always close the browser. We can't stop that.

I suggest fighting against friends instead - maybe make a clan rule that you can't quit matches, ask other clans to do the same.

Maybe if you can choose?
1. If the opponenent quits the game is over if you want
2. when your opponent quit or close the browser the game is still going. He lose his action points but you can finish him if you really want. And of course the opponent can't search for a new battle until you finished him. Thats his punishment.

actually, I disagree Alex. What if you simply lock in a mech on the match to stay online until their battle is over? The only issue I see with this is the potential of getting stuck if a winner that has the "finish him" feature up decides to leave. In which case, we just need to add in an auto end feature. Just keep the 20 second time limit for moves on all aspects.

If a player quits, the battle proceeds and the other mech will simply stay still for their 20 seconds. If they were purposefully trying to quit, if they log back in, they will still be in the battle. Keep it this way until somebody wins.

So this way, if a player does get disconnected BUT logs back in on time, they could potentially get back and finish their match against someone. I know this has happened to me once or twice. I was confident in my win, but my roommate accidentally turned my wifi off

I logged back in seconds later and it's already done. Would be nice if it simply continued. And if a player REALLY wanted to mess with a quitter, they could take them down to 1 hp (or something) then simply leave them in the match

Then the other player has to beat them. Of course, i'm sure this COULD cause server issues and bog things down. So perhaps make an auto quit feature if a player misses 4 or more turns. That part could easily be put up for discussion.

However, not being a programmer, I do not know what kind of hassle it would be to do this. To me it sounds simple enough of a change.

Thanks for the feedback guys!

Though my point is, (or alternative idea for this suggestion) is..... Once you reach a skull rank, you won't be able to quit. And if you quit, you would lose certain items from your inventory. However, would the server detect if a player had connection lost in his country? If so, the fight wouldn't count as a loss.

Nor when a player misses 4 turns, then auto-quit? Shouldn't count as a win. For example, my opponent had missed 4 turns. However, it wouldn't count as a loss. Though it will be counted as.. (probably): "AFK Lost" ? (I am just suggesting.)

Oh by the way, I had another idea up my sleeves. Which is.... that there should be at least a 30 second pause. Though, however... You can only have maximum pauses for 1 time. (for avoiding abusement purposes.) Note: The timer countdown for using turns wouldn't be affected if you used the 30 second pause. Any who, you guys can tweak the newly suggested idea of mine.

^ Suggesting that because I usually get commands from my sisters or mother during a match. (also for beneficial purposes for players)

That's all, I have to sleep bye! I will be enrolled for school tomorrow at 8 AM.

PS. You can manually stop the 30 second pause. And by the way Josh, I like the way you're thinking.

There is already a autom. quit after 2 missed turns



A quit is a free win (if he quit at start), and after a % of damage you get a reward.
I see no problem with it, as it is.

ONLY ...

HERE Bluz is 100% right ... that bug should be solved, it is really annoying

That happens very often, I think it happens, if a iphone- or tablet-user quit against a pc-user.