Pages: 1 2 3 [4] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 4 post(s) |
X Gallentius
Quantum Cats Syndicate Villore Accords
173
|
Posted - 2012.04.25 16:15:00 -
[91] - Quote
GM Zerat wrote:This is a bug, and is scheduled to be fixed in a future patch. Abusing this intentionally is NOT allowed. Period. Was this bug fixed in this patch? If not, is there any way you could provide a timeframe for the future patch for when it will be fixed?
|
David Caldera
Screaming War Eagles Incorporated
15
|
Posted - 2012.04.25 18:00:00 -
[92] - Quote
X Gallentius wrote:GM Zerat wrote:This is a bug, and is scheduled to be fixed in a future patch. Abusing this intentionally is NOT allowed. Period. Was this bug fixed in this patch? If not, is there any way you could provide a timeframe for the future patch for when it will be fixed? Not fixed with Escalation. I can get get other people to confirm that as well. |
Damar Rocarion
Nasranite Watch Caldari State Capturing
163
|
Posted - 2012.04.29 17:40:00 -
[93] - Quote
Could CCP comfirm if preventing captured plexes from despawning and re-entering circulation is an exploit or not? This is relatively easy to achieve and practiced by gallente a lot.
|
Cearain
Imperial Outlaws
348
|
Posted - 2012.04.30 15:26:00 -
[94] - Quote
David Caldera wrote:X Gallentius wrote:GM Zerat wrote:This is a bug, and is scheduled to be fixed in a future patch. Abusing this intentionally is NOT allowed. Period. Was this bug fixed in this patch? If not, is there any way you could provide a timeframe for the future patch for when it will be fixed? Not fixed with Escalation. I can get get other people to confirm that as well.
CCP please take a look at this. Few are playing this aspect of the game due to your neglect of this known bug. Make faction war occupancy pvp instead of pve https://forums.eveonline.com/default.aspx?g=posts&m=53815&#post53815
|
Tiffy Mezzier
Quantum Cats Syndicate Villore Accords
0
|
Posted - 2012.04.30 23:46:00 -
[95] - Quote
Yeah, ignoring the politics, the larger issue is that this is a bug that disrupts normal gameplay.
We need to collectively focus on this fact rather than finger pointing. If we ensure that CCP makes the effort to fix the issue, then the discussion regarding its exploitation will be rendered irrelevant. |
Damar Rocarion
Nasranite Watch Caldari State Capturing
163
|
Posted - 2012.05.02 14:38:00 -
[96] - Quote
Tiffy Mezzier wrote:Yeah, ignoring the politics, the larger issue is that this is a bug that disrupts normal gameplay.
We need to collectively focus on this fact rather than finger pointing. If we ensure that CCP makes the effort to fix the issue, then the discussion regarding its exploitation will be rendered irrelevant.
Yesterday Gallentes removed two plexes from circulation in Kedama, at least one pilot was petitioned for it. Knowing CCP, they will not take action since gallentes were involved.
|
Cearain
Imperial Outlaws
362
|
Posted - 2012.05.03 14:04:00 -
[97] - Quote
Damar Rocarion wrote:Tiffy Mezzier wrote:Yeah, ignoring the politics, the larger issue is that this is a bug that disrupts normal gameplay.
We need to collectively focus on this fact rather than finger pointing. If we ensure that CCP makes the effort to fix the issue, then the discussion regarding its exploitation will be rendered irrelevant. Yesterday Gallentes removed two plexes from circulation in Kedama, at least one pilot was petitioned for it. Knowing CCP, they will not take action since gallentes were involved.
Damar you are right ccp doesn't care about bugs in faction war and never has. But they don't care who is using the bug. They just don't care at all.
I think you should bug report it as a null sec issue that might get it to someone who actually fixes bugs. Make faction war occupancy pvp instead of pve https://forums.eveonline.com/default.aspx?g=posts&m=53815&#post53815
|
Tiffy Mezzier
Quantum Cats Syndicate Villore Accords
1
|
Posted - 2012.05.04 06:20:00 -
[98] - Quote
Damar Rocarion wrote:Tiffy Mezzier wrote:Yeah, ignoring the politics, the larger issue is that this is a bug that disrupts normal gameplay.
We need to collectively focus on this fact rather than finger pointing. If we ensure that CCP makes the effort to fix the issue, then the discussion regarding its exploitation will be rendered irrelevant. Yesterday Gallentes removed two plexes from circulation in Kedama, at least one pilot was petitioned for it. Knowing CCP, they will not take action since gallentes were involved.
Damar, I'm surprised that you'd qoute me but then completely gloss over the entire point of what I was trying to say. Hear me out, because I think this will explain a lot.
Understand, the way most studios work, bugs like these get submitted to a live server QA team. Live QA then has to find it amidst the garbage and dupilcate bugs people submit, and send it to a QA pending box. The bug then sits there until a lead in core QA finds it and farms it out for someone to confirm. After being confirmed, the bug gets sent by QA to the bugbox of whatever team the bug needs to be fixed by. This is not always the right box...
It then sits in whatever bugbox it got sent to until someone on that team discovers it. If the bug is listed as high-priority , then they will probably see it within the day. If it's a medium or lower, then it could be a month before anyone sees it.
When it's deemed fixed by that team, it gets compiled into a build with whatever other fixes and patches are being worked on and rolled out onto an internal server. The bug then goes BACK to QA who confirms that the fix actually worked. This does not always happen...
After ALL of this, that fix remains on the internal servers until the whole build is deemed as "complete" regarding whatever milestone or sprint the various teams are working on.
So here's what I'm trying to say:
If we want to see this thing fixed, we have to make enough noise collectively to justify the community and/or live team flagging the bug as high-priority. There are two required things needed to accomplish this:
One is a clear and coherent bug report free of any information that does not directly relate to the bug itself.
You've done a good job of collecting information, so kudos for that. Polish up your steps for reproducing the bug, and log into the test server to get fraps or screenshots. It's much easier for CCP to approach fixing an issue when they have all information on what the issue is, where it occurs, and how it occurs.
Then the next thing would be to approach a relevant member of the dev staff, and ask them politely to prioritize this. It is highly likely that there is already a fix for this going into the next big patch since FW is getting overhauled.
As a side note, for the sake of ensuring the issue gets assigned to the proper staff members, I would strongly advise against making any accusations of exploiting in your bug report, and instead include that information into a SEPARATE report.
This because any such accusations will immediately cause the report to be sent to the community team, who will then sit on the issue if they can get away with it until it becomes irrelevant. Not because CCP is chosing sides, but because sitting on an issue is much easier than trying to appease angry mobs.
|
Damar Rocarion
Nasranite Watch Caldari State Capturing
172
|
Posted - 2012.05.04 20:03:00 -
[99] - Quote
Tiffy Mezzier wrote:As a side note, for the sake of ensuring the issue gets assigned to the proper staff members, I would strongly advise against making any accusations of exploiting in your bug report, and instead include that information into a SEPARATE report.
This because any such accusations will immediately cause the report to be sent to the community team, who will then sit on the issue if they can get away with it until it becomes irrelevant. Not because CCP is chosing sides, but because sitting on an issue is much easier than trying to appease angry mobs.
In other words, give in to terrorists. F..k no. I should never have reported this one since CCP is content to let gallente side keep using this bug without repercussions as I bit expected.
|
Tiffy Mezzier
Quantum Cats Syndicate Villore Accords
1
|
Posted - 2012.05.04 22:34:00 -
[100] - Quote
Damar Rocarion wrote:Tiffy Mezzier wrote:As a side note, for the sake of ensuring the issue gets assigned to the proper staff members, I would strongly advise against making any accusations of exploiting in your bug report, and instead include that information into a SEPARATE report.
This because any such accusations will immediately cause the report to be sent to the community team, who will then sit on the issue if they can get away with it until it becomes irrelevant. Not because CCP is chosing sides, but because sitting on an issue is much easier than trying to appease angry mobs.
In other words, give in to terrorists. F..k no. I should never have reported this one since CCP is content to let gallente side keep using this bug without repercussions as I bit expected.
I tried Damar, I tried so hard to turn this thread around and steer the discussion away from your tiresome grandstanding.
I was hoping for some kind of positive result where the FW community as a whole would be able to benefit. Instead you insist on using every remotely well thought out post as your personal soapbox.
So enjoy your corner, I'm fairly sure that your efforts have made this thread radioactive. To the point that any legitimate issues which might have been solved here have likely been taken out back and buried 400 feet under the Icelandic tundra. |
|
Mekhana
Spiritus Draconis Sicarius Draconis
446
|
Posted - 2012.05.12 02:01:00 -
[101] - Quote
Damar never ceases to amuse me. |
Andreus Ixiris
Mixed Metaphor Federal Consensus Outreach
871
|
Posted - 2012.05.15 12:07:00 -
[102] - Quote
Bad Messenger wrote:Well, you get warning only because you are part of Caldari militia and preventing CCP plans to make gallente to win.
I recommend that everyone quits militia right now because normal game play may cause you to get bans.
CCP has finally gone too far.
This must be related to their new goal to make WoW in space.
It doesn't count as trolling when you're doing the crying.
Mane 614
|
Cearain
Imperial Outlaws
424
|
Posted - 2012.05.18 12:11:00 -
[103] - Quote
Tiffy Mezzier wrote:Yeah, ignoring the politics, the larger issue is that this is a bug that disrupts normal gameplay.
We need to collectively focus on this fact rather than finger pointing. If we ensure that CCP makes the effort to fix the issue, then the discussion regarding its exploitation will be rendered irrelevant.
Have they fixed this bug yet? Or are we charging into big consequences knowing that people already gained and defended allot of territory from an exploit? Make faction war occupancy pvp instead of pve https://forums.eveonline.com/default.aspx?g=posts&m=53815&#post53815
|
Val Erian
Azure Horizon Federate Militia
5
|
Posted - 2012.05.25 20:32:00 -
[104] - Quote
As of Inferno release this bug HAS NOT BEEN FIXED.
Currently causing disruption in FW Gameplay as it has for couple of years. |
|
CCP Ytterbium
C C P C C P Alliance
609
|
Posted - 2012.05.29 15:05:00 -
[105] - Quote
Hey folks, we've been reviewing FW deployment with the CSM, who pointed this thread as one of the long, bitter issues that need to be looked into.
We had this issue investigated a few weeks back before Inferno deployment and we believed we fixed it back then. Obviously it's not, we'll have another look into it.
Thanks for the update! |
|
Bienator II
madmen of the skies
738
|
Posted - 2012.05.29 16:10:00 -
[106] - Quote
btw i filed a bug yesterday right after i soloed a major plex in a hostile system without getting any LP (or any kind of mail notification). After asking in local some said (enemy militia) that they have the exact same issue from time to time. The system occupacy bar flashed after i finished the plex so it got recognised in a form or the other. a eve-style bounty system https://forums.eveonline.com/default.aspx?g=posts&m=359105 You fail you fail you fail you fail you fail you fail you fail to jump because you are cloaked |
Super Chair
Project Cerberus Caldari State Capturing
263
|
Posted - 2012.06.03 06:10:00 -
[107] - Quote
CCP Ytterbium wrote:Hey folks, we've been reviewing FW deployment with the CSM, who pointed this thread as one of the long, bitter issues that need to be looked into.
We had this issue investigated a few weeks back before Inferno deployment and we believed we fixed it back then. Obviously it's not, we'll have another look into it.
Thanks for the update!
Still not fixed, but it appears praznimrak is starting to use it intentionally in oicx. I may have to create my first gallente alt in a couple years if its going to be a race of who exploits the most until CCP either starts issuing bans or fixes said bugs :)
|
Bienator II
madmen of the skies
744
|
Posted - 2012.06.03 14:41:00 -
[108] - Quote
also: the system progress bar randomly disapears. I am sure it has been said already a few times. a eve-style bounty system https://forums.eveonline.com/default.aspx?g=posts&m=359105 You fail you fail you fail you fail you fail you fail you fail to jump because you are cloaked |
|
CCP Masterplan
C C P C C P Alliance
357
|
Posted - 2012.06.18 17:58:00 -
[109] - 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 |
|
Ponder Yonder
Fleet of the Damned
34
|
Posted - 2012.06.20 13:04:00 -
[110] - Quote
CCP Masterplan wrote:
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.
@CCP Masterplan
Your recipe is basically correct, but a critical detail is clearly missing. I suspect that B needs to leave the plex after chasing A out. Some time later, after A sees that B is not in local anymore, he returns to the plex.
A recent example: A runs the counter down to 5 mins. B enters the plex, A warps off. A spawns another plex in the same system and caps it. A notices that B is not in local anymore and returns to the original plex, finding the timer increased. (Not sure whether it was more or less than the initial 10mins). A orbits the button until 0, but no completion message.
Would it help if we gave you examples of bugged plexes immediately after finding them in-game? |
|
Hans Jagerblitzen
Autocannons Anonymous Late Night Alliance
2554
|
Posted - 2012.06.20 13:32:00 -
[111] - Quote
Isn't combat part of this equation? It was my understanding that you not only had to warp in and out of the plex according to the pattern, but that shots had to be exchanged between opposing WT within range of the button for this bug to be triggered. (which is why this bug is reported to occur so frequently, the conditions for its reproduction are too similar to normal game play within the complex).
Thanks for the update CCP, keep us comprised as to your progress I'm sure there is plenty of folks here happy to assist with narrowing this down, unless its already been fixed and no one here has actually tested it themselves since the supposed fix. Vice Secretary of the 7th Council of Stellar Management.
|
|
CCP Masterplan
C C P C C P Alliance
362
|
Posted - 2012.06.20 13:50:00 -
[112] - Quote
Great news everyone! I think I've found the critical missing piece of the jigsaw this morning. I'm now able to repro the problem on demand, which is 90% of the way to a solution. "This one time, on patch day..." CCP Masterplan -á| -áTeam Five-0: Rewriting the law |
|
|
|
|
Pages: 1 2 3 [4] :: one page |
First page | Previous page | Next page | Last page |