Pages: 1 2 3 4 5 6 7 [8] 9 10 11 12 .. 12 :: one page |
|
Author |
Thread Statistics | Show CCP posts - 5 post(s) |
Manks Girl
|
Posted - 2010.02.09 13:40:00 -
[211]
Originally by: Tarhim
Originally by: Manks Girl
"On January 28, CCP disabled safety protocols (emergency warp, despawn, inter-node synchronicity) to keep the node from dying. A few days later, CCP Atlas states that it was a fix for the bug that was causing the node to crash"
You are quoting someone's half-baked guess about what CCP did.
Quote:
Unbelievable that the paying subscribers entering the lagfest of the current Sov Warfare werent told and explained to that if u log off the emergency warp protocols wouldnt work. This is blatantly what happened.
And you know it how?
Because i lost a dread 1.5hours after logging as well as another 100+ people did, and this wasnt the first report. Also happened to PL.
|
Tarhim
Caldari
|
Posted - 2010.02.09 14:02:00 -
[212]
Originally by: Manks Girl
Because i lost a dread 1.5hours after logging as well as another 100+ people did, and this wasnt the first report. Also happened to PL.
Actually only thing you can know for sure is that massive lag happened and affected outcome of battle. Because of this lag you can't really trust timestamps, too.
Any guesses if CCP-applied fix made matters worse or better, of if massive crash cascade would be more or less "objective" are just that, guessed.
Idea that fix amounted to direct meddling with important for players safety protocols doesn't really sit well with anything that CCP said and we can't exactly check if they are lying. However, if they'd want to lie why not go all the way and deny any interference with node?
I'd probably be pretty ****ed too if I lost capital ship and battle through no fault of my own, but that doesn't mean I'd drawn false conclusions.
|
Skaarl
|
Posted - 2010.02.09 14:11:00 -
[213]
Originally by: Tarhim
Originally by: Manks Girl
Because i lost a dread 1.5hours after logging as well as another 100+ people did, and this wasnt the first report. Also happened to PL.
Actually only thing you can know for sure is that massive lag happened and affected outcome of battle. Because of this lag you can't really trust timestamps, too.
Any guesses if CCP-applied fix made matters worse or better, of if massive crash cascade would be more or less "objective" are just that, guessed.
Idea that fix amounted to direct meddling with important for players safety protocols doesn't really sit well with anything that CCP said and we can't exactly check if they are lying. However, if they'd want to lie why not go all the way and deny any interference with node?
I'd probably be pretty ****ed too if I lost capital ship and battle through no fault of my own, but that doesn't mean I'd drawn false conclusions.
you have noticed that CCP atlas has been changing his blog and walking his comments back from "we took measures that would make a system admin faint" to "oh it was just a bug fix, we didnt actually do anything..."
they have admitted to doing things, they know they did things wrong and gave an advantage to the side who has also changed its story pretty steadily from the day it happened (we had no grid load or module lag to it was horrible for us too!), and CCP will have to admit that they made a mistake. they screwed things up; they need to man up and try to repair their reputation. they obviously don't know the consequences of their actions since they cant even get nodes stable with noone in them today.
add in the fact that there are still petitions open on this 11 days later with no replies, and the people who have gotten some sort of replies its been a canned response or a fairly snotty reply from a GM and you can understand why as customers we are ****ed.
oh, and the 1.5 hours later part? a cov ops ship watched the dreads show up on grid an hour after the logout was called if i remember. was yelling it out on vent and people were loggin in alts to try and get the ghosts to despawn. it wasnt just bad time stamps.
|
Manks Girl
|
Posted - 2010.02.09 14:27:00 -
[214]
Originally by: Tarhim
Originally by: Manks Girl
Because i lost a dread 1.5hours after logging as well as another 100+ people did, and this wasnt the first report. Also happened to PL.
Actually only thing you can know for sure is that massive lag happened and affected outcome of battle. Because of this lag you can't really trust timestamps, too.
Any guesses if CCP-applied fix made matters worse or better, of if massive crash cascade would be more or less "objective" are just that, guessed.
Idea that fix amounted to direct meddling with important for players safety protocols doesn't really sit well with anything that CCP said and we can't exactly check if they are lying. However, if they'd want to lie why not go all the way and deny any interference with node.
I'd probably be pretty ****ed too if I lost capital ship and battle through no fault of my own, but that doesn't mean I'd drawn false conclusions.
We have to come to some conclusions as CCP are back tracking everytime they mention anything. But using common sense and reading up on their previous tests and statements 2+2 = 4 surely.
All things being equal the simplest answer is normally the right one. Its obvious that there is a bug in the Node for big fleet engagements which has been admitted by CCP Atlas, however under their reimbursement policies "bugs" which pilots have no control over should be entitled and eligible for a reimbursement.
CCP cannot deny these people and myself reimbursement.
|
Skaarl
|
Posted - 2010.02.09 14:37:00 -
[215]
Originally by: Manks Girl
Originally by: Tarhim
Originally by: Manks Girl
Because i lost a dread 1.5hours after logging as well as another 100+ people did, and this wasnt the first report. Also happened to PL.
Actually only thing you can know for sure is that massive lag happened and affected outcome of battle. Because of this lag you can't really trust timestamps, too.
Any guesses if CCP-applied fix made matters worse or better, of if massive crash cascade would be more or less "objective" are just that, guessed.
Idea that fix amounted to direct meddling with important for players safety protocols doesn't really sit well with anything that CCP said and we can't exactly check if they are lying. However, if they'd want to lie why not go all the way and deny any interference with node.
I'd probably be pretty ****ed too if I lost capital ship and battle through no fault of my own, but that doesn't mean I'd drawn false conclusions.
We have to come to some conclusions as CCP are back tracking everytime they mention anything. But using common sense and reading up on their previous tests and statements 2+2 = 4 surely.
All things being equal the simplest answer is normally the right one. Its obvious that there is a bug in the Node for big fleet engagements which has been admitted by CCP Atlas, however under their reimbursement policies "bugs" which pilots have no control over should be entitled and eligible for a reimbursement.
CCP cannot deny these people and myself reimbursement.
sure they can. just like we as customers can deny them access to credit cards every month.
|
Hast
The Illuminati. Pandemic Legion
|
Posted - 2010.02.09 16:30:00 -
[216]
so glad I cancelled all of my accounts. I have been a player for six years now, pretty much to the day (4th of february iirc) but now I'm gone, for good.
Originally by: omeega PICTURE TOO BIG, KGB INCOMING HAVE FUN.
|
Jonas Trelonian
|
Posted - 2010.02.09 16:37:00 -
[217]
Better late than never - it "only" took two months for CCP to acknowledge these issues!
The majority of people raging in this thread (and others) are angry. And most of this anger is directed at CCP - not for broken game mechanics, but for consistently ignoring the players. Us. Your customers. The guys who pay your salaries at the end of the month.
After Dominion was released, people complained almost immediately that there were issues. CCP said nothing, merely issued patches that failed to fix said issues and introduced others. This is not the first time the playerbase has been subjected to such sloppy coding, but what annoys me most is that CCP failed to admit to this.
It is not a failure to admit that you ****ed up. It is, however, a failure to not learn something from such an experience - and CCP have continuously done this. Time after time, something breaks, we players ask for answers, and we get nothing. Do you think we're asking for information because we're bored? No, it's because we want to know what's going on - because we have a right to know!
CCP: Talk. To. Your. Players. And when you do something crazy like meddle with a node in the middle of a huge fleet fight - the result of which is a one-sided battle where many players died without even firing a shot - then you must be ready to reimburse players who justly believe that your game, and hence you, have failed them.
tl;dr: CCP, stop behaving like ****s.
|
Horrible Horris
|
Posted - 2010.02.09 16:38:00 -
[218]
People can deny them access to their credit card information every month, the reality of it is though that they won't. Why? Because they live in the vain hope that CCP will eventually deliver what they promise in fleet fights etc.
Admitedly some issues are unforseen, although the massive fleet engagements that are now becoming common place due to Titan and Sov changes changes was obvious
AOE Titan = Null : Bigger gangs (admittedly better fits available now) - Obvious Sov Changes, SBU's : Gate engagements - Obvious POS's : apparently no longer required in game mechanics as the new Sov fixes everything - wrong.... JB's, moon goo, &c. &c. - and it costs even more to have Sov now as you need pos's still
My main was in WI when this was first noticed, the first major fleet engagement after the Dominion patch - there was no where near the numbers on the 28th Jan, however it was pretty evident then that something was wrong. Yet WI got flamed for mentioning it, fail cascade, call it what you will, it was so obvious something was wrong, yet CCP refused to listen or even act on it. Since then so many alliances have spoken up about it (with obvious trolls of fail FCs &c from the fearless opposition) that CCP finally has had to listen.
It is such a shame that it has taken so long to: A) recognise that there is an issue B) actually begin to do something about it.
The recognition of the fact that there is a problem does not help those who have spent time and isk in bringing it to light (well those who have lost assets anyways), "our logs show nothing" is common place, ship reimbursement for major fleet battels will probably never happen due to this statement, although I did lose a drake to 48 damage - and I have the KM to prove it, yet apparently their logs do not show a problem... Maybe I should take off the large shield debuffer II
100 caps destroyed with no losses is the single biggest failure to date, no FC is that bad - even I am not that bad - and I don't FC - I would have taken at least something down!
As High Sec is unaffected by the changes to the Sov mechanics, there is little support from those living there, maybe it will take a bunch of alliances to neut each other to get into position and war dec in empire to show the rest of the community the unplayabe conditions that are becoming more and more apparent in null sec space
Their stance is disappointing and their failure to compensate those who pay to play the game when the failure is so apparent is equally disappoiniting. Personally I am thinking of moving on, I am tired of the promises that are given, the snazzy trailers showing high combat scenarios yet the delivery being less than acceptable, if not flawed.
Someone posted earlier that we don't pay to beta test, how very true, but CCP seem to rely on that and the player base to write useful documentation for them, hopefully one day they will realise that there is only so much people can endure, the stick and carrot will only work for a short while, then you just go to sleep.
Its a shame - but its only pixels, if only space ones
|
Skaarl
|
Posted - 2010.02.09 16:55:00 -
[219]
out of curiousity who were PL and WI fighting when this happened to them?
|
Mankell Grenze
The Illuminati. Pandemic Legion
|
Posted - 2010.02.09 17:05:00 -
[220]
Edited by: Mankell Grenze on 09/02/2010 17:12:13
Quote: out of curiosity who were PL and WI fighting when this happened to them?
*edited for really bad spelling...
CCP Developers.
*pretends dominion is all about capital fights *toys with the node during a battle *one side gets killed (3-4 times in different regions) and the other side takes no losses *pretends it was even for everyone *doesn't reimburse any fleet fights (can hardly call these a fleet fight when only one side gets to push buttons) *CCP atlas posts that there's a fix coming for the node bugs *CCP atlas backpedals a thousand times in a single thread *same ****, different day
Oh the joy of paying and having to read such posts/petitions, doesn't make you bitter does it.
|
|
Skaarl
|
Posted - 2010.02.09 17:09:00 -
[221]
Originally by: Mankell Grenze
Originally by: Skaarl Edited by: Skaarl on 09/02/2010 16:57:04 out of curiosity who were PL and WI fighting when this happened to them?
*edited for really bad spelling...
CCP Developers.
...
i *know* that, was curious what alliance(s)
the fact that we have all lost to the CCP dev team is a valid answer however.
|
Future Mutant
Republic Military School
|
Posted - 2010.02.09 17:19:00 -
[222]
What morons decided to stuff 1600 ppl into a system? What did you think was going to happen? Well guess what? It happened- deal with it.
For those who are saying theyre unsubbing. Thank god-i hope that means less whining.
To everyone else- yes you got a bad hand. Man up. Or accept your a 6 yr old girl and leave.
|
Severion Atarkos
|
Posted - 2010.02.09 17:23:00 -
[223]
Edited by: Severion Atarkos on 09/02/2010 17:24:43
Originally by: Skaarl
Originally by: Mankell Grenze
Originally by: Skaarl Edited by: Skaarl on 09/02/2010 16:57:04 out of curiosity who were PL and WI fighting when this happened to them?
*edited for really bad spelling...
CCP Developers.
...
i *know* that, was curious what alliance(s)
the fact that we have all lost to the CCP dev team is a valid answer however.
PL were fighting IT/pets/-A- etc, not sure about who WI were fighting.
I just don't understand how they can admit that there server is ******, but still will not reimburse the losses that were suffered from obvious server failures.
So they are pretty much saying "We don't care about you, yes the servers were broke and protocols were not working as intended and the battle was totally one sided and did not affect all sides equally but we won't reimburse you for our screwups and we just cannot understand why you the playerbase cannot accept this"
Well CCP like people have stated above, you could save whatever dignity you have left by doing the right thing and reimbursing the losses that insued from your bug. Rather then taking the route you are which will result eventually ruin your game.
|
Skaarl
|
Posted - 2010.02.09 17:26:00 -
[224]
Originally by: Severion Atarkos Edited by: Severion Atarkos on 09/02/2010 17:24:43
Originally by: Skaarl
Originally by: Mankell Grenze
Originally by: Skaarl Edited by: Skaarl on 09/02/2010 16:57:04 out of curiosity who were PL and WI fighting when this happened to them?
*edited for really bad spelling...
CCP Developers.
...
i *know* that, was curious what alliance(s)
the fact that we have all lost to the CCP dev team is a valid answer however.
PL were fighting IT/pets/-A- etc, not sure about who WI were fighting.
I just don't understand how they can admit that there server is ******, but still will not reimburse the losses that were suffered from obvious server failures.
So they are pretty much saying "We don't care about you, yes the servers were broke and protocols were not working as intended and the battle was totally one sided and did not affect all sides equally but we won't reimburse you for our screwups and we just cannot understand why you the playerbase cannot accept this"
Well CCP like people have stated above, you could save whatever dignity you have left by doing the right thing and reimbursing the losses that insued from your bug. Rather then taking the route you are which will result eventually ruin your game.
i think PL were fighting the same people. its amazing to me that -a- never suffers the negative effects in this, yet anyone who fights them does.
|
Jonas Trelonian
|
Posted - 2010.02.09 18:00:00 -
[225]
@Horrible Horris: I'm a hi-sec carebear (this is a forum alt if you hadn't already guessed ;) ) and although I am (mostly) unaffected by Dominion (except for the DB crashes and random disconnects), I'm not prepared to sit silent on the sidelines while CCP ****es off their paying players. If everyone sits back and does nothing, how long will it be before everyone in the game is affected by CCP's refusal to fix that which is obviously flawed?
Besides, a game that is broken in one aspect is still a broken game, and I don't like paying for things that are broken.
|
Xikorita
Mob Thought Phalanx Alliance
|
Posted - 2010.02.09 18:05:00 -
[226]
I participated in some big fleet battles and had everything turned off. It seemed so fun if I could use my modules and all. Thankfully I left that kind of fight from the dominion trailer to small roams.
It is a shame that big fleets (im talking 200v200) doesn't work at all.
|
Imran
Sniggerdly Pandemic Legion
|
Posted - 2010.02.09 18:12:00 -
[227]
WTB shoe throw at next fan fest. __________________________________________ EwokPoacher: Why hate Gallente? Blackest Sheep: Because we are beautiful.
|
San Ti
Gallente The Illuminati. Pandemic Legion
|
Posted - 2010.02.09 19:05:00 -
[228]
Originally by: CCP Atlas Eve has never been able to support anywhere close to 1600 person fleet fights and we have never claimed to support those numbers. Hopefully we are heading in that direction with some of the optimizations that are in the works but we're not there yet.
Originally by: Batolemaeus Even if the cluster behaved like before dominion and even if you get fights up to 1.5k under control, your failure in game design will produce higher and higher numbers until the nodes break again.
|
Camios
Minmatar Insurgent New Eden Tribe Systematic-Chaos
|
Posted - 2010.02.09 21:11:00 -
[229]
Edited by: Camios on 09/02/2010 21:12:06
Originally by: Kanuo Ashkeron
Originally by: CCP Atlas
Eve has never been able to support anywhere close to 1600 person fleet fights and we have never claimed to support those numbers. Hopefully we are heading in that direction with some of the optimizations that are in the works but we're not there yet.
DonŠt do that. I donŠt know how old you are. But can you remember the days with hard disks less than 1GB (probably you can remember the days of hard disks with like 10MB). Most of the time we were quite happy, then mp3 files were used and shared, and out of a sudden there was too less space for all the music. Luckily Seagate et al were not lazy, and gave us hard disks with 50-100 GB and we had plenty of space, however at the same time we started to save movies (not that anybody could watch all the movies he has stored now) and again, hard disk space was scarce. And this will continue to the end of days.
I hope you get the idea, the same will happen with the servers. Just adding performance wont solve the problem.
Camius had some nice ideas in the F&I forum and I added something similar. And as you (CCP) said: Game designers are cheaper then Programmers (on the other hand it might be a good idea to spend some money on a really designer).
Hi 5 mate! Yes, I strongly believe that a change in gameplay mechanics is the only thing that will fix lag once for all. Here is my analysis and proposal on a possible final fix of lag by game design.
We strongly need a mechanic that advantages splitting forces between many solarsystem, while the current mechanic encourages focus fire.
|
Hannibell
Genco Curatores Veritatis Alliance
|
Posted - 2010.02.09 21:23:00 -
[230]
Originally by: Lykouleon
3) Your completely disregarding the facts that Atlas has outlined: that no game mechanics were affected during the fleet fight.
What Fleet fight? There was never any Fleet fight at the SBU. All Capitals Logged BEFORE ANY REDS WERE EVEN ON GRID, and yet reappeared in 1s and 2s later (a fact confirmed by multiple pilots on multiple forums and even seen in several fraps) LONG after they had logged off.
I've been playing this game for 6 years, what happened in D-G violated every game mechanic with respect to log off in play, and then CCP ADMITS they were monkeying with the node settings all the while.
Calling it now... CCP Atlas is actually Mohammed Saeed al-Sahhaf
|
|
Skaarl
|
Posted - 2010.02.09 21:48:00 -
[231]
Originally by: Hannibell Edited by: Hannibell on 09/02/2010 21:26:06
Originally by: Lykouleon
3) Your completely disregarding the facts that Atlas has outlined: that no game mechanics were affected during the fleet fight.
What Fleet fight? There was never any Fleet fight at the SBU. All Capitals Logged BEFORE ANY REDS WERE EVEN ON GRID, and yet reappeared in small groups later (a fact confirmed by multiple pilots on multiple forums from both sides and even seen in several fraps) hours after they logged off to be slaughtered while not even in game. Apparently you dont understand the definition of the word 'fight' any better than CCP does.
I've been playing this game for 6 years, what happened in D-G violated every game mechanic with respect to log off in play, and then CCP ADMITS they were monkeying with the node settings all the while.
Calling it now... CCP Atlas is actually Mohammed Saeed al-Sahhaf
now now. its Comrade Atlas and dont you dare accuse him of handing victory after victory to -a-.
|
Gabriel Virtus
hirr
|
Posted - 2010.02.09 22:41:00 -
[232]
This is why I love CCP. You guys fail at some things, but the subtle comedy makes me love you. Please pay attention to the local window in the example eve screen:
Eve Player #1 > OMG, the lag is terrible!!! Eve Player #2 > Common, CCP is on it! Eve Player #3 > I can't jump in, LOL! But I still love CCP Eve Player #4 > I know CCP are doing everytthing they can to fix this Eve Player #5 > Yeah, CCP is pretty cool Eve Player #6 > If anyone can fix this lag, CCP can!
Besides a complete disregard to actual locals during these circumstances, I commend CCP's effort to in subliminal messenging and would like to admit that it has worked. Thanks for the efforts CCP
-GV
|
Mah Kraah
Minmatar Masuat'aa Matari Ushra'Khan
|
Posted - 2010.02.09 23:52:00 -
[233]
generaly the devs are right when saying that lag and loadissues are random. in the fight we talk about here, -a- entered system 3+h bevore the fight to avoid that system and grid load problem. " as if someone told them exactly how to play around the problems(accusing ccp of taking sides)" well we did 2 weeks of intensive tests in 49 with stressed out servers and several nodecrashes just a few days bevore that d-g fight, thats why we knew what to avoid. "the attacker know when he attack the defender dont know when to defend so defender is screwed" BS, the dominion sov system gives the defender 4 timers. he know 4 times in a row, more than a day ahead, exactly at what minute he has to defend and he has the luxory to screw up 3 times and if he does everything right at only one of the timers he has won already. cva knew 2 days in advance when to be in system and when to force -a-to jump into them. cva where even in system and had already loaded system and grid but jumped out of system to jump back in again, exactly that was the moment they removed the randomness from the problem: one party loaded one party not. not the code, not the dev in system , cva s decission made the problem a onesided one. jumping in 150 caps at once and jumping in the in-system support fleet to the same location resuts in many thousend database read and write acessrequests landing in a que on a cpu that is already far beyond 100% usage...... they had to load system and than grid while -a- had to load grid only and than started to shoot and added to the problem by doing so.
making ships apear in system and on grid only AFTER the client report that he has finished loading would solve half of the problem.
logged off ships died houres later: thats a fishy one. if a client is unresponsible the server warps a ship to save, the well known emergency warps we all experiance from time to time. same if he loose connection or logs off. i give it 15 min max excuseable time for server beeing slow, anything that died after that has to be reimbursed because reason for the ship loss was a server no longer acting as intended. even having to discuss with gm when it comes to 30m 40m 1h afterwards is a shame.
the server know when the client was sending last data and the server know when he decided that this ship is dead. if logs dont show such problems than the log creating mechanics need to be fixed, it costs ccp nothing to reimburse such obvious malfunction caused losses why not just doing it? at least than u reduce the dammage done to a pilot caused by things he has no influence on.
|
Ban Doga
|
Posted - 2010.02.10 00:29:00 -
[234]
Edited by: Ban Doga on 10/02/2010 00:31:02
Originally by: Mah Kraah generaly the devs are right when saying that lag and loadissues are random. in the fight we talk about here, -a- entered system 3+h bevore the fight to avoid that system and grid load problem. " as if someone told them exactly how to play around the problems(accusing ccp of taking sides)" well we did 2 weeks of intensive tests in 49 with stressed out servers and several nodecrashes just a few days bevore that d-g fight, thats why we knew what to avoid. "the attacker know when he attack the defender dont know when to defend so defender is screwed" BS, the dominion sov system gives the defender 4 timers. he know 4 times in a row, more than a day ahead, exactly at what minute he has to defend and he has the luxory to screw up 3 times and if he does everything right at only one of the timers he has won already. cva knew 2 days in advance when to be in system and when to force -a-to jump into them. cva where even in system and had already loaded system and grid but jumped out of system to jump back in again, exactly that was the moment they removed the randomness from the problem: one party loaded one party not. not the code, not the dev in system , cva s decission made the problem a onesided one. jumping in 150 caps at once and jumping in the in-system support fleet to the same location resuts in many thousend database read and write acessrequests landing in a que on a cpu that is already far beyond 100% usage...... they had to load system and than grid while -a- had to load grid only and than started to shoot and added to the problem by doing so.
If it was truely random nothing they did before the battle should matter. That's the very definition of random: to be unpredictable. When what you say is true, then the results are somewhat predictable and thus NOT random - it would make that a kind of de facto game mechanics that certain actions cause certain problems in the node and that those problems are likely to strike pilots doing certain actions and likely render them helpless. Of course we could argue whether this would make it an exploit or not, but I doubt CCP will ever call it that.
But the actual point is that it is possible to create conditions in which players can be killed without them being able to do anything about it. You have to be very naive to think that this can be in the interest of any player. Because everybody/-thing in EVE tells you "There is someone who knows more / fights harder / learns faster / has more luck / etc. - If you can win today someone else can win tomorrow"
Oh and a CPU cannot really be far beyond 100% usage - not even a little bit...
|
Rakshasa Taisab
Caldari Sane Industries Inc. Initiative Mercenaries
|
Posted - 2010.02.10 04:34:00 -
[235]
Originally by: Skaarl you have noticed that CCP atlas has been changing his blog and walking his comments back from "we took measures that would make a system admin faint" to "oh it was just a bug fix, we didnt actually do anything..."
What makes system admins faint is the prospect of a cluster-wide crash due to a renegade node. They don't give rats ass about your Good Fights in a 1600+ fight.
But go ahead, be all butthurt and emoraging about losing a dread. Besides, where does CCP state that a ship that logs out on a lagged node is guaranteed to be gone after 15 minutes?
|
evsNOTeve
|
Posted - 2010.02.10 04:57:00 -
[236]
Originally by: Rakshasa Taisab where does CCP state that a ship that logs out on a lagged node is guaranteed to be gone after 15 minutes?
here you go from the official evelopedia even (link is on the bar to the left here)
|
Rakshasa Taisab
Caldari Sane Industries Inc. Initiative Mercenaries
|
Posted - 2010.02.10 05:03:00 -
[237]
Originally by: evsNOTeve
Originally by: Rakshasa Taisab where does CCP state that a ship that logs out on a lagged node is guaranteed to be gone after 15 minutes?
here you go from the official evelopedia even (link is on the bar to the left here)
Sorry, can't see anything about lagged nodes.
Perhaps you are confused, and think CCP has guaranteed game mechanics function without lag on overloaded servers. Kinda like how our guns are supposed to work immediately when we click the little gun icon thingie even with 1000 ships on grid.
|
evsNOTeve
|
Posted - 2010.02.10 05:18:00 -
[238]
Edited by: evsNOTeve on 10/02/2010 05:19:42 no but it doesnt say that it doesnt work on a lagged node either.....
are you really that dense? the 1min/15min timers have been in the game A LONG time, and it for sure should be one thing that works on a node, lagged or not (it helps the server to know that it doesn't have to worry about that ship anymore....)
***edit o and the gun thingie does work if you click it, just maybe not as fast as you would like...but ccp admitted that in the blog here........they've NEVER said that logging out mechanics would be affected as well
|
Rakshasa Taisab
Caldari Sane Industries Inc. Initiative Mercenaries
|
Posted - 2010.02.10 05:37:00 -
[239]
Originally by: evsNOTeve no but it doesnt say that it doesnt work on a lagged node either.....
are you really that dense? the 1min/15min timers have been in the game A LONG time, and it for sure should be one thing that works on a node, lagged or not (it helps the server to know that it doesn't have to worry about that ship anymore....)
Now you are projecting your own expectations on what you think _should_ happen, and making it the official rules.
CCP has never claimed that using the ship scanner doesn't work on a lagged node either...
Or that ejecting Exotic Dancers won't get lagged, or what ever.
|
evsNOTeve
|
Posted - 2010.02.10 06:19:00 -
[240]
yes, so? in this blog they admit certain things like guns cycling and interface items dont work, and therefore you shouldn't expect them to (at least now after the blog), but they did not say that logging out does not work, so we should expect that it works AS NORMAL until they tell us it doesn't
we're talking regular, essential, game mechanics here and i'm pretty sure the expectation is that they work as normal until we're told otherwise
in this particular case, ccp/gms refuse to admit that there is any sort of problem with logging out...
|
|
|
|
|
Pages: 1 2 3 4 5 6 7 [8] 9 10 11 12 .. 12 :: one page |
First page | Previous page | Next page | Last page |