Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 1 post(s) |
Baun
4S Corporation Morsus Mihi
|
Posted - 2008.09.29 23:43:00 -
[1]
For the health of this game, CCP needs to have a definitive policy on how to deal with node crashes in PVP situations.
The current system is as follows: 1. Two large forces start fighting each other 2. Too many players come into the system 3. Node crashes 4. After ~1 hour the first players start loading a system. CCP imposes a soft *UNKNOWN* cap on the number of players that can load the system. 5. The fight restarts with a completely different force balance than existed before the node crash in a completely arbitrary way determined by who was lucky enough to get into the system before the soft cap was imposed.
This system makes the game a COMPLETE joke. Inevitably, when the node crashes one side gets Turkey Shot.
CCP needs a clear policy of what to do in this situation so they don't leave their GMs with hundreds of petitions to sort through.
Here is my suggestion: When the node crashes all players should be moved back to the last station that they were docked in and the crashed system should be rendered inaccesible for 8 hours in order to prevent the station's location from being a strategic advantage.
There are alot of flaws to my suggestion, but its a start. CCP needs to step up with this because if all node crashes result in arbitrary ganks with hundreds of players staring at load screens for several hours then this game suffers and we all suffer for it. |
Baun
4S Corporation Morsus Mihi
|
Posted - 2008.09.29 23:43:00 -
[2]
For the health of this game, CCP needs to have a definitive policy on how to deal with node crashes in PVP situations.
The current system is as follows: 1. Two large forces start fighting each other 2. Too many players come into the system 3. Node crashes 4. After ~1 hour the first players start loading a system. CCP imposes a soft *UNKNOWN* cap on the number of players that can load the system. 5. The fight restarts with a completely different force balance than existed before the node crash in a completely arbitrary way determined by who was lucky enough to get into the system before the soft cap was imposed.
This system makes the game a COMPLETE joke. Inevitably, when the node crashes one side gets Turkey Shot.
CCP needs a clear policy of what to do in this situation so they don't leave their GMs with hundreds of petitions to sort through.
Here is my suggestion: When the node crashes all players should be moved back to the last station that they were docked in and the crashed system should be rendered inaccesible for 8 hours in order to prevent the station's location from being a strategic advantage.
There are alot of flaws to my suggestion, but its a start. CCP needs to step up with this because if all node crashes result in arbitrary ganks with hundreds of players staring at load screens for several hours then this game suffers and we all suffer for it.
The Enemy's Gate is Down
|
D'ceet
Omega Fleet Enterprises Executive Outcomes
|
Posted - 2008.09.30 04:22:00 -
[3]
Edited by: D''ceet on 30/09/2008 04:23:44 cynoing in 100 people, on top of the 400 that jumped in, that could have been the straw that broke the camels back... .... .... ....
edit: and we'll crash the node every 8 hours. Your signature is too large. Please resize it to a maximum of 400 x 120 with the file size not exceeding 24000 bytes. If you would like further details please mail [email protected] ~~~Applebabe |
|
CCP Casqade
|
Posted - 2008.09.30 10:37:00 -
[4]
Quote: 4. After ~1 hour the first players start loading a system. CCP imposes a soft *UNKNOWN* cap on the number of players that can load the system.
This is not true, we do not limit the amount of players in the system or log in or load. The reason why people cannot log in is because of the load on the node, much like you used to be unable to log into Jita during Sunday evenings when it was loaded.
|
|
B0rn2KiLL
Black Nova Corp Band of Brothers
|
Posted - 2008.09.30 12:15:00 -
[5]
Edited by: B0rn2KiLL on 30/09/2008 12:15:36 whats stopping people from abusing this mechanic to protect key systems?
say alliance A is running an important poject in system X, Alliance B comes to try and foil their plans and kill their puppies; Alliance A proceeds to request a massive fleet to jump into System X every time Alliance B tries to attack it and insodoing crash it. Rendering system X safe for 8 hours (human sleep cycle time) which restarts then after.
bad idea imo.
good try though. =] ---
Originally by: Oveur It's important to understand that EVE is a "PvP" focused game
|
Philip Jones
Gallente Thundercats RAZOR Alliance
|
Posted - 2008.09.30 13:06:00 -
[6]
Edited by: Philip Jones on 30/09/2008 13:06:42 What we really need is a login system when your ship is the last thing to load. At the moment this is not the case and you are left unable to do anythng and at risk from others.
Your ship really needs to be the last thing that loads after a crash.
System should load, planets and gates etc, then overview should load with all other fully loaded pilots showing in the overview. Then any other items, such as your people and places. Once everything is loaded around you your ship should finally load into the game.
At the moment it seems the ship loads first then everything else while you try to log in.
|
Etien Aldragoran
DarkStar 1 GoonSwarm
|
Posted - 2008.09.30 16:28:00 -
[7]
Originally by: Philip Jones
Your ship really needs to be the last thing that loads after a crash.
This is a good idea in general. I've lost way too many ships while my screen was still black and showing the loading bar. |
Baun
4S Corporation Morsus Mihi
|
Posted - 2008.09.30 16:44:00 -
[8]
Originally by: CCP Casqade
Quote: 4. After ~1 hour the first players start loading a system. CCP imposes a soft *UNKNOWN* cap on the number of players that can load the system.
This is not true, we do not limit the amount of players in the system or log in. The reason why people cannot log in is because of the load on the node, much like you used to be unable to log into Jita during Sunday evenings when it was (over)loaded.
This is what I mean by a soft cap. Perhaps my wording was not delicate enough but what I meant is that your server coding prevents the same number of people who were in before the node crash from logging back in.
One of the principle problems is that people are loaded in game to be turkey shot in these situations while they cannot even play the game to defend themselves. Perhaps think about change the load architecture to prevent them (like Philip is suggesting). SOMETHING clear needs to be done - every other fleet battle is ending in one side shooting defenseless lagged out people and its making this game pointless.
The Enemy's Gate is Down
|
Suicidal Hamster
Hamster Holding Corp
|
Posted - 2008.09.30 17:55:00 -
[9]
Edited by: Suicidal Hamster on 30/09/2008 18:03:37
Originally by: Baun
This is what I mean by a soft cap. Perhaps my wording was not delicate enough but what I meant is that your server coding prevents the same number of people who were in before the node crash from logging back in.
I doubt that there is a soft cap. As I understand - in case of Jita - they limited the number of people who could log in, as the node run out of memory. And that was with a player number of 1400+ .
What happened possibly in your case is that the amount of people and the fleet battle simply overloaded the node CPU wise.
Edit:
Originally by: CCP Lingorm
...system cap only applies to Jita.
I don't think there is anything else to say. I hope the next big fleet battle will be more enjoyable.
|
Baun
4S Corporation Morsus Mihi
|
Posted - 2008.10.06 17:22:00 -
[10]
If that is true then what needs to change is the login mechanic itself. If the node is out of CPU then players should not be permitted to try to load instead of simply dieing at black screen.
The Enemy's Gate is Down
|
|
Ineun
Minmatar House An'geles Wildly Inappropriate.
|
Posted - 2008.10.07 11:46:00 -
[11]
always helps when you have GMs in your alliance that monitor the server and tell the alliance if its about to go under and when its back up.... :) ohai i is your resident Socialist... |
MAX MEXX
|
Posted - 2008.10.07 12:12:00 -
[12]
Originally by: Baun If that is true then what needs to change is the login mechanic itself. If the node is out of CPU then players should not be permitted to try to load instead of simply dieing at black screen.
This seamed realy logical actaly, wy can't cpp do this i have also lost to many ships sitting looking at my blackscreen
|
Car Wars
Destructive Influence Band of Brothers
|
Posted - 2008.10.08 12:29:00 -
[13]
Edited by: Car Wars on 08/10/2008 12:32:52
Originally by: CCP Casqade
Quote: 4. After ~1 hour the first players start loading a system. CCP imposes a soft *UNKNOWN* cap on the number of players that can load the system.
This is not true, we do not limit the amount of players in the system or log in. The reason why people cannot log in is because of the load on the node, much like you used to be unable to log into Jita during Sunday evenings when it was (over)loaded.
Tbh the current system is totally borked, like pointed out by the OP.
Example: m-o node crash: A lot of people including me could not log back into system for 2-3 hours. Looking at character entering system etc. Some people claim that their ship was shootable during this, donĘt know if that is true. (Stuck petitions were ignored and closed and all out service of ccp was truly poor).
Other people that werenĘt in m-o at the moment of the node crash now happily traveled there and jumped in by gate or cyno. Why are these people allowed in before people already there and trying to load? The load on the node argument doesnĘt seem to fly. These players entered system after some loading lag thatĘs it. Think the main issue is that the latter players already have their game fully loaded. And hence get preferred.
People trying to load the system after the node crash should either be preferred over new people jumping in or get at least the same chance.
|
Ametyst
Destructive Influence Band of Brothers
|
Posted - 2008.10.10 19:30:00 -
[14]
Originally by: Ineun always helps when you have GMs in your alliance that monitor the server and tell the alliance if its about to go under and when its back up....
Yeah nobody use the old "click connect" in Eve anymore after a crash |
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |