Forums » General
VO 1.8.91 includes:
- Logoff timer is now increased to 30 seconds if you should receive a private message. The extended logoff period exists for 20 seconds after receiving any incoming message. After waiting the extended countdown period, logoff proceeds normally. This only occurs during flight, not in stations.
- Fixed bug with Linux version where the client didn't use some of the enumerated resolutions correctly.
- Added ability to override window-mode resolution in Linux. For example:
[refgl]
xf86vidmode=0
xsize=1000
ysize=1000
- Fixed crashing sectors.
- Logoff timer is now increased to 30 seconds if you should receive a private message. The extended logoff period exists for 20 seconds after receiving any incoming message. After waiting the extended countdown period, logoff proceeds normally. This only occurs during flight, not in stations.
- Fixed bug with Linux version where the client didn't use some of the enumerated resolutions correctly.
- Added ability to override window-mode resolution in Linux. For example:
[refgl]
xf86vidmode=0
xsize=1000
ysize=1000
- Fixed crashing sectors.
For a more length explanation on the logoff timer thing, see the thread that started it.
For a more lengthy explanation of the Linux resolution problems, see this thread.
Thanks guys! These were the three things that have bothered me the most about VO for the last 3 months, and you apparently fixed all three of them in one update.
Time to go blow up logging ninnies in M-14 while running VO at a resolution that makes sense for my monitor! Wheee!
Time to go blow up logging ninnies in M-14 while running VO at a resolution that makes sense for my monitor! Wheee!
Awesome!
It's about time loggers can no longer get away.
Wow .. is the antialiasing option under linux new?
mr_spuck, New as of Vendetta 1.8.84. Read the motd for that update.
Whoa ..must have missed it.
With the new time thing does /lua Game.Quit() still work correctly? Meaning if you are in the station are you still subjected to this routine? Does /lua Game.Quit() force the quit with out doing the timer?
If it is subjected to these rules then it's possible that some abusive groups could easily msg you every few seconds and prevent you from logging off.
This feature will become very annoying very fast for many due to the way it works. It also encourages bad behavior which VO does not need at all.
Also how does this get affected by /lua ReloadInterface() then /lua Game.Quit() ?
If it is subjected to these rules then it's possible that some abusive groups could easily msg you every few seconds and prevent you from logging off.
This feature will become very annoying very fast for many due to the way it works. It also encourages bad behavior which VO does not need at all.
Also how does this get affected by /lua ReloadInterface() then /lua Game.Quit() ?
IIRC /lua Game.Quit() is in this case similar to just force quitting vo
ie. your ship stays in space for a minute or so anyway.
I'm not entirely sure tho.
ie. your ship stays in space for a minute or so anyway.
I'm not entirely sure tho.
I was trying to decode the exact conditions for the 30 second increase with little success last night. I started a countdown, aborted it myself with a turbo, then received a private message. When I tried the logout again it had increased to 30 seconds.
What are the exact conditions that cause the increase to 30 seconds, and more importantly, how long before it kicks back to 10?
What are the exact conditions that cause the increase to 30 seconds, and more importantly, how long before it kicks back to 10?
I actually think it's broken. A message coming over 100 aborted my log off last night, just by a "gf" message. lol
vskye, the 30 second msg will not abort logoff. Something else must've aborted it.
tumblemonster, your test result seemed correct.
blacknet, the timer shouldn't be affected by ReloadInterface() and does not apply when you are logout in-station.
It works like this:
When you receive a private message, your logout timer changes to 30 seconds. If you are already logging out, then the timer is reset to 30 seconds but continues to count down.
If you try logging out within 20 seconds, you will get the 30 second timeout. Once 20 seconds has passed, the timer will change back to the 10 second timer.
tumblemonster, your test result seemed correct.
blacknet, the timer shouldn't be affected by ReloadInterface() and does not apply when you are logout in-station.
It works like this:
When you receive a private message, your logout timer changes to 30 seconds. If you are already logging out, then the timer is reset to 30 seconds but continues to count down.
If you try logging out within 20 seconds, you will get the 30 second timeout. Once 20 seconds has passed, the timer will change back to the 10 second timer.
I can't believe this was actually implemented.
Does a private message reset logout 30 second timer or the cooldown 20 second timer? If so then that needs to be fixed. One private message should set the logout timer to 30 seconds and the "cooldown" timer to 20 seconds. This will should only happen once. After the cooldown timer is finished and the logout is set to 10 seconds again, a cooldown period should be set to at least 5 seconds, at the most 10 seconds. During this period no private messages will incur the 20 second logout penalty.
I haven't been on in awhile, but if you're hit and the logoff timer doesn't stop, it probably should.
Also, private messages in this way should only work if you're in the same sector as the person you were private messaged. It might also be a good idea to disable the logoff for 5-10 seconds after a jump has been complete, in-system jump or otherwise.
Does a private message reset logout 30 second timer or the cooldown 20 second timer? If so then that needs to be fixed. One private message should set the logout timer to 30 seconds and the "cooldown" timer to 20 seconds. This will should only happen once. After the cooldown timer is finished and the logout is set to 10 seconds again, a cooldown period should be set to at least 5 seconds, at the most 10 seconds. During this period no private messages will incur the 20 second logout penalty.
I haven't been on in awhile, but if you're hit and the logoff timer doesn't stop, it probably should.
Also, private messages in this way should only work if you're in the same sector as the person you were private messaged. It might also be a good idea to disable the logoff for 5-10 seconds after a jump has been complete, in-system jump or otherwise.
Also, if every time you log in Vendetta gives you a dose of high energy alpha radiation, that should be fixed.
Why it wasn't just changed to 30 seconds anytime you're logging off in space is beyond me.
We're looking into it. The timeout change wasn't thought through 100%. Some specific scenarios weren't covered.
K.I.S.S.
You can also msg yourself to incur the 30 second wrath.