Cooldown Period on Casino machines.

[Achtergelaten Hond]

So, There I was minding my own business when out of the blue came a wild 606K jackpot WoM machine. "Wow." I thought, "Sure would be nice to win that." So it was decided that I was going to spend as much time as was nessesary to get that jackpot. I have no life afterall so hours of bingeing was no problem. There I sat for 25 hours straight pressing my spacebar. It was a long and tedious road but I stuck to it! I was determined.

When suddenly I was disconnected from the server for less than 2 minutes! "Oh no!" I exclaimed. "My machine better not be taken by some Autohotkey ♥♥♥♥♥♥!" but alas, I was not so lucky. My now almost 700K jackpot machine was taken right out from under me by some ♥♥♥♥boi Autohotkey user.

Now, here I stand. Wanting to kill myself. The moral of the story; Add back the machine cooldown period that holds the seat for you for up to 5 minutes after you leave it and don't be an Autohotkey ♥♥♥♥♥♥.

Also, shoutout to this ♥♥♥♥ hope he/she gets merked:
https://puu.sh/rtC7h/2ffc7418fc.jpg

tl;dr
Add machine cooldowns for if you get disconnected accidentally and ♥♥♥♥ AHK users.

[boxes]

"There I sat for 25 hours straight pressing my spacebar."
no you didn't
you're entitled and have no proof anyone is macroing or just "sitting there for 25 hours straight pressing your spacebar"

the only response you could have to this is some passive aggresive dismissive remark. make money just like everyone else.

[Achtergelaten Hond]

You call me out for not having proof yet you have no proof that I didn't actually sit there for 25 hours. Whether you believe it or not in irrelivent.

As for the macroing it's pretty obvious when someone it using one. There is no delay between lever pulls. They are always at the exact same time without fail. The spins happen instantly. Also, the fact that you'll see people win jackpots and then just stay in the seat continuing to play. No reaction to the win, not a single remark in chat.

This post was supposed to be light-hearted but of course, some people have to take everything so seriously. I earn my money just like everyone else as there is no way to earn money outside of the public available methods.

I'm perfectly fine with people macroing as long as they do it while they're still at their PC and they actually interact and chat with others while they're playing the machines. It's when you get the same people every night logging on for the sole purpose of getting onto the WoM machines just to macro while they're asleep. I don't see the point.

Anyway, the key point of my original post still stands. There should be some sort of cooldown in the unlucky event that someone is timed out. Just like in GMT. If someone got up from a slot machine there was a 5 minute wait period before anyone else could use that machine.

[boxes]

tldr

[Achtergelaten Hond]

Of course. Start something and look for the easiest way out. Good lad. +1 to you.

[Twelve-Oh-One Alarm]

Originally posted by Valhalla:

You call me out for not having proof yet you have no proof that I didn't actually sit there for 25 hours. Whether you believe it or not in irrelivent.

The burden of proof falls on you. A claim with no evidence can be dismissed with no evidence.

[Achtergelaten Hond]

Originally posted by Ðérak:

Originally posted by Valhalla:

You call me out for not having proof yet you have no proof that I didn't actually sit there for 25 hours. Whether you believe it or not in irrelivent.

The burden of proof falls on you. A claim with no evidence can be dismissed with no evidence.

Of course. Under any other circumstances I would agree with you but when the problem is so blatantly obvious and the issue is already being adressed by the developers I see no need in providing proof.

Anyway, this thread is going way off topic. The key point seems to have been lost.

[Twelve-Oh-One Alarm]

Originally posted by Valhalla:

Originally posted by Ðérak:

The burden of proof falls on you. A claim with no evidence can be dismissed with no evidence.

Of course. Under any other circumstances I would agree with you but when the problem is so blatantly obvious and the issue is already being adressed by the developers I see no need in providing proof.

Anyway, this thread is going way off topic. The key point seems to have been lost.

Well as you said, the developers have adressed it. They're pushing an update sometime in the next 7 days Matt has stated today[u.patrickqh.com]