Previous Thread
Expand All
Collapse All
Ignore Author
Reply
I know the rule, three strikes caught and you're out, perma deleted etc
What I'm curious about is..
When pulling folks for being AFK and/or while checking them.. Do you PING them to see if they're actually there or if by chance they're not due to technical difficulties?
Recent deletion ...character claims caught only due to technical difficulties.. not going to argue whether or not the character's player was or not at the keyboard or should have been, or not deleted, was 3 times AFK within a year...we all know the risk, or should.
My only concern is this.. I'd rather know that we're being pinged to see if we're truly here or not or possibly had been disconnected in which case the script would keep running IG until the game finally drops us.
~Averalaan
They don't PING anyone during a script check. The PING attempt would just allow a loophole in the scriptchecking process (technical difficulties being equal to deliberately pulling the phone/ethernet cable out). Ergo, folk will use it to escape punishment simply by mimicking the conditions of an honest connection issue.
This is one of the reasons why you SHOULD respond quickly to any script-check messaging, because you could very well be sitting there going "hmmph, he isn't up to the OOC warning messaging yet, think I'll continue for a little before answering", and right before you choose to respond your connection craps out. Suddenly, for practically no reason at all, you just failed a script check.
J'Lo, no that other one
The Manipulation List -- http://symphaena.com/index.html
This is one of the reasons why you SHOULD respond quickly to any script-check messaging, because you could very well be sitting there going "hmmph, he isn't up to the OOC warning messaging yet, think I'll continue for a little before answering", and right before you choose to respond your connection craps out. Suddenly, for practically no reason at all, you just failed a script check.
J'Lo, no that other one
The Manipulation List -- http://symphaena.com/index.html
>They don't PING anyone during a script check. The PING attempt would just allow a loophole in the scriptchecking process (technical difficulties being equal to deliberately pulling the phone/ethernet cable out). Ergo, folk will use it to escape punishment simply by mimicking the conditions of an honest connection issue.
It always amuses me when people insist that the GMs should be able to do this. It's not like someone can fly/drive out to your computer to verify that your modem did indeed crap out, as opposed to you pulling the plug. From serverside there's no difference - it's just a dropped connection, period.
~Aleximarus
It always amuses me when people insist that the GMs should be able to do this. It's not like someone can fly/drive out to your computer to verify that your modem did indeed crap out, as opposed to you pulling the plug. From serverside there's no difference - it's just a dropped connection, period.
~Aleximarus
Uh, if someone pulled out the cable in the middle of a script check in order to prove technical difficulties, they would be responsive or easily able to be responsive.
Seeing as GMs can tell what a person inputs and you don't need to be learning experience at the time of the warning, only at the start or maybe middle of the script check, I don't think it would be too much to ask though there may be some other difficulties associated with such a practice.
I am --- Navak
Seeing as GMs can tell what a person inputs and you don't need to be learning experience at the time of the warning, only at the start or maybe middle of the script check, I don't think it would be too much to ask though there may be some other difficulties associated with such a practice.
I am --- Navak
>Uh, if someone pulled out the cable in the middle of a script check in order to prove technical difficulties, they would be responsive or easily able to be responsive.
You never know with some people. c_c People are weird!
Either way the logout-disconnect issue is really much more relevant to ghosting/logging out in combat, rather than script checks.
~Aleximarus
You never know with some people. c_c People are weird!
Either way the logout-disconnect issue is really much more relevant to ghosting/logging out in combat, rather than script checks.
~Aleximarus
This one is a good question.
<<Do you PING them to see if they're actually there or if by chance they're not due to technical difficulties?>>
The answer to this is, sort of. If you're using the Wizard or StormFront, there is automatic checking that goes on to make sure the front end is still connected, and the front end responds all by itself. There is also a second item in there that will log you out automatically if no commands are being sent (that's the one in SET inactivity) so this is something we check at two levels by indirect means.
Once that is accounted for there are still other things we do. When I check these I know what the system rules are, how long the inactivity timer works, and look for things like were commands being sent or not? That's a great indicator of disconnects. If someone is saying they were disconnected, but commands were being sent the whole time, the math on that is pretty easy. There are still other things I can check on this front as well, those are just some of the basics.
Even then we've found a couple of special cases that if I can see, we'll handle differently. A few years ago there was a series of tornados that tore up a part of western Missouri. Last year there were the hurricanes causing problems in the gulf, and also on parts of the east coast. Before that was the Florida year. Once upon a time, a couple of idiots with a backhoe severed a fiberoptic trunk line connecting Minneapolis to Chicago (which is one of three big lines doing east-west data transmission) and I'm sure you can fill in the blanks on what kind of mess that caused.
What all of these have in common is they are events beyond anyone's control (except the guy at the levers of the backhoe), and many of them are direct threats to life and limb. Always put your safety ahead of that of your character. Sometimes bad things are going to happen, and if they can be documented, I will make sure the results at this end are minimized. If there's a tornado, forget about the computer and take cover.
Finally, as people know, I can't talk about specific cases. Because of that, I'm going to ask that the conversation in the second part of this thread drop. The privacy rules I have to operate under mean I can't talk about accounts or characters with anyone but the account holder. I can't confirm what happened or even if anything happened at all. There are days I would love to tell everyone "This guy did this and this and this, and if that weren't enough, this, this, and this too." but I can't. If you want to talk about it on someone else's boards that's up to you, but not here. It's a question we cannot answer without breaking the privacy rules, and that is not going to happen.
--Sanguious
<<Do you PING them to see if they're actually there or if by chance they're not due to technical difficulties?>>
The answer to this is, sort of. If you're using the Wizard or StormFront, there is automatic checking that goes on to make sure the front end is still connected, and the front end responds all by itself. There is also a second item in there that will log you out automatically if no commands are being sent (that's the one in SET inactivity) so this is something we check at two levels by indirect means.
Once that is accounted for there are still other things we do. When I check these I know what the system rules are, how long the inactivity timer works, and look for things like were commands being sent or not? That's a great indicator of disconnects. If someone is saying they were disconnected, but commands were being sent the whole time, the math on that is pretty easy. There are still other things I can check on this front as well, those are just some of the basics.
Even then we've found a couple of special cases that if I can see, we'll handle differently. A few years ago there was a series of tornados that tore up a part of western Missouri. Last year there were the hurricanes causing problems in the gulf, and also on parts of the east coast. Before that was the Florida year. Once upon a time, a couple of idiots with a backhoe severed a fiberoptic trunk line connecting Minneapolis to Chicago (which is one of three big lines doing east-west data transmission) and I'm sure you can fill in the blanks on what kind of mess that caused.
What all of these have in common is they are events beyond anyone's control (except the guy at the levers of the backhoe), and many of them are direct threats to life and limb. Always put your safety ahead of that of your character. Sometimes bad things are going to happen, and if they can be documented, I will make sure the results at this end are minimized. If there's a tornado, forget about the computer and take cover.
Finally, as people know, I can't talk about specific cases. Because of that, I'm going to ask that the conversation in the second part of this thread drop. The privacy rules I have to operate under mean I can't talk about accounts or characters with anyone but the account holder. I can't confirm what happened or even if anything happened at all. There are days I would love to tell everyone "This guy did this and this and this, and if that weren't enough, this, this, and this too." but I can't. If you want to talk about it on someone else's boards that's up to you, but not here. It's a question we cannot answer without breaking the privacy rules, and that is not going to happen.
--Sanguious
