Forums » Suggestions
Followed on from this thread: https://www.vendetta-online.com/x/msgboard/2/30877
Add an Icon near the target box, or a text notification (which ever is easier!) if your current target tries to /logoff in space. Something like this might work.
Or anything really.
Add an Icon near the target box, or a text notification (which ever is easier!) if your current target tries to /logoff in space. Something like this might work.
Or anything really.
-1 overly beneficial to pirates. Rather than change the game, how about you change the way you pirate? (shoot sooner)
+1
I thought you're opposed to griefing, greenie? This is a change that would encourage less griefing and real RP pirating rather than just shooting people to death over and over... Boring.
I thought you're opposed to griefing, greenie? This is a change that would encourage less griefing and real RP pirating rather than just shooting people to death over and over... Boring.
Please explain how this would reduce griefing.
Does the logoff timer no longer work or not work with mobile where doing damage or changing the velocity of the ship cancels the logoff? If that is no longer functioning, then I would suggest fixing that problem rather than adding a notification.
I can however see some benefit to such a notification in that it enables the pirate to be more patient with new players on mobile devices that may be having trouble sorting out how to respond to the threat, while also allowing a faster response against players that disengage by logging.
0 becasue I think the current solution is sufficient and don't see enough in the way of added value. If it's a quick easy change, then yeah, why not give a bit of low hanging fruit.
Edit: +1 if the loff off disruption for mobile cannot be repaired.
I can however see some benefit to such a notification in that it enables the pirate to be more patient with new players on mobile devices that may be having trouble sorting out how to respond to the threat, while also allowing a faster response against players that disengage by logging.
0 becasue I think the current solution is sufficient and don't see enough in the way of added value. If it's a quick easy change, then yeah, why not give a bit of low hanging fruit.
Edit: +1 if the loff off disruption for mobile cannot be repaired.
-1 This wouldn't add anything to gameplay. Joyless... shooting ships is not griefing. This is vendetta, lol.
Now, I'd support knowing whether or not a person you've seen in the last 10 minutes has logged off. Sometimes I wonder if I'm hunting prey that already logged.
Now, I'd support knowing whether or not a person you've seen in the last 10 minutes has logged off. Sometimes I wonder if I'm hunting prey that already logged.
I'd rather know a target is not loging out, so I can not shoot them. As it stands I just shoot them all regardless. I would love to go back to the times when I could hail a target with demands, and they would stop and go "ok, i'll pay" and actually pay. These days there are too many smart asses around, and they go poof and vanish. So rather than demand stuff, I just shoot till they are dead.
@ Death Fluffy.
The damage thing only makes them have to type /logoff again, and it will not abort the countdown again, even if you shoot them. And if they have said "OK, I will pay!!!" then yeah.
Same with hailing them, you have to do it AFTER they type /logoff, and how are you going to know to do this? It only makes them wait longer, or type /logoff again. You get no indication they are trying to escape death. Also the movement thing only ever was "if they moved" AKA, if they press any movement keys, it aborts the logoff. Since collision damage was nerfed, ramming them is not an option.
@ Greenwall.
Yes, this would stop me shooting people on sight. It might not stop me being an ass, but it may bring me back to demanding stuff rather than just shooting outright "just in case".
[edit]
Also @ Greenwall - are you dumb? sorry for asking this, but 10 seconds is enough time to kill someone outright, it is not enough time for everyone to work out the /givemoney command for the first time. Shooting sooner is not a valid option, especially if you have already shot them to 5%...
@ Death Fluffy.
The damage thing only makes them have to type /logoff again, and it will not abort the countdown again, even if you shoot them. And if they have said "OK, I will pay!!!" then yeah.
Same with hailing them, you have to do it AFTER they type /logoff, and how are you going to know to do this? It only makes them wait longer, or type /logoff again. You get no indication they are trying to escape death. Also the movement thing only ever was "if they moved" AKA, if they press any movement keys, it aborts the logoff. Since collision damage was nerfed, ramming them is not an option.
@ Greenwall.
Yes, this would stop me shooting people on sight. It might not stop me being an ass, but it may bring me back to demanding stuff rather than just shooting outright "just in case".
[edit]
Also @ Greenwall - are you dumb? sorry for asking this, but 10 seconds is enough time to kill someone outright, it is not enough time for everyone to work out the /givemoney command for the first time. Shooting sooner is not a valid option, especially if you have already shot them to 5%...
+1. The game should also notify us if the player is within 30 seconds of being despawned due to a dropped connection.
@Death Fluffy: No, the current solution is not sufficient. You have to remember that we're talking about newbies, and more often than not, mobile newbies. Newbs don't know about things like interrupting logout timers, and their chat area is so small that we really can't do much explaining while pirating them or they'll just get more confused as things scroll off faster than they can read. Meanwhile we have to start shooting them to keep them from logging out, and since they don't know what's happening, they'll panic and think we've lost patience and are killing them.
This suggestion doesn't hurt anything, it mitigates a vector for cheating, and it would result in fewer newbs ending up frustrated and dead.
@Death Fluffy: No, the current solution is not sufficient. You have to remember that we're talking about newbies, and more often than not, mobile newbies. Newbs don't know about things like interrupting logout timers, and their chat area is so small that we really can't do much explaining while pirating them or they'll just get more confused as things scroll off faster than they can read. Meanwhile we have to start shooting them to keep them from logging out, and since they don't know what's happening, they'll panic and think we've lost patience and are killing them.
This suggestion doesn't hurt anything, it mitigates a vector for cheating, and it would result in fewer newbs ending up frustrated and dead.
Yoda and Pizzasgood... why not just suggest removal of the option to log off from the user interface when not docked in station? Now that we have stations throughout space where tridents can dock, let's just get rid of the option to log off when we are not in the station. This also would keep tridents and all players that are being chased from disappearing. Everyone would equally have to safely make it to a station in order to log off instead of cheating a chaser of their pk (obviously, people who 'get' disconnected would have to time out eventually, but hopefully not for a long long time).
Edited to add... if you time out, your ship should be put in the nearest available station that you have docking privileges when you log back in
Edited to add... if you time out, your ship should be put in the nearest available station that you have docking privileges when you log back in
+1 for the OP. I am convinced.
"Yoda and Pizzasgood... why not just suggest removal of the option to log off from the user interface when not docked in station?"
Well, that's a bit excessive since people do need a way to exit the game quickly if real life happens, even if they're deep in hostile territory where there aren't any friendly stations. Something like persistant ships would work better, and I do support that. However, although that is a more comprehensive fix, it also impacts a lot more people and is therefor less likely to be supported than Yoda's more restricted change. I would prefer persistence, but logout-attempt notifications are better than nothing.
Well, that's a bit excessive since people do need a way to exit the game quickly if real life happens, even if they're deep in hostile territory where there aren't any friendly stations. Something like persistant ships would work better, and I do support that. However, although that is a more comprehensive fix, it also impacts a lot more people and is therefor less likely to be supported than Yoda's more restricted change. I would prefer persistence, but logout-attempt notifications are better than nothing.
Christ.
@ biretak, I do think that would solve this problem and have suggested similar in the past. But although there are stations in every system, not everyone can dock everywhere.
For example: Even without a capship my current character of choice can only dock at Corvus and Orion stations. If I was in Edras, I would have to fly all the way to Bractus before I could dock to log off. Not practical if I have to shoot off somewhere.
Also placing the player in the nearest station with docking rights is a bit of an exploit waiting to happen too. My suggestion does not change the game that much for anyone, except those who use /logoff as a way to avoid combat.
For example: Even without a capship my current character of choice can only dock at Corvus and Orion stations. If I was in Edras, I would have to fly all the way to Bractus before I could dock to log off. Not practical if I have to shoot off somewhere.
Also placing the player in the nearest station with docking rights is a bit of an exploit waiting to happen too. My suggestion does not change the game that much for anyone, except those who use /logoff as a way to avoid combat.
Good points pizzasgood and yoda. Instead of adding something to the user interface, maybe it would be easier to cancel log off if another player is within 3000m? Sounds as simple as a line of code.
Yeah, I'm fine with forbidding logouts while other players are within some distance. That doesn't address the broken connection issue though, unless the current one-minute disconnect persistence is extended to two-minutes while player ships are within that proximity. (One minute isn't quite enough to distinguish noobs from cheaters, but two minutes should be.)
It would not really need something adding to the UI either. Like I said, a text message in the chat box would work.
*** Your target has initiated logoff (better wording maybe - but this should be simple enough, the client already sends a message when it intends to log out)
As far as lag outs go, that is harder to display a message about, as neither the client not the server would know if the target was simply dropping packets or actually disconnected. Extending the "ship spinny in space" to two minutes could achive this though.
*** Your target has initiated logoff (better wording maybe - but this should be simple enough, the client already sends a message when it intends to log out)
As far as lag outs go, that is harder to display a message about, as neither the client not the server would know if the target was simply dropping packets or actually disconnected. Extending the "ship spinny in space" to two minutes could achive this though.
Should it also send a message if the intended target has initated a log out prior to being targeted or during an occulsion gap?
Fluffy, echoing the logoff messages to sector chat would solve that and sounds simple enough...
<kennyb> 10
<kennyb> 9
etc
<kennyb> 10
<kennyb> 9
etc
Yeah, sector messages are the way to go.
"As far as lag outs go, that is harder to display a message about, as neither the client not the server would know if the target was simply dropping packets or actually disconnected."
Nah, there's already a convention for this, which is used for despawning people if their client goes 60 seconds without communicating with the server. All it would need to do is to send a sector message when it's 30 seconds away from taking that action. If they suddenly start communicating again, it can just send a new "timeout averted" message, the same as it would if somebody was trying to logout but then aborted.
"As far as lag outs go, that is harder to display a message about, as neither the client not the server would know if the target was simply dropping packets or actually disconnected."
Nah, there's already a convention for this, which is used for despawning people if their client goes 60 seconds without communicating with the server. All it would need to do is to send a sector message when it's 30 seconds away from taking that action. If they suddenly start communicating again, it can just send a new "timeout averted" message, the same as it would if somebody was trying to logout but then aborted.
Rather than adding an immersion breaking notice for something like that, just adjust the rules for logging out/dropped connection. Retain the existing dropped connection rules, but when they are about to be disconnected check if there is a PC within 1km. If there is, delay the disconnect until that condition is no longer met (poll every 10 seconds after[?] and perhaps exclude PCs that are in the player's group/guild).
If the player tries logging out within range of someone that meets the aforementioned condition while not docked at a station, warn them that is it not safe to log off, but don't deny them the ability to do so.
If the player tries logging out within range of someone that meets the aforementioned condition while not docked at a station, warn them that is it not safe to log off, but don't deny them the ability to do so.