
CCP Masterplan
C C P C C P Alliance
357

|
Posted - 2012.06.18 17:58:00 -
[1] - Quote
Super Chair wrote:Quote:Bug that causes outposts to not respawn: Say militia A is running the timer in the plex. Militia B shows up and forces Militia A out of the plex and begin running the timer. Militia A comes back and forces Militia B out and runs the timer until the timer goes to what is normally "captured" on the timer progress bar that you see in space. However, the timer "bugs" and the capture message does not appear in local (even though the progress bar, or timer on the button shows captured). Militia A now has two options, they can spend the extra time and continue to sit on the timer until the capture message shows up in local, or they can choose (or be forced) to leave to plex before the capture message (in local) appears. If the second scenario happens, and Militia A leaves the plex before the message in local appears, the plex will despawn just like any other "captured" plex and close. However, it will not respawn. So, outposts can be removed from circulation thus making a system "unattackable" intentionally. Also keep in mind that this can be caused unintentionally (such as two militias fighting over the the plex, and whoever wins the plex doesn't know any better and warps off when the timer reads captured, but no green message in local to say that the plex was actually captured, or that militia knows of the bug, tries to sit on the timer for an extra amount of time, but is forced to leave the plex because of a blob coming for them).
Again to recap the conditions that must be met: 1) Members of opposing militias must each control the timer at some point 2) The militia that controls the timer originally must be the militia to capture the plex for the bug to occur. (So in an A->B->A->Captured format) If Militia A controls the timer and then Militia B comes and and kicks Militia A out and captures it (A->B->Captured) the bug will not occur (at least that is what I have witnessed). 3) Militia A must vacate the plex so it will despawn sometime between the progress bar showing "captured" and the local message showing up in local. Am I correct in the details of the bug? I haven't seen it happen unless control of the timer changes hands at least twice. Also, what is GM stance on the bug happening unintentionally? Because the bug does occur when militias just happen to be fighting over the plex, and the above conditions are met, the bug will occur. Will the GM department attempt to make the distinguishment between the bug simply occuring during "normal" gameplay and intentionally attempting to trigger the bug? Hi all, I've been asked to take a look in to this issue.
Firstly, let me say that arguing about who has or hasn't used tactic X is not something I'm concerned with here. If you have issues about something being an exploit or not, or accusations of someone cheating, please keep it to yourself (or file a petition). My only concern with this is getting to the bottom of what is happening to these stuck plexes, and finding a solution. Apart from the quoted post and the OP, the noise in this thread is simply no help to me whatsoever in this regard. So from now on, please consider this a problem-solving thread, not a mud-slinging one. I'll start asking the moderators to take action if this doesn't improve. I don't care what side of FW you represent, I just want to let you all get on with blowing stuff up in a reliable manner, so let's drop the "CCP prefers side Y over Z" stuff, OK?
So, with that out of the way... When I first read the post above, it seemed that a reliable reproduction case would be straightforward to develop. However I've been testing this for a while, and have been unable to make it happen at all on my test server. I must be missing something, if it is as reliable as some suggest.
Here's what I'm doing: * Characters A and B in opposing NPC militias, in B's space (so A is attacker, B is defender) * A warps in to a minor outpost and approaches the beacon. The countdown starts * After one minutes, B warps in and approaches the beacon. Beacon becomes contested (at around 9mins) * A warps out. Beacon now starts counting back for B (from 11mins) * A warps back in to the plex. Beacon becomes contested again. * B warps out. Beacon starts counting back for A again. * Once the timer expires, the beacon becomes captured, and the "Site has been captured" message immediately appears in local for A * A warps out * Around 30 minutes later, a new instance of the plex reappears on scan, as normal.
As you can see, I'm failing to get a repro, following what appears to be the steps mentioned by Super Chair. So, what am I missing?
Like I said above, please keep your replies constructive. If you're not posting something that might be useful to me for fixing this, then don't post it.
"This one time, on patch day..." CCP Masterplan -á| -áTeam Five-0: Rewriting the law |