| Pages: 1 2 [3] :: one page |
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Dukath
   |
Posted - 2006.10.30 14:28:00 -
[61]
When pressing ctrl-q or quitting the game in a clean way the client should send a signal to the server. A clean logout should not result in an emergency warp.
Whether or not people would then plug the network cable is irrelevant. It already takes longer for a ship that really crashed to warp off than someone who quits. So now the loggers will also at least suffer the extra time needed for the server to discover the disconnect.
As an added bonus people would now be able to log off inside a POS bubble even with agression timer. A clean quit means the ships stays inside the pos bubble until it disappears.
PS: no need to say anything about the change when it is implemented, let people who ctrl-q find out the hard way that their ship doesn't warp out anymore :)
|
Swirler
|
Posted - 2006.10.30 14:35:00 -
[62]
Interesting.
In systems with sovereignty, non-aligned players would be denied the ability to log off.
In addition, if they 'crashed' (CTRL-Q) they would log in in the nearest non-sovereign system. And they should be put in a queue to not be able to log back in for 20 minutes.
Couple this with not being able to log off w/o crashing for 20+ minutes if you or your gang killed a player. This might just have the desired effect of keeping players in game and on target, instead of just logging off/crashing themselves.
Ya get where I am going with this? |
ChaosOne
Caldari
DarkStar 1
Ascendant Frontier
|
Posted - 2006.10.30 15:59:00 -
[63]
its quite simple really. if your scrammed or in a warp bubble your ship should not be able to warp off. youve obviously got yourself into that position in the first place, computer crash or ctrl-q should not matter.
to prevent the coincidence of a mass logon it would be easy to make a logon timer that puts you in a ss where your not scanable (a bit like jump cloak), have the timer set for 5-10 mins where you cant activate your hi-slots..
|
Sally
Caldari
R.u.S.H.
Red Alliance
|
Posted - 2006.10.30 16:53:00 -
[64]
Edited by: Sally on 30/10/2006 16:53:59
 Originally by: ChaosOne
its quite simple really. if your scrammed or in a warp bubble your ship should not be able to warp off. youve obviously got yourself into that position in the first place, computer crash or ctrl-q should not matter.
to prevent the coincidence of a mass logon it would be easy to make a logon timer that puts you in a ss where your not scanable (a bit like jump cloak), have the timer set for 5-10 mins where you cant activate your hi-slots..
First part is obviously how it should be, allbeit not with current unstable servers what crash even when 40 man gang jump in a system.
The second part is just stupid - force the peoples to wait 10 min after legitimate logon - is a no-go. Many peoples actually value they time...
--
Stories: #1
--
|
Darth Hammer
Caldari
Centurians
|
Posted - 2006.10.31 01:01:00 -
[65]
Just make it so if a person has a lock on a ship they are engaging the ship that has a target lock on it cant ctl-q.
That would eliminate the problem pretty much.
|
Drusus Rensus
Gallente
Klima Galactic
|
Posted - 2006.10.31 01:46:00 -
[66]
Edited by: Drusus Rensus on 31/10/2006 01:51:28
I think that there are a few things that need to be done together:
1) Forget about timers, I think it would be good if you ship never just "poofed". If you log off in a station, you're in the station. If you log off in space, then your ship just sits there until you log back in. Having it just go "poof" is pretty unrealistic. I generally like realism if there isn't a good faith reason why it would break the game play. Which brings me to my second point:
2) You should be able to "opt out" of local, or at least drop out when you log even if your ship stays in space. You can't really do the above until you do this, since local provides a cheap system wide scanner that alerts hostiles of your ships' presence. If you could opt out of local (meaning you wouldn't be able to see who's in the system, but they wouldn't be able to see you either, you wouldn't really need to have your ship go "poof" when you log in a safe spot.
3) Allow a ship to remain "cloaked" while you're logged off, if it has a cloaking device fitted.
The result of the above would be that if you were going to take a ship deep into hostile territory for an extended period, you'd have to fit a cloaking device, or run the risk of being found by probes while you were logged off. Hostiles could still find you if they happened to see you come into the system, they'd just have to do a laborious grid-wise seek-and-destroy to spot you visually.
There's probably a hole in my reasoning here, since I'm new. Would this work?
|
Raste
Shinra
Lotka Volterra
|
Posted - 2006.10.31 02:32:00 -
[67]
Originally by: Drusus Rensus
Edited by: Drusus Rensus on 31/10/2006 01:51:28
I think that there are a few things that need to be done together:
1) Forget about timers, I think it would be good if you ship never just "poofed". If you log off in a station, you're in the station. If you log off in space, then your ship just sits there until you log back in. Having it just go "poof" is pretty unrealistic. I generally like realism if there isn't a good faith reason why it would break the game play. Which brings me to my second point:
2) You should be able to "opt out" of local, or at least drop out when you log even if your ship stays in space. You can't really do the above until you do this, since local provides a cheap system wide scanner that alerts hostiles of your ships' presence. If you could opt out of local (meaning you wouldn't be able to see who's in the system, but they wouldn't be able to see you either, you wouldn't really need to have your ship go "poof" when you log in a safe spot.
3) Allow a ship to remain "cloaked" while you're logged off, if it has a cloaking device fitted.
The result of the above would be that if you were going to take a ship deep into hostile territory for an extended period, you'd have to fit a cloaking device, or run the risk of being found by probes while you were logged off. Hostiles could still find you if they happened to see you come into the system, they'd just have to do a laborious grid-wise seek-and-destroy to spot you visually.
There's probably a hole in my reasoning here, since I'm new. Would this work?
Because of scan probes, this part is not correct:
"If you could opt out of local (meaning you wouldn't be able to see who's in the system, but they wouldn't be able to see you either, you wouldn't really need to have your ship go "poof" when you log in a safe spot."
But in a hard-core world, #3 provides the solution.
I like it, but no I don't think it'd work because it'd be a pretty radical change and a lot of people would be up at arms. Also given the server instability it'd lead to a lot of ship loss related to server issues/lag/crashing.
|
Conmen
Valiant Logistics Inc.
|
Posted - 2006.10.31 03:33:00 -
[68]
Is this even being talked about? The intentions of the game? how the hell would you knwo the intentions of the game. LOG IN TRAPS PURE BULLL SHIIIIIITTTT. simply logging off in enemy space ot harras them makes perfect sense. Its warfare if you cant keep them from getting in stop complaining about them stayin. Patrol your border bait um into a fight use real tactics other then I BRING 10 TO ONE ODDS SCAN PROBE GO I WIN. Is this the way the game is heading jesus christ sommon sense should take the cake in this
WE ARE THE UBER LEET !*TH CENTURY RP CORP !*THCENTURY STYLE BABY. THANK YOU SHEEDZOR FOR THIS SIG GET PREPARED EVE TO BE WTFOWN |
Drusus Rensus
Gallente
Klima Galactic
|
Posted - 2006.10.31 03:33:00 -
[69]
Quote:
I like it, but no I don't think it'd work because it'd be a pretty radical change and a lot of people would be up at arms. Also given the server instability it'd lead to a lot of ship loss related to server issues/lag/crashing.
I've been thinking about this too. I've never experienced a node crash yet. I have experienced a couple of CTDs. It seems to me that you could handle both scenarios by putting the ship into the equivelent of the reinforced mode that POSes have. Basically if the client and server lost contact with each other for any reason at all other than an "orderly", player requested log-off, the ship would be un-targtetable for the duration of a timer (say 15 minutes) or until the pilot touched the controls, whichever came first.
In the case of a node crash, the timer would start when the node came back up. This would end the race to log back on. Everyone would have a chance to log in and have control of their boats before fighting resumed. It would also take away the option not to come back. If there was a crash and you didn't log back in within the timer duration after the node came back up, your ship would becomes targetable.
In the case of logoffski, the server can recognize an intentional, player requested log-off vs. situations where the client just stops talking to the server. If the player logoffskis, their ship would just be a sitting duck. If it were a legit crash, the timer would come into effect and the player could log back in with an opportunity to take control of their ship and resume the fight.
Would work? Wouldn't work?
|
Conman
CONMAN Enterprise
|
Posted - 2006.10.31 03:35:00 -
[70]
THing is if there is a crew and you log off in real life you would simply have them warping around making it impossible to scan so please stop throwing well things just dont disapear for christ sake the physics in the game dont even make sense and it should god damnit.
I am drunken irish slave hahaha i live
|
| |
|
| Pages: 1 2 [3] :: one page |
| First page | Previous page | Next page | Last page |