|
Author |
Thread Statistics | Show CCP posts - 40 post(s) |
Aryth
GoonWaffe Goonswarm Federation
42
|
Posted - 2012.05.02 14:21:00 -
[1] - Quote
Some feedback on the technical issues we experienced.
Note, I am the planner and supplier of this event.
The bad:
TIDI makes the Blackscreening issue much worse. To the point that someone with lower than -2.5 sec status may never load grid before they are dead by faction police. Blackscreening was the #1 issue needing fixing.
Wardecs not being able to be fired upon. This results when a wardec is in place in only one direction. From what I understand, this is a quite old bug. Perhaps it can be fixed with the wardec revamp.
The good:
Two shots. When originally planned I only expected each BC to get a single shot off. However, due to some wierdness with TIDI and concord, quite often people managed two. Even without ROF implants and such. Interesting but not easily repeatable. This was more than the usual 6 second bonus for off grid.
Smoothness. The best part of single shot ganking is that you aren't usually TIDI'ed for the first shot. Only when the target is dying and concord spawning does it kick in. So you get to watch in slow motion as someone dies.
We only used 1/3rd of the ships we had stockpiled. This was mostly due to the complete lockdown that Jita went into as far as freighters and JF's. Mineral volumes dropped 50%+ across the board etc. Targets dried up as no one would jump in or out of Jita. To the point that when we even saw the freighter with 1 exotic dancer, he just had to die too as we were bored.
So we have a stockpile of ships still in Jita that can do two more burn Jitas. Approx 1250 Tornados and another 12-13k Thrashers. The vast majority of our ships blown up were personal ones bought off market to clear that out before hitting stockpiles. We suspect the login screen advert and one month notice saved many a victim. Next time we will not notify in advance and will simply show up and announce our presence with a nice fat 10b+ ISK kill.
Everyone had a blast, and a total of 520B ISK in damage was done. Given the original goal was 1T using the entire stockpile, and we were on track for 1.5. This was a success for us far beyond what was expected. Jita turtling up was unexpected and a happy occurrence. So the players do read news/login screens in general and react appropriately.
We will be back, we already have the ships ready, and you shall see the howitzers on the gates of Jita once more.
|
Aryth
GoonWaffe Goonswarm Federation
43
|
Posted - 2012.05.02 14:34:00 -
[2] - Quote
CCP Veritas wrote:Aryth wrote:TIDI makes the Blackscreening issue much worse. We've tracked down a likely cause for this, and it's related to how the emergency hot-patch was done. Did you guys continue to experience this problem after Saturday's downtime?
Yes. It was an issue the entire weekend. Very similar to the old 0.0 issues where you never load grid and are dead before you do. |
Aryth
GoonWaffe Goonswarm Federation
45
|
Posted - 2012.05.02 14:48:00 -
[3] - Quote
CCP Veritas wrote:Aryth wrote:CCP Veritas wrote:Aryth wrote:TIDI makes the Blackscreening issue much worse. We've tracked down a likely cause for this, and it's related to how the emergency hot-patch was done. Did you guys continue to experience this problem after Saturday's downtime? Yes. It was an issue the entire weekend. Very similar to the old 0.0 issues where you never load grid and are dead before you do. Well damn, time to keep up the search then. If you happen to have any known instances with char names and times please eve-mail me. Vile rat wrote:If you want to smug it up in this thread you go right ahead ok? Got most of that out of my system at Fanfest
I am asking around. Hard when people don't remember exactly which KM was blackscreen and which weren't. Some would just die to faction while trying to warp off etc. Hopefully someone has a good memory. |
Aryth
GoonWaffe Goonswarm Federation
46
|
Posted - 2012.05.02 15:01:00 -
[4] - Quote
Note, many of the kills happened in perimeter and sobi. Especially some of the most expensive. So you may want to include those in the stats. |
Aryth
GoonWaffe Goonswarm Federation
47
|
Posted - 2012.05.02 15:09:00 -
[5] - Quote
Katrina Bekers wrote:CCP smugness in the devblog and in these posts is very well deserved.
The dilemma: is CFC happy that CCP finally delivered an environment where Burn Jita is not only possible, but actually enjoyable; or is CCP happy that CFC gave them the chance to showoff their best server-fu?
In the end, everyone is happy that the sandbox works as intended, both technically and as player-driven content.
Both
We know this wasn't possible even a year ago. This was actually attempted once before, the concord spawn crashed the node.
Nerfing boomeranging was a slight damper as that was the original basis of the thrasher fleet, but it didn't change our ability for carnage in general.
Everyone won with this event. Except of course the guys flying 15B isk freighters that got popped. |
Aryth
GoonWaffe Goonswarm Federation
51
|
Posted - 2012.05.02 15:32:00 -
[6] - Quote
Yes, the population cap meant that ganking in Jita was actually the wrong choice for most of the weekend. Nice juicy targets would stack up trying to get into Jita and getting the node full message. So you had plenty of time to scan them all and blow them up. So anytime the node was full, we jumped into another system and ganked everyone waiting to get in.
Good times. |
Aryth
GoonWaffe Goonswarm Federation
61
|
Posted - 2012.05.02 17:04:00 -
[7] - Quote
CCP Explorer wrote:Vincent Athena wrote:What happens now? What was the fix?
I could see:
Inform all clients of the correct time GCC time when someone jumps into system; Make the 15 minute timer not subject to TiDi; Something else...?
What was the fix? The issue was the following: When player A acquired GCC then Jita was informed and everyone cached the timer. Then player A left Jita, served the GCC on another node not under TiDi and came back to Jita. The Jita server cleared the GCC but the clients in Jita still had the old timer cached; therefore player A was blinking red as legitimate target but if someone actually shot then the server would activate CONCORD. The fix was to not rely on cached timers from the last time but rather have player A's client inform the solarsystem on arrival about the GCC having run out on a different node (that was not under TiDi) and have everyone clear their local cache. Edit: See CCP Masterplan's reply here https://forums.eveonline.com/default.aspx?g=posts&m=1231364#post1231364
We unintentionally made this far worse when we discovered GCC's were impacted by TIDI. It became common practice early on to tell people to wait out their GCC outside Jita as the timer ran at 100% normal in Perim/Sobi. So quite often they would come back into Jita and someone would try to pod them or gank. |
|
|
|