| Pages: [1] :: one page |
| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Cyxopyc
The Dead Parrot Shoppe Inc.
Brutally Clever Empire
   |
Posted - 2008.04.29 15:43:00 -
[1]
I've tried twice to report this bug and I have failed the filter both times. If you are up to the moderately difficult task just reply here saying you want to do this and if you are the first to do so it will be assumed you've taken it over.
Although nowhere on the initial bug report page does it say so I believe reporting a bug requires screenshots. You'll need to uncheck 'save screenshots in high quality' in game. Make a screenshot whenever any aspect of the bug can be seen in game, no matter how trivial. Also to always use the LogServer.exe program. These screenshots and Logserver results must be included with the bug report.
From what I've gathered your role as a bug reporter is not to let CCP know there is a bug but rather to prove there is a bug and to prove precisely as possible what that bug is or is not. This puts a big load of work on the bug reporter but this is how it is. Read this post before proceeding nullCreating Bug Reports.
--
Previously reported as:
Report ID: 53510
Title: Kill Rights punish victim acted on quickly
--
Briefly, here is how to see the bug. Do nothing other than what is detailed here:
In low sec away from sentry guns have one player destroy a second player¦s ship. Observe Kill Rights on both characters, note the time shown. Then have player one pod the second player. Observe Kill Rights on both characters and note the time has not updated from the podding. Shortly after countdown timers have faded, with neither having logged out, have the second player act on the kill rights in high sec. It demonstrates the bug every time with Concord punishing the second player with ship destruction and security status loss. I did this test twice with trial accounts.
Submit your bug report here http://bugs.eve-online.com/
I would pursue this but I've moved to 0.0 and don't feel like spending more time on it.
Evemail me in game if you have questions.
==
Support fixing the EVE UI |
Eleana Tomelac
Gallente
Through the Looking Glass
|
Posted - 2008.04.29 16:06:00 -
[2]
 Originally by: Cyxopyc
Briefly, here is how to see the bug. Do nothing other than what is detailed here:
In low sec away from sentry guns have one player destroy a second player¦s ship. Observe Kill Rights on both characters, note the time shown. Then have player one pod the second player. Observe Kill Rights on both characters and note the time has not updated from the podding. Shortly after countdown timers have faded, with neither having logged out, have the second player act on the kill rights in high sec. It demonstrates the bug every time with Concord punishing the second player with ship destruction and security status loss. I did this test twice with trial accounts.
I'm not sure I can follow exactly what you say, it's confusing.
Could you explain it again saying player A and player B? Because it's confusing, I don't know who shot who at the start.
Also, from what I understood, the killright didn't disapear when it should and it makes the player think he still has a killright while it has been completed few minutes ago, so when shooting the other in hi-sec, concord replies because there was no killright.
So, it was filtered because it's unclear in the exact steps to make this happen. We get lost in who must shoot who and who has a killright when.
--
Pocket drone carriers (tm) enthousiast !
Assault Frigates MK II |
Cyxopyc
The Dead Parrot Shoppe Inc.
Brutally Clever Empire
|
Posted - 2008.04.30 01:15:00 -
[3]
It seems so clear to me 
Once again, in A B form...
-------------------------------------------------------
- in low sec
Player A attacks and destroys player B's ship
(note details on the kill rights now displayed especially the exact time)
Player A attacks and pods player B
(note details on the kill rights have not changed and still display the original time from the ship destruction)
* At no time while in low sec does player B attack Player A.
- in high sec after countdowns expire
Player B attacks player A.
* No warning window appears because player B has kill rights on Player A
* Instantly a concord security status loss is immediately suffered by player B followed shortly by concord destroying player B's ship.
* At no time has either player A or player B logged out or been disconnected during this test.
-------------------------------------------------------
I've tried many ways to explain this. I feel like everyone is joking around with me. It's a very straight forward pvp encounter in low sec that involves ship destruction and podding of the defenseless victim. Then the victim attempts to act on the kill rights. Concord jumps in on the victim.
If it matters, I used brand new minmatar characters out of Ammold V - Republic Military School on trial accounts to check this out flying through Emolgranlan to low sec Eifer for the initial pvp part. Both characters were using Reapers for the test with the low sec attacker using two newbie gatlins (to do twice the wimpy damage). I was running both characters myself on two computers.
==
Support fixing the EVE UI |
Eleana Tomelac
Gallente
Through the Looking Glass
|
Posted - 2008.04.30 09:38:00 -
[4]
It is perfectly clear said this way.
I guess you could try to update your bugreport explaining this way.
It seems a severe issue in the killrights system as it's someone having a killright and concord reacting to his authorized use of the killright.
--
Pocket drone carriers (tm) enthousiast !
Assault Frigates MK II |
Katana Seiko
Gallente
|
Posted - 2008.04.30 11:09:00 -
[5]
The problem is - if the bug hinter doesn't understand what you want to say, your bug report is either ignored or refused... And yes, a screen shot of those timers might be a good idea too...
---
"Multiple exclamation marks are a sure sign for a diseased mind." -Terry Pratchett |
Jaketh Ivanes
Amarr
Do Or Die And Live Or Try
The Kano Organisation
|
Posted - 2008.04.30 14:08:00 -
[6]
Just a little question, when you say "Player A pods player B" do you mean that player blows the pod or only the ship (many people says they have been podded, when only the ship goes boom).
Not sure it has any influence on the kill rights system, but it might be an important detail.
|
Cyxopyc
The Dead Parrot Shoppe Inc.
Brutally Clever Empire
|
Posted - 2008.04.30 21:52:00 -
[7]
Thanks for the feedback everyone. I may resubmit it someday with this text plus screenshots and logserver results.
Originally by: Jaketh Ivanes
Just a little question, when you say "Player A pods player B" do you mean that player blows the pod or only the ship (many people says they have been podded, when only the ship goes boom).
Not sure it has any influence on the kill rights system, but it might be an important detail.
You're right I've heard 'podding' used incorrectly to mean just a player's ship was destroyed. Here, I do mean player B's pod is attacked and destroyed by player A.
It's a tough line to follow between clarity and confusion.
==
Support fixing the EVE UI |
| |
|
| Pages: [1] :: one page |
| First page | Previous page | Next page | Last page |