Pages: [1] 2 3 :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
PHPR Ronin
|
Posted - 2007.07.09 03:55:00 -
[1]
Step 1) Have your filters set to prompt for dangourous actions (to avoid being concoreded) Step 2) Shield rep a friend (no prompt for dangourous action Step 3) He had auto-target back on (normally no big deal) Step 4) game client was glitched and his missle launcher was apperently set to auto-fire Step 5) he fired on me once targeted (since were not in the same corp.. concordegeddon) Caldari navy raven down... Step 6) Missles never actually hit (server log proves this) (missle's always hit dont they?) Step 7) CNR pilot is flagged as a criminal Step 8) still no "dangouos act" prompt Step 9) I get flagged as a criminal. Step 10) concordegeddon BBQ rapege.
Yes I normally just run missions and am what the general public calls a "carebear" but there is a bug in the client and the GM's dont care so I am posting this hear as a warning for all those pilots. Don't shield rep non-corp mates, and be careful of even shield repping corp mates as you will likely loose your ship and CCP will not re-imburse it and they have no desire to hear about the bug either thru the petition system or thru the bug report tool.
you are warned.
|
Dr Cron
Northern Lights Number 5
|
Posted - 2007.07.09 04:01:00 -
[2]
DURR
oh noez did I forgot a smiley face in my post? |
Cdr Foxbat
Vanguard Frontiers INVICTUS.
|
Posted - 2007.07.09 04:04:00 -
[3]
That one has been around for years................
Problem is its hard to tell if you are repping a friend who accidently shot YOU, or repping a friend who intentionaly shot someone else and wants to remote tank concord.
Any change would have the high sec NPC hunters using and abusing it: "shield rep my ship!!!" then opening fire on the poor guy that helped them.......
Originally by: Marduk Felzhen
Originally by: Vorian Atraties i bid my kidney...
i bid his other kidney
|
Tarminic
Black Flame Industries
|
Posted - 2007.07.09 04:05:00 -
[4]
1. Concord destroys missiles in flight, I believe 2. He got CONCORDED because he fired on you. End of story. 3. You were shield-repping someone being CONCORDED, which could be used as an exploit to avoid losing your ship to concord, therefore you received a firm CONCORDOKKEN. What exactly are you complaining about? LAG IBTL! IBDS/DC! IBTC! 1st in a BoB post! And other such forum tom-foolery. |
PHPR Ronin
|
Posted - 2007.07.09 04:18:00 -
[5]
Originally by: Tarminic 1. Concord destroys missiles in flight, I believe 2. He got CONCORDED because he fired on you. End of story. 3. You were shield-repping someone being CONCORDED, which could be used as an exploit to avoid losing your ship to concord, therefore you received a firm CONCORDOKKEN. What exactly are you complaining about?
The problem lies that I was shield repping him before he became a criminal. I should have been given a chance to shut down my reppers before i was also flagged. Maybe an automatic shutdown "Sheild rep module has been deactived because your target is now a global criminal" or perhaps a message stating "if you continue to shield rep %playername% then you will be flagged as a criminal"
I'm complaining that I have my client set specifically to avoid being concorded for stupid acts of dumbness. I'm sure if I targeted someone after they were globally flagged as a criminal and then activated my remote shield rep I would be given the option, but because i was shield repping him before he did a criminal act I was also flagged without warning or a chance to avoid it.
|
PHPR Ronin
|
Posted - 2007.07.09 04:19:00 -
[6]
Originally by: Cdr Foxbat That one has been around for years................
Problem is its hard to tell if you are repping a friend who accidently shot YOU, or repping a friend who intentionaly shot someone else and wants to remote tank concord.
Any change would have the high sec NPC hunters using and abusing it: "shield rep my ship!!!" then opening fire on the poor guy that helped them.......
You would think that if both players involved (non corp mates) had their standings set to 10 that concord/CCP would be smart enough to realize it was an oops and not come in to "save the day"
|
Plutoinum
German Cyberdome Corp Cult of War
|
Posted - 2007.07.09 04:21:00 -
[7]
Originally by: PHPR Ronin
Step 6) Missles never actually hit (server log proves this) (missle's always hit dont they?)
Ok, don't know, what happened, maybe lagged.
But the hit itself doesn't trigger concord response, but the gun/launcher activation already. You can even get on the killmail, although your missiles never hit him, because he popped before they were there afaik, except the mail is truncated ofc.
|
Santa Anna
Caldari Blackguard Brigade
|
Posted - 2007.07.09 04:25:00 -
[8]
Originally by: PHPR Ronin Step 1) Have your filters set to prompt for dangourous actions (to avoid being concoreded) Step 2) Shield rep a friend (no prompt for dangourous action Step 3) He had auto-target back on (normally no big deal) Step 4) game client was glitched and his missle launcher was apperently set to auto-fire Step 5) he fired on me once targeted (since were not in the same corp.. concordegeddon) Caldari navy raven down... Step 6) Missles never actually hit (server log proves this) (missle's always hit dont they?) Step 7) CNR pilot is flagged as a criminal Step 8) still no "dangouos act" prompt Step 9) I get flagged as a criminal. Step 10) concordegeddon BBQ rapege.
Very interesting. /me notes this phenomenon for future use.
_____ Heat Warfare |
Midarin
|
Posted - 2007.07.09 04:31:00 -
[9]
Originally by: PHPR Ronin Step 3) He had auto-target back on (normally no big deal)
Very dangerous setting. Do not use.
Quote: Step 4) game client was glitched and his missle launcher was apperently set to auto-fire
It's not a glitch. We call this "cycling" your weapons and modules. If you turn on a module but it can't actually come on (most commonly because the target is out of range or completely off grid) it will stay on until you target something else at which point it comes on automatically, or until there is a session change like jumping through a gate or docking at which point the modules go back to normal.
You can use this to your advantage when fighting. Click on all the relevant weapons and other modules and then click in your overview or in space on some object that is way off grid (like a far away gate). Then when your target appears, you just start targeting him like normal. As soon as you have a lock, all cycled modules instantly turn on your target at once.
|
Draconyx
|
Posted - 2007.07.09 04:34:00 -
[10]
Believe it or not you just reproduced one of the most common scams around. That is why you get those nice warnings when you join a group in high sec.
|
|
Big Al
The Aftermath
|
Posted - 2007.07.09 04:43:00 -
[11]
Auto Target is always a no-no if you have out of corp support ships on you in empire.
You and your friend have learned a lesson.
fwiw, if you need remote support in a CNR for missioning you are doing something wrong in the first place.
we ran outta cowbell. |
Taikun
Gallente Serenity Prime Praesidium Libertatis
|
Posted - 2007.07.09 04:57:00 -
[12]
Originally by: Tarminic 1. Concord destroys missiles in flight, I believe 2. He got CONCORDED because he fired on you. End of story. 3. You were shield-repping someone being CONCORDED, which could be used as an exploit to avoid losing your ship to concord, therefore you received a firm CONCORDOKKEN. What exactly are you complaining about?
Umm lets see... he wasn't complaining, he was informing.
You on the other other hand came forth and baically parroted his warning and tried to stick the knife in accusing him of complaining.
Where I come from we call folks like you a troll. Trolls by the forum rules are NOT welcome.
Perhaps you shoudl consider THAT next time you see fit to respond to anyones post. Ever.
To the OP. Thanks for the reminder of this issue. Obviously CCP and their game mechanics department are too busy holding fan-faire than fixing long known outstanding issues with the game.
Taikun
-----------------------------------
For lack of a better word ladies and gentlemen... Greed is good. |
Tarminic
Black Flame Industries
|
Posted - 2007.07.09 05:09:00 -
[13]
Originally by: Taikun
Originally by: Tarminic 1. Concord destroys missiles in flight, I believe 2. He got CONCORDED because he fired on you. End of story. 3. You were shield-repping someone being CONCORDED, which could be used as an exploit to avoid losing your ship to concord, therefore you received a firm CONCORDOKKEN. What exactly are you complaining about?
Umm lets see... he wasn't complaining, he was informing.
You on the other other hand came forth and baically parroted his warning and tried to stick the knife in accusing him of complaining.
Where I come from we call folks like you a troll. Trolls by the forum rules are NOT welcome.
Perhaps you shoudl consider THAT next time you see fit to respond to anyones post. Ever.
To the OP. Thanks for the reminder of this issue. Obviously CCP and their game mechanics department are too busy holding fan-faire than fixing long known outstanding issues with the game.
Taikun
The subject of the post was "How to have CCP Legally steal your battleship with no warning."
Originally by: Websters Complain: To express dissatisfaction, pain, uneasiness, censure, resentment, or grief; find fault
I think it can be easily said that based on the content of the title, the OP was complaining because the title of the post is obviously expressing dissatisfaction. Otherwise he would have made a title like "Beware - remote repping someone being CONCORDED is Bad" Stealing implies that it was taken from him wrongfully. And I would hardly call accusations that someone is complaining "sticking the knife in." I would advise you to calm down.
Quote: Where I come from we call folks like you a troll. Trolls by the forum rules are NOT welcome.
Perhaps you shoudl consider THAT next time you see fit to respond to anyones post. Ever.
According to the most popular entry on Urban Dictionary, a troll is defined as follows:
Originally by: Urban Dictionary Troll: One who posts a deliberately provocative message to a newsgroup or message board with the intention of causing maximum disruption and argument
I don't believe my message was posted to provoke, cause disruption, or argue. I'm sorry that I offended you, but I don't believe that you're warranted in flying off of the handle like that. Chill.
LAG IBTL! IBDS/DC! IBTC! 1st in a BoB post! And other such forum tom-foolery. |
evs
|
Posted - 2007.07.09 06:05:00 -
[14]
he doesnt even have to shoot at you..he can target one of your drones...even a repper drone, and the same thing will happen
|
Lance Fighter
|
Posted - 2007.07.09 06:11:00 -
[15]
wait a sec. Something is wrong here when I can gank a mission runner with his drones idle by shooting his drone... I mean, seriously.
|
Tarminic
Black Flame Industries
|
Posted - 2007.07.09 06:14:00 -
[16]
Originally by: Lance Fighter wait a sec. Something is wrong here when I can gank a mission runner with his drones idle by shooting his drone... I mean, seriously.
Well, it's kind of a mutual-gank since both of you would lose your ships. And do drones always aggress a player firing on them? I haven't tested this theory myself, and drone behavior isn't always consistent. LAG IBTL! IBDS/DC! IBTC! 1st in a BoB post! And other such forum tom-foolery. |
Lance Fighter
|
Posted - 2007.07.09 06:17:00 -
[17]
Originally by: Tarminic
Originally by: Lance Fighter wait a sec. Something is wrong here when I can gank a mission runner with his drones idle by shooting his drone... I mean, seriously.
Well, it's kind of a mutual-gank since both of you would lose your ships. And do drones always aggress a player firing on them? I haven't tested this theory myself, and drone behavior isn't always consistent.
if they are orbiting the player who controls them, they will attack anything that agress them. But still, all i need is a frigate to pwn a CNR!
|
Tarminic
Black Flame Industries
|
Posted - 2007.07.09 06:20:00 -
[18]
Originally by: Lance Fighter
Originally by: Tarminic
Originally by: Lance Fighter wait a sec. Something is wrong here when I can gank a mission runner with his drones idle by shooting his drone... I mean, seriously.
Well, it's kind of a mutual-gank since both of you would lose your ships. And do drones always aggress a player firing on them? I haven't tested this theory myself, and drone behavior isn't always consistent.
if they are orbiting the player who controls them, they will attack anything that agress them. But still, all i need is a frigate to pwn a CNR!
Hrm...now THAT could be a problem. I've never heard of that actually being done, however, so either it hasn't gotten out (until now) or most mission runners know better than to have their drones out anywhere other when they're already fighting something, which makes sense to me. LAG IBTL! IBDS/DC! IBTC! 1st in a BoB post! And other such forum tom-foolery. |
Lance Fighter
|
Posted - 2007.07.09 06:23:00 -
[19]
hmm true. I would not know where to start on mission probing though :(
|
Tarminic
Black Flame Industries
|
Posted - 2007.07.09 06:27:00 -
[20]
Originally by: Lance Fighter hmm true. I would not know where to start on mission probing though :(
Wouldn't work that well - drones that the player has already ordered will continue to attack their original targets (or other targets that have already aggressed the controller) even if they're attacked, meaning that your only opportunity would be when drones are orbiting around his ship without orders. You would either have to arrive with him AFK, or catch him in the moments after the NPCs are defeated but before he pulls his drones into the hangar, in addition to being close enough to his drones to have them actually fire on you before CONCORD finishes grinding you into dust. LAG IBTL! IBDS/DC! IBTC! 1st in a BoB post! And other such forum tom-foolery. |
|
Lance Fighter
|
Posted - 2007.07.09 06:32:00 -
[21]
Originally by: Tarminic
Originally by: Lance Fighter hmm true. I would not know where to start on mission probing though :(
Wouldn't work that well - drones that the player has already ordered will continue to attack their original targets (or other targets that have already aggressed the controller) even if they're attacked, meaning that your only opportunity would be when drones are orbiting around his ship without orders. You would either have to arrive with him AFK, or catch him in the moments after the NPCs are defeated but before he pulls his drones into the hangar, in addition to being close enough to his drones to have them actually fire on you before CONCORD finishes grinding you into dust.
You speak truth. i figure, exec, AB, nano fit, something, civvie gatling. Get as close as you can when the last rat is going down, lock a drone, as SOON as the thing pops go pewpew right next to it :)
|
BluOrange
Gallente Agony Unleashed Agony Empire
|
Posted - 2007.07.09 08:02:00 -
[22]
Originally by: Lance Fighter
Originally by: Tarminic
Originally by: Lance Fighter wait a sec. Something is wrong here when I can gank a mission runner with his drones idle by shooting his drone... I mean, seriously.
Well, it's kind of a mutual-gank since both of you would lose your ships. And do drones always aggress a player firing on them? I haven't tested this theory myself, and drone behavior isn't always consistent.
if they are orbiting the player who controls them, they will attack anything that agress them. But still, all i need is a frigate to pwn a CNR!
No, because the CNR has to be remote repping you for the concordokken to claim him after they claim you. Now, it does happen, and there's almost always 'pilot error' in there somewhere, but once you aggress him, he's allowed to aggress you back.
Recruitment FAQ |
Banana Torres
The Green Banana Corporation
|
Posted - 2007.07.09 08:04:00 -
[23]
Originally by: Tarminic
Originally by: Lance Fighter
Originally by: Tarminic
Originally by: Lance Fighter wait a sec. Something is wrong here when I can gank a mission runner with his drones idle by shooting his drone... I mean, seriously.
Well, it's kind of a mutual-gank since both of you would lose your ships. And do drones always aggress a player firing on them? I haven't tested this theory myself, and drone behavior isn't always consistent.
if they are orbiting the player who controls them, they will attack anything that agress them. But still, all i need is a frigate to pwn a CNR!
Hrm...now THAT could be a problem. I've never heard of that actually being done, however, so either it hasn't gotten out (until now) or most mission runners know better than to have their drones out anywhere other when they're already fighting something, which makes sense to me.
Or because it doesn't work that way. As soon as the frigate fired on the CNR he would become crimainally flagged so the CNR's drones can attack him with no CONCORD response.
See ex-Privateers have their uses, an in depth knowledge of fighting in high sec.
|
Cipher7
OldBastardsPub SMASH Alliance
|
Posted - 2007.07.09 10:20:00 -
[24]
The person you were repping locked and fired on you, he got concorded.
While he was being concorded you were repping him, so you got concorded.
lol
Ya know we've all done alot of stupid things. Most normal people don't waste the GM's time petitioning our boneheaded mistakes.
So you sit in empire and do missions. Great. Then you can afford to buy your friend and yourself new ships. Not like you ever lose anything anyway.
|
yarrmarr
Beyond Divinity Inc
|
Posted - 2007.07.09 10:39:00 -
[25]
Originally by: Cipher7 The person you were repping locked and fired on you, he got concorded.
While he was being concorded you were repping him, so you got concorded.
lol
Ya know we've all done alot of stupid things. Most normal people don't waste the GM's time petitioning our boneheaded mistakes.
So you sit in empire and do missions. Great. Then you can afford to buy your friend and yourself new ships. Not like you ever lose anything anyway.
useless troll.
In my opinion the repping victim got concorded the moment his repper started the next cycle after the CNR became flagged. It shouldn't be that difficult (and probably a very nice gesture, highly appreciated by mission runners and high sec pvp'ers) to have the program do a check on the status of the target before the cycle initiates.
|
Braineater
Minmatar BINFORD
|
Posted - 2007.07.09 11:10:00 -
[26]
Originally by: PHPR Ronin Step 3) He had auto-target back on (normally no big deal) Step 4) game client was glitched and his missle launcher was apperently set to auto-fire
Seems to me that 3) is the real cause of trouble here. Everything else that has happened is a valid consequence of the preceding action, so I really don't see the point of this complaint. But: I'm really curious about how many deaths this setting has actually caused, maybe it's time to set it to zero by default... could imagine a few logistics pilots getting shot at by gang mates while camping because someone hat auto-target back on and his weapons pre-cycling. ______
|
lofty29
Infinitus Odium
|
Posted - 2007.07.09 11:12:00 -
[27]
CONCORD IS STEELIN MAH TARGETS!! ---
Project Mayhem |
Mastin Dragonfly
Absolutely No Return The Red Skull
|
Posted - 2007.07.09 11:14:00 -
[28]
CONCORD should just perma jam you an offline all your modules or something, destroying a ship is excessive, unless the pilot has -5 sec status or lower.
|
Ulii
|
Posted - 2007.07.09 11:16:00 -
[29]
Originally by: Mastin Dragonfly CONCORD should just perma jam you an offline all your modules or something, destroying a ship is excessive, unless the pilot has -5 sec status or lower.
they are there as punishment, not to prevent!
|
OneSock
Silentia Mortalis Curse Alliance
|
Posted - 2007.07.09 11:22:00 -
[30]
Seems a bit daft to me. If you've joined a gang with someone you resign all rights to concord protection. You've effectively entered into a trusted relationship and can shoot each other at will regardless.
At least that's how I'd code it.
|
|
|
|
|
Pages: [1] 2 3 :: one page |
First page | Previous page | Next page | Last page |