logout macros shouldn't be tolerated

logout macros make hardcore and especially races a joke. I'm absolutely baffled that people have been banned for taping their flask keys or using a popsicle stick but well known streamers can actually advertise the logout macro that they use in their stream info (look at etup's twitch page). IMO if a logout macro that gets your character out of the game a fraction of a second faster saves your life, you probably should've got out a full second earlier. How is that not one keypress performing multiple actions? (which from what I've read is the reason you cant use a popsicle stick or w.e)

Video Game Police sighted. Confirming identity: Scrubcore.

Commence with whine.

Thanks for that, however I'm genuinely asking how logout macros can be tolerated when they require the macro to press enter and type in "/exit" and press enter again. The macro is performing 7 keystrokes but the server only gets the "/exit" command?

edit: as opposed to having something that hits all 5 flasks at once [5 inputs to the server] (or w.e it might be, saw a post where a guy said he was banned for a macro that made a noise when he got below 50% hp he said he didn't have it linked to use any flasks)

"

DreamLAB a écrit :

...saw a post where a guy said he was banned for a macro that made a noise when he got below 50% hp he said he didn't have it linked to use any flasks

I fail to see why something like that should be considered bannable, given that it does not, as noted, input anything. In fact, such a low-health warning wouldn't be a bad thing to have in the game proper (with the threshold configurable in options).

"

The_Reporter a écrit :

It's because GGG doesn't have the stones to just ban ALL of it. They should also man up and add a logout delay as well. Enough of this grey area garbage.

As interesting as this debate is (aside from the silliness that is the first response), the fact does remain that etup or whoever using such a thing doesn't oblige anyone else to follow suit.

"

DreamLAB a écrit :

Thanks for that, however I'm genuinely asking how logout macros can be tolerated when they require the macro to press enter and type in "/exit" and press enter again. The macro is performing 7 keystrokes but the server only gets the "/exit" command?

That's considered one command yes, like /oos macro was one command and allowed.

But yeah, logout macros should not be allowed. Logging out manually is already too OP.

In fact to be honest, it don't save you the vast majority of the time. as a matter of fact you can saw that HC people die even with the existence of this macro. You'll die so quickly generally that you can't use that macro efficiently.
Try to play HC and you'll see that's not the saving grace you think...

I don't see how GGG could possibly detect the use of a log out macro? Of course they could notice someone advertising a log out macro but they can't programatically detect the use of a log out macro, can they?

snyde remarks aside. The CEO of gridinggeargames is on record stating that logout macros are within the TOS, and he actually recommends using one in hardcore because of the way game difficulty is balanced.

So, your opinion is valid, and considered, but this ship has sailed for some time.

I'm having trouble locating this - can someone link my source? I'll keep looking, though.

"

DreamLAB a écrit :

Thanks for that, however I'm genuinely asking how logout macros can be tolerated when they require the macro to press enter and type in "/exit" and press enter again. The macro is performing 7 keystrokes but the server only gets the "/exit" command?

This is actually not how most logout macros work. The best ones send a TCP disconnect to the server.

"

Turtledove a écrit :

I don't see how GGG could possibly detect the use of a log out macro? Of course they could notice someone advertising a log out macro but they can't programatically detect the use of a log out macro, can they?

only if their copy protection takes control over the whole computer and all programs.

afaik, the logout maccro uses a exe which sends a "abort connection nao" packet to the server on the way the client normally communicates with the server (it injects the packet on the same socket), the server interpretes this as coming from the client and immediately closes the instance and confirms that to the client. the client interpretes the closing message from the server as "abnormal connection closure" from the server cause it didn't close the connection itself.