Pages: 1 2 [3] 4 5 :: one page |
|
Author |
Thread Statistics | Show CCP posts - 6 post(s) |
Bubanni
SniggWaffe YOUR VOTES DON'T COUNT
275
|
Posted - 2012.04.28 12:11:00 -
[61] - Quote
CCP Masterplan wrote:So here's the rules: * You can freely kill a pod if the pilot is an outlaw (below -5 sec status) * You can't kill a pod if the pilot just has a GCC. If you try, you'll get the non-suppressible "Are you sure? CONCORD will wtfpwn you if you do this" dialog This has always been the case
Normally someone with GCC will show up as red. What changed with Escalation was that we removed a special case in the UI that suppressed this red if they had GCC AND were in a pod. Now someone with GCC will always show up as red, regardless of their ship. However you will stil get punished if you kill a GCC pod BUT only if you click 'Yes' to the CONCORD question.
I do agree this can be a little confusing, and we're looking at adjusting it a little based on feedback such as this.
What a horrible change, there was no reason for that... worst of all, you forgot to tell everyone! You should really consider reimbursing everyone who lost ships because of this. |
Adriel Malakai
Shoulda Checked Local Break-A-Wish Foundation
36
|
Posted - 2012.04.28 12:16:00 -
[62] - Quote
Bubanni wrote:CCP Masterplan wrote:So here's the rules: * You can freely kill a pod if the pilot is an outlaw (below -5 sec status) * You can't kill a pod if the pilot just has a GCC. If you try, you'll get the non-suppressible "Are you sure? CONCORD will wtfpwn you if you do this" dialog This has always been the case
Normally someone with GCC will show up as red. What changed with Escalation was that we removed a special case in the UI that suppressed this red if they had GCC AND were in a pod. Now someone with GCC will always show up as red, regardless of their ship. However you will stil get punished if you kill a GCC pod BUT only if you click 'Yes' to the CONCORD question.
I do agree this can be a little confusing, and we're looking at adjusting it a little based on feedback such as this. What a horrible change, there was no reason for that... worst of all, you forgot to tell everyone! You should really consider reimbursing everyone who lost ships because of this.
Quote:Characters in capsules will now show up as criminals on the overview just like when piloting any other ship.
http://community.eveonline.com/updates/patchnotes.asp
Under Changes - Crimewatch
Note: Reading patch notes is a good idea.
Also, the ships should not be reimbursed (the pilots are responsible for turning off the CONCORD warning in the first place), but this change should be reversed. |
|
CCP Greyscale
C C P C C P Alliance
1255
|
Posted - 2012.04.28 12:39:00 -
[63] - Quote
Adriel Malakai wrote:You can permanently suppress the CONCORD pop-up with a convenient check-box, so people are getting GCC'd because they shot a red pod, without receiving a warning.
If that's the case then please file a bug report immediately - the CONCORD pop-up should not be suppressible (and wasn't when I was testing on SiSi yesterday).
|
|
Destination SkillQueue
Are We There Yet
2311
|
Posted - 2012.04.28 12:45:00 -
[64] - Quote
CCP Masterplan wrote:So here's the rules: * You can freely kill a pod if the pilot is an outlaw (below -5 sec status) * You can't kill a pod if the pilot just has a GCC. If you try, you'll get the non-suppressible "Are you sure? CONCORD will wtfpwn you if you do this" dialog This has always been the case
Normally someone with GCC will show up as red. What changed with Escalation was that we removed a special case in the UI that suppressed this red if they had GCC AND were in a pod. Now someone with GCC will always show up as red, regardless of their ship. However you will stil get punished if you kill a GCC pod BUT only if you click 'Yes' to the CONCORD question.
I do agree this can be a little confusing, and we're looking at adjusting it a little based on feedback such as this.
IIRC the (default setting)design was supposed to be, that if it's red you can initiate combat freely while the red can't and if it's blinky red you can both initiate combat freely. Basicly if it's red you're always free to engage. Pods of criminals were specifically excluded because you're not free to fire on them if they're not WTs or outlaws. So it sound to me, like you just intentionally broke the intended design of the current system for no real reason or gain. Maybe I misunderstood what you meant or something, but that's how it looks to me.
|
DODGE CITY
We are the few. -Silicon Heaven-
5
|
Posted - 2012.04.28 12:50:00 -
[65] - Quote
i think we should be allowed to hunt and kill any one who has bounty on them over 10 million in high security we can kill any Rat that has bounty on them in high security why not players..its useless to see those big juicy isk numbers under their name and if you try to collect it concord will shoots you in the ass. IF CCP WOULD ALLOW PLAYERS TO VOTE ON GAME CHANGES BEFORE THEY MAKE THEM -áPLAYERS WOULD HAVE LESS REASON TO COMPLAUN GëíGêÜGëí |
J3ssica Alba
Federal Navy Academy Gallente Federation
335
|
Posted - 2012.04.28 12:54:00 -
[66] - Quote
Every person I ask about if I can shoot a pod that is -5, -6, - 9.8, -10 and so on has a different opinion about it. Can you shoot anything within a range of -5 to -10 without getting concorded? This is my signature. There are many others like it, but this one is mine.-á Without me, my signature is useless. Without my signature, I am useless |
Adriel Malakai
Shoulda Checked Local Break-A-Wish Foundation
36
|
Posted - 2012.04.28 13:00:00 -
[67] - Quote
CCP Greyscale wrote:Adriel Malakai wrote:You can permanently suppress the CONCORD pop-up with a convenient check-box, so people are getting GCC'd because they shot a red pod, without receiving a warning. If that's the case then please file a bug report immediately - the CONCORD pop-up should not be suppressible (and wasn't when I was testing on SiSi yesterday).
Just tested this - it appears you removed the check box in Escalation. Please tell me you were at least intelligent enough to have a check-box for low sec.
EDIT: Just checked this and you were. I'm sad to say that I was genuinely surprised that this was the case. |
|
CCP Greyscale
C C P C C P Alliance
1255
|
Posted - 2012.04.28 13:04:00 -
[68] - Quote
Adriel Malakai wrote:CCP Greyscale wrote:Adriel Malakai wrote:You can permanently suppress the CONCORD pop-up with a convenient check-box, so people are getting GCC'd because they shot a red pod, without receiving a warning. If that's the case then please file a bug report immediately - the CONCORD pop-up should not be suppressible (and wasn't when I was testing on SiSi yesterday). Just tested this - it appears you removed the check box in Escalation. Please tell me you were at least intelligent enough to have a check-box for low sec.
AFAIK it has *always* been the case that the CONCORD pop-up is the only non-suppressible confirmation dialogue in the game. Lowsec warnings have always had one AFAIK. None of this should have been changed in Escalation, but I can go check against previous expansions on a reference server if it's bothering you |
|
Adriel Malakai
Shoulda Checked Local Break-A-Wish Foundation
36
|
Posted - 2012.04.28 13:05:00 -
[69] - Quote
J3ssica Alba wrote:Every person I ask about if I can shoot a pod that is -5, -6, - 9.8, -10 and so on has a different opinion about it. Can you shoot anything within a range of -5 to -10 without getting concorded?
If they are below -5.0, you can pew pew them without CONCORD interference. |
Adriel Malakai
Shoulda Checked Local Break-A-Wish Foundation
36
|
Posted - 2012.04.28 13:06:00 -
[70] - Quote
CCP Greyscale wrote:Adriel Malakai wrote:CCP Greyscale wrote:Adriel Malakai wrote:You can permanently suppress the CONCORD pop-up with a convenient check-box, so people are getting GCC'd because they shot a red pod, without receiving a warning. If that's the case then please file a bug report immediately - the CONCORD pop-up should not be suppressible (and wasn't when I was testing on SiSi yesterday). Just tested this - it appears you removed the check box in Escalation. Please tell me you were at least intelligent enough to have a check-box for low sec. AFAIK it has *always* been the case that the CONCORD pop-up is the only non-suppressible confirmation dialogue in the game. Lowsec warnings have always had one AFAIK. None of this should have been changed in Escalation, but I can go check against previous expansions on a reference server if it's bothering you
This is not the case. I know because I learned the hard way to reset the warning suppresion after a lowsec roam when I lost a Tengu (different character) to a wreck that I thought I could legally shoot.
EDIT: This could have been put in prior to Escalation, but I know as recently as Incursions, this was the case. |
|
Polly Oxford
GoonWaffe Goonswarm Federation
0
|
Posted - 2012.04.28 13:19:00 -
[71] - Quote
DODGE CITY wrote:i think we should be allowed to hunt and kill any one who has bounty on them over 10 million in high security we can kill any Rat that has bounty on them in high security why not players..its useless to see those big juicy isk numbers under their name and if you try to collect it concord will shoots you in the ass.
I'm totally for this! I'll just put a 10m bounty on one of those juicy freighter pilots and kill them without Concord intervening :) |
Adriel Malakai
Shoulda Checked Local Break-A-Wish Foundation
36
|
Posted - 2012.04.28 13:21:00 -
[72] - Quote
Polly Oxford wrote:DODGE CITY wrote:i think we should be allowed to hunt and kill any one who has bounty on them over 10 million in high security we can kill any Rat that has bounty on them in high security why not players..its useless to see those big juicy isk numbers under their name and if you try to collect it concord will shoots you in the ass. I'm totally for this! I'll just put a 10m bounty on one of those juicy freighter pilots and kill them without Concord intervening :)
You must have a sec status below -1.0 to have a bounty placed on you. Not many freighter pilots fall under this category. |
Mashie Saldana
Veto. Veto Corp
491
|
Posted - 2012.04.28 13:31:00 -
[73] - Quote
By "fixing" crimewatch in Jita, did you by any chance break the Caldari Navy agression timers?
First of all they are now hidden again and they don't end after 15 minutes. Dominique Vasilkovsky Mashie Saldana Monica Foulkes |
ElQuirko
Gravit Negotii Rogue Elements.
634
|
Posted - 2012.04.28 13:37:00 -
[74] - Quote
Chopper Rollins wrote:This stuff is just punk nonsense anyway, ever heard of Demonfuge Malevolent?
How is that guy so well known? He followed me round for about a year. CISPA - Readin' your secret corptheft mails since 2012 |
Aeron Sophus
Sebiestor Tribe Minmatar Republic
0
|
Posted - 2012.04.28 13:53:00 -
[75] - Quote
CCP Greyscale wrote:Adriel Malakai wrote:CCP Greyscale wrote:Adriel Malakai wrote:You can permanently suppress the CONCORD pop-up with a convenient check-box, so people are getting GCC'd because they shot a red pod, without receiving a warning. If that's the case then please file a bug report immediately - the CONCORD pop-up should not be suppressible (and wasn't when I was testing on SiSi yesterday). Just tested this - it appears you removed the check box in Escalation. Please tell me you were at least intelligent enough to have a check-box for low sec. AFAIK it has *always* been the case that the CONCORD pop-up is the only non-suppressible confirmation dialogue in the game. Lowsec warnings have always had one AFAIK. None of this should have been changed in Escalation, but I can go check against previous expansions on a reference server if it's bothering you Uhm... Weren't you (or Masterplan, I forgot.) talking about messing with these checkboxes in your talk at fanfest?
|
|
CCP Greyscale
C C P C C P Alliance
1255
|
Posted - 2012.04.28 14:08:00 -
[76] - Quote
Aeron Sophus wrote:CCP Greyscale wrote:Adriel Malakai wrote:CCP Greyscale wrote:Adriel Malakai wrote:You can permanently suppress the CONCORD pop-up with a convenient check-box, so people are getting GCC'd because they shot a red pod, without receiving a warning. If that's the case then please file a bug report immediately - the CONCORD pop-up should not be suppressible (and wasn't when I was testing on SiSi yesterday). Just tested this - it appears you removed the check box in Escalation. Please tell me you were at least intelligent enough to have a check-box for low sec. AFAIK it has *always* been the case that the CONCORD pop-up is the only non-suppressible confirmation dialogue in the game. Lowsec warnings have always had one AFAIK. None of this should have been changed in Escalation, but I can go check against previous expansions on a reference server if it's bothering you Uhm... Weren't you (or Masterplan, I forgot.) talking about messing with these checkboxes in your talk at fanfest?
For the redesign we're hoping to do over the summer, yes. Not for this release, though |
|
Potamus Jenkins
The Lucky Bible Company The Veyr Collective
87
|
Posted - 2012.04.28 14:11:00 -
[77] - Quote
goons plan big event after major patch crazy things happen players scream conspiracy |
Mynas Atoch
Eternity INC. Goonswarm Federation
42
|
Posted - 2012.04.28 14:24:00 -
[78] - Quote
CCP Greyscale wrote:Adriel Malakai wrote:You can permanently suppress the CONCORD pop-up with a convenient check-box, so people are getting GCC'd because they shot a red pod, without receiving a warning. If that's the case then please file a bug report immediately - the CONCORD pop-up should not be suppressible (and wasn't when I was testing on SiSi yesterday). Just get back in fleet and you'll see it yourself. What was the point of giving you all complimentary goonwaffe accounts if you weren't going to file your own bug reports. sheesh |
Elsebeth Rhiannon
Gradient Electus Matari
276
|
Posted - 2012.04.28 15:00:00 -
[79] - Quote
CCP Greyscale wrote:AFAIK it has *always* been the case that the CONCORD pop-up is the only non-suppressible confirmation dialogue in the game. I am fairly certain this is not the case. Fleets used to die for escalating CONCORD thingies because a person being repped shot at something, and I seem to recall that couple of years back we used to have to tell people to check that their pop-ups are on, because of this. No information on the current situation, that is, but I am fairly convinced this has not always been the case.
Also, even with the pop-up an overview where something shows as "shootable" but isn't is terrible. Please make it go away soon. |
Skex Relbore
Space Exploitation Inc Mordus Angels
152
|
Posted - 2012.04.28 15:20:00 -
[80] - Quote
Cloned S0ul wrote:For me was always clear, if background was red and flashy and no mater if with GCC or withaut GCC i was able aways to shot. Seems like it's still pretty clear, if you get a warning telling you that Concord with WTFBBQ you if you shoot this person and you shoot them anyway you get WTFBBQ'd so if you get said warning don't click yes.
Quote: Btw remove concord because they useless, freighters pilots die even if 100 concord police officers spawn before kamikaze atac, concord are just additional chaos and drop of FPS on scren.
Yeah that's brilliant instead of making people lose a couple billion isk in non-insurable ships to kill a freighter they can do at absolutely 0 risk and loss.
|
|
Fleet Warpsujarento
State Protectorate Caldari State
76
|
Posted - 2012.04.28 15:23:00 -
[81] - Quote
So for the last 9 years if something was red you could shoot it. Now that's no longer the case.
Great job CCP. You've managed to break one of the few game mechanics that actually worked properly. Really inspires confidence in Inferno. |
|
CCP Greyscale
C C P C C P Alliance
1256
|
Posted - 2012.04.28 15:55:00 -
[82] - Quote
Fleet Warpsujarento wrote:So for the last 9 years if something was red you could shoot it. Now that's no longer the case.
Great job CCP. You've managed to break one of the few game mechanics that actually worked properly. Really inspires confidence in Inferno.
The "if it's blinky red you can shoot it" convention has IIRC only existed since we redid the overview defaults in Apocrypha. We're going to have another look at this issue next week and see if we need to revise the way this works or not. |
|
Beekeeper Bob
Beekeepers Anonymous
104
|
Posted - 2012.04.28 16:07:00 -
[83] - Quote
CCP Greyscale wrote:Fleet Warpsujarento wrote:So for the last 9 years if something was red you could shoot it. Now that's no longer the case.
Great job CCP. You've managed to break one of the few game mechanics that actually worked properly. Really inspires confidence in Inferno. The "if it's blinky red you can shoot it" convention has IIRC only existed since we redid the overview defaults in Apocrypha. We're going to have another look at this issue next week and see if we need to revise the way this works or not.
Yes, using the same color for GCC and a pirate is a masterstoke?
I really wish you people would wake up CCP, it seems like your attitude is back to "it's playable" rather than "It's fun to play".
Looking to stamp out apiphobia in my lifetime..... |
Arkady Sadik
Gradient Electus Matari
619
|
Posted - 2012.04.28 17:05:00 -
[84] - Quote
CCP Greyscale wrote:The "if it's blinky red you can shoot it" convention has IIRC only existed since we redid the overview defaults in Apocrypha. We're going to have another look at this issue next week and see if we need to revise the way this works or not. Yes, you do. The current state is not useful at all - the important information is not visible on the overview, while the unimportant information is. (No one except the pilot herself cares if she is GCC while in a capsule.)
Alternatively, make GCCd capsules valid targets :o) |
Sid Hudgens
42
|
Posted - 2012.04.28 17:41:00 -
[85] - Quote
I feel the biggest issue here is this:
I was under the impression that you could shoot a pod that is considered an "outlaw."
I specifically went into my overview settings before engaging anyone and made sure that the only thing set to be "flashy red" is for "pilot is an outlaw."
I then fired on a flash red pod and had my ship blown up and took a 30% security status hit.
I don't have a real strong opinion on what the exact rules should be, but I would like to see choices in the overview settings to be a little clearer. At the moment it would seem that "pilot is an outlaw" is not an accurate description of that overview status category.
I had the sense to try all of this out on an alt toon ... but someone who thought they knew how the overview settings worked and found this out the hard way in an expensive ship could be understandably upset. I usually don't do anything in an expensive ship without knowing that I fully understand the mechanics.
I am really glad I didn't try this out on one of my real pilots as that is a lot of security status to grind back up! "....as if 10,058 Goon voices cried out and were suddenly silenced."
This post has been brought to you by an NPC corp alt. |
Elsebeth Rhiannon
Gradient Electus Matari
277
|
Posted - 2012.04.28 18:09:00 -
[86] - Quote
CCP Greyscale wrote:Fleet Warpsujarento wrote:So for the last 9 years if something was red you could shoot it. Now that's no longer the case.
Great job CCP. You've managed to break one of the few game mechanics that actually worked properly. Really inspires confidence in Inferno. The "if it's blinky red you can shoot it" convention has IIRC only existed since we redid the overview defaults in Apocrypha. We're going to have another look at this issue next week and see if we need to revise the way this works or not. The main point is that before this change it was possible to set up your overview in such a manner that you can on a glance tell which things you can and which things you cannot shoot without CONCORD / gate gun interference. This is pretty essential in high-sec and low-sec combat, where bubbles do not exist and you have to be fast if you want to have a tackle rate anywhere close to useful. With this change, this is no longer possible, which is a major change. If it was intentional, yea, fine - but as an unintentional side effect it is quite annoying.
For the record, the solution of making GCCed pods valid targets would work for me too. ;) |
Beekeeper Bob
Beekeepers Anonymous
106
|
Posted - 2012.04.28 18:15:00 -
[87] - Quote
Here's another issue CCP. Why are Concord and the gate/stations guns not subject to Tidi like everyone else? Smaller ships are being instapopped by them while people sit and wait 30 seconds to lock.
Working as intended?
Looking to stamp out apiphobia in my lifetime..... |
Shai 'Hulud
Guiding Hand Social Club
20
|
Posted - 2012.04.28 19:20:00 -
[88] - Quote
You have never been able to shoot pods of players with higher sec. status than -5.0 unless at war or in same corp, while in high sec (without incurring a gcc yourself). Also, there has not been a "check box" to remove the warning for actions that provoke a gcc in high sec. for a LONG time now.
They changed the display of pods in gcc state, but you still get the warning and the rules did not change.
(There is a bug where you don't get the warning before shooting, but this has to do with a tidi bug) |
Aeron Sophus
Sebiestor Tribe Minmatar Republic
1
|
Posted - 2012.04.28 21:18:00 -
[89] - Quote
CCP Greyscale wrote:Aeron Sophus wrote:CCP Greyscale wrote:Adriel Malakai wrote:CCP Greyscale wrote:
If that's the case then please file a bug report immediately - the CONCORD pop-up should not be suppressible (and wasn't when I was testing on SiSi yesterday).
Just tested this - it appears you removed the check box in Escalation. Please tell me you were at least intelligent enough to have a check-box for low sec. AFAIK it has *always* been the case that the CONCORD pop-up is the only non-suppressible confirmation dialogue in the game. Lowsec warnings have always had one AFAIK. None of this should have been changed in Escalation, but I can go check against previous expansions on a reference server if it's bothering you Uhm... Weren't you (or Masterplan, I forgot.) talking about messing with these checkboxes in your talk at fanfest? For the redesign we're hoping to do over the summer, yes. Not for this release, though I don't know what kind of version control you use internally (if any - and god I hope you do, I think someone trolled CCP Veritas about that at Fanfest and he got rather evasive...) but could it be possible that something slipped into this release? I mean you DID implement the server sided under the hood crime watch changes this patch around - at least according to the patch notes. |
|
CCP Greyscale
C C P C C P Alliance
1256
|
Posted - 2012.04.28 21:38:00 -
[90] - Quote
Aeron Sophus wrote:CCP Greyscale wrote:Aeron Sophus wrote:CCP Greyscale wrote:Adriel Malakai wrote:CCP Greyscale wrote:
If that's the case then please file a bug report immediately - the CONCORD pop-up should not be suppressible (and wasn't when I was testing on SiSi yesterday).
Just tested this - it appears you removed the check box in Escalation. Please tell me you were at least intelligent enough to have a check-box for low sec. AFAIK it has *always* been the case that the CONCORD pop-up is the only non-suppressible confirmation dialogue in the game. Lowsec warnings have always had one AFAIK. None of this should have been changed in Escalation, but I can go check against previous expansions on a reference server if it's bothering you Uhm... Weren't you (or Masterplan, I forgot.) talking about messing with these checkboxes in your talk at fanfest? For the redesign we're hoping to do over the summer, yes. Not for this release, though I don't know what kind of version control you use internally (if any - and god I hope you do, I think someone trolled CCP Veritas about that at Fanfest and he got rather evasive...) but could it be possible that something slipped into this release? I mean you DID implement the server sided under the hood crime watch changes this patch around - at least according to the patch notes.
I'm reasonably sure that this hasn't happened, on the basis that I don't think our version control software supports integration of code that hasn't actually been written yet
(I'm sure Explorer will be along shortly to confirm/deny!) |
|
|
|
|
|
Pages: 1 2 [3] 4 5 :: one page |
First page | Previous page | Next page | Last page |