Pages: 1 2 3 [4] 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 .. 19 :: one page |
|
Author |
Thread Statistics | Show CCP posts - 14 post(s) |
PKlavins
Caldari 3rdlane Industries
|
Posted - 2006.08.29 21:59:00 -
[91]
Originally by: Tobias Sjodin
CLARIFICATIONS PLEASE! DEVS!
Just listen to the feedback,
you claim you listen to your players.
LISTEN!
they may be listening, sure, but we want them to ANSWER!!!
maybe they mistook a shaved gorilla (brought over from summer holidays) for oveur, and started doin wat it said??
I make sigs/banners 5mill each, convo/evemail for details
|
Ikonz
Puppets on Steroids iPOD Alliance
|
Posted - 2006.08.29 22:00:00 -
[92]
So as a 0.0 player, I'm essentially stuck to the same regions I now have BM's for since getting BM's for any other regions is going to be next to impossible. Gee thanks CCP, way to limit my game.
|
Nyabinghi
Minmatar Khumatari Holdings Ushra'Khan
|
Posted - 2006.08.29 22:01:00 -
[93]
I'll try and be constructive here but nerfing cov-ops by not allowing the ships to break lock attempts by cloaking is gotta be the most ridiculous implementation I've seen CCP commit. I can accept not being able to cloak once you are already locked but otherwise cov-ops needs those precious seconds of locking time to cloak and escape. As been stated (and why are players explaining the game to the creators?) cov-ops are the weakest ships in game next to shuttles. They can't shield or armor up to compensate and their sig radius is on the larger end of Frigs. Cov-ops defense IS their cloaks, and now you want to take that away too?
Seriously what's the point in even having cov-ops ships if CCP is gonna nerf them so bad? They take forever to train for, near impossible to fit for what they were designed for, they require the most price inflated module, hulls and armor made of paper...
This move is nothing more than a gift to the gate campers and a kick in stomache to cov-ops pilots everywhere. You don't fix things by breaking more things.
|
Kazoki Zocore
|
Posted - 2006.08.29 22:02:00 -
[94]
Edited by: Kazoki Zocore on 29/08/2006 22:03:17 To everyone that says that Cov Ops is now broken: They are still fixing it!
This first fix is simply a graphical fix to the already existing bug. In build 4557, if a Cov Ops was being locked and cloaked, he was already locked. The secondary problem this caused is that the player doing the cloaking had no idea because of a graphical bug. In build 4560, the main bug still exists, but now pilots will know that they are not cloaked. That is all that is changing.
As to BM copying requiring a person actually doing more work: Huzzah!
|
JFxSummoner
|
Posted - 2006.08.29 22:02:00 -
[95]
Originally by: lizen Edited by: lizen on 29/08/2006 21:49:44 instas just seem like such a pain for everyone, all the time.
why not make it so you can warp to 2km of stationary objects, and leave the min warp distance at 15km for mobile objects?
edit : and make the min warp distance for autopilot be 15km still, so that ppl can't harmlessly autopilot through 0.0
would be all to perfect i wish that kinda logic was used in this game alot more often elimante the instas with manual 2km warp and increase eve performance all the way around
|
RobW1
Caldari Iyen-Oursta Salvage
|
Posted - 2006.08.29 22:04:00 -
[96]
When do we envisage fixing the 20+ other bugs introduced with the last patch?
|
Purgatori
Minmatar Cutting Edge Incorporated RAZOR Alliance
|
Posted - 2006.08.29 22:05:00 -
[97]
Originally by: Kazoki Zocore Edited by: Kazoki Zocore on 29/08/2006 22:03:17 To everyone that says that Cov Ops is now broken: They are still fixing it!
This first fix is simply a graphical fix to the already existing bug. In build 4557, if a Cov Ops was being locked and cloaked, he was already locked. The secondary problem this caused is that the player doing the cloaking had no idea because of a graphical bug. In build 4560, the main bug still exists, but now pilots will know that they are not cloaked. That is all that is changing.
As to BM copying requiring a person actually doing more work: Huzzah!
End ur self ? We play a game t o spend all night copying BM's ? riggght..
|
Gift
Amarr Loot
|
Posted - 2006.08.29 22:05:00 -
[98]
Originally by: Kazoki Zocore Edited by: Kazoki Zocore on 29/08/2006 22:03:17 To everyone that says that Cov Ops is now broken: They are still fixing it!
This first fix is simply a graphical fix to the already existing bug. In build 4557, if a Cov Ops was being locked and cloaked, he was already locked. The secondary problem this caused is that the player doing the cloaking had no idea because of a graphical bug. In build 4560, the main bug still exists, but now pilots will know that they are not cloaked. That is all that is changing.
As to BM copying requiring a person actually doing more work: Huzzah!
I hope this is the case.
|
Swillin
|
Posted - 2006.08.29 22:06:00 -
[99]
It seems every game at some point in time has "that patch". Dragon looks to be the one for eve. How companies continue down paths with the entire player bases screaming no is beyond me. The threads on queuing so far have been overwhelmingly a plea for it to stop.
This patch will ensure that basic travel in this game broken. Please please take a look at past gaming companies who did exactly this thing and saw their subscription count plummet. I haven't been playing this game long enough yet to watch all the friends I have made leave.
Lastly it never seems a good idea to break someone's career path without fixing it. To say that covert ops is a high enough priority to make such drastic changes but not patch it until some later patch doesn't make any sense. Fix it all now or wait until a time when you can fix it all. Why gimp it now when it doesn't seem to be a game breaking mechanic? Did someone up there get podded.. heh
|
Lo3d3R
Implant Liberation Front
|
Posted - 2006.08.29 22:06:00 -
[100]
nerf the BM copying = good
nerf the cov-ops: when getting locked but there is not a full lock it still uncloaks or doesnt cloak at all = wtf ?
just remove the whole BM near gates, just use warp to member if you want to instajumpt a gate so badly... and get on with the game, must say again that cov-ops thing is really - wtf - ___________________
Eating Chopped Bear: |
|
Chewan Mesa
Beagle Corp
|
Posted - 2006.08.29 22:06:00 -
[101]
Originally by: Kazoki Zocore Edited by: Kazoki Zocore on 29/08/2006 22:03:17 To everyone that says that Cov Ops is now broken: They are still fixing it!
This first fix is simply a graphical fix to the already existing bug. In build 4557, if a Cov Ops was being locked and cloaked, he was already locked. The secondary problem this caused is that the player doing the cloaking had no idea because of a graphical bug. In build 4560, the main bug still exists, but now pilots will know that they are not cloaked. That is all that is changing.
As to BM copying requiring a person actually doing more work: Huzzah!
It shouldnt require more work ,it should be removed and a new solution put in.
Concering the Cov Ops, it does definetly sound like a "greater fix", not like "we are just fixing the latest bug"...
Did you hire someone from SOE lately?
|
Velax
UNICORN Squadron
|
Posted - 2006.08.29 22:06:00 -
[102]
"Bookmark copying is now limited to 5 bookmarks at a time. Attempting to copy more than 5 bookmarks will result in only 5 being copied."
Holy ****. :S BMs have become one of those thingsthat you need in order to survive. some regions are around 600+ bms, thats going to take a LONG time and be boring.
"If a ship that is being targeted, and cloaks, the lock will now guarantee the uncloak effect occurs."
Thats makes covert ops almost useless. :S
"The missing warping sound effect has returned."
\0/
|
Skarsnik
Caldari A.W.M Knights Of the Southerncross
|
Posted - 2006.08.29 22:07:00 -
[103]
Have to say I normally support what CCP do, it normally makes sense, but this time, I really believe this is slightly off the rails.
Please do tell us what your thinking CCP, this is truely the craziest thing you've ever gone and done in the name of balance and fixes. ------------------------------------------------- AWMCorp is Recruiting
EVE-Ink - An Tattoo Project Based on EVE-Online |
RobW1
Caldari Iyen-Oursta Salvage
|
Posted - 2006.08.29 22:07:00 -
[104]
Originally by: Kazoki Zocore Edited by: Kazoki Zocore on 29/08/2006 22:03:17 To everyone that says that Cov Ops is now broken: They are still fixing it!
This first fix is simply a graphical fix to the already existing bug. In build 4557, if a Cov Ops was being locked and cloaked, he was already locked. The secondary problem this caused is that the player doing the cloaking had no idea because of a graphical bug. In build 4560, the main bug still exists, but now pilots will know that they are not cloaked. That is all that is changing.
As to BM copying requiring a person actually doing more work: Huzzah!
If the above is true, isn't it like driving a car at high speed in to a brick wall, getting out and washing the car... ie just not terribly sensible work?
|
Kusotarre's Alt
|
Posted - 2006.08.29 22:10:00 -
[105]
Originally by: Alex Harumichi This has got to be a joke.
First off, covops ships which are already iffy to fly because they require a currently 60M module (price direct result of sloppy game design with t2 cloaks and the broken BPO system) become instant road kill if anyone so much as manages to start locking them?
Second, the jump queue system, which already has a near-20-page thread detailing why it's killing pvp in the game, will be left as is?
Do the devs have any idea of what the above two will do to the game? Covops are already screwed due to cloak issues, and now this. And since this thread might actually get some proper dev response (unlike aforementioned N-page thread), how about someone official coming here and telling us how:
a) we're supposed to move gangs system-to-system without them trickling one-by-one into the waiting arms of a gate camp
b) we're supposed to escort anything, when the escorts might get randomly separated from the target at any gate?
c) we're supposed to have tactical warfare in general, when any gate might randomly not function with no way to know in advance?
And don't give me crap about "it only happens in major hub system". It happens all the time, sometimes with systems with only 2-3 other people in them. It happens in 1.0. It happens in 0.4. It happens in 0.0. People are losing ships to it all the time, and there is no way they can fight it. Other than not use jump gates.
Seriously, these two points seriously make me question where CCP is headed right now, and if the people in charge have a clue anymore. Or if there really is anyone in charge, is everyone competent in panic mode scrambling after server performance problems and the rest are making these decisions?
If these changes are intended to stay, we need discussion right now about:
1) the complete plan for covert ops and cloaking, assuming there is one. Why was the cloaking change implemented, what problem is it trying to solve.
2) an explanation of how we're supposed to have tactical PVP in the game with the random gate queues, ideally with a discussion of what real problem this was trying to solve (and why that problem is bigger than the disaster it's causing), and an explanation of what the final system will look like.
We're waiting.
And skip the pseudo-funny "we were drunk at the time" stuff, if ceased to be funny some time ago as a response to serious player issues, and just looks like what it is (an attempt to skirt the issue).
QFT. Signed. Stamped. Approved. Agree.
This patch, and the initial Dragon patch itself, are very close to gamebreaking. People aren't exaggerating when they compare the CCP of the past month to SOE. It's that bad.
Do the devs even play this game anymore?
|
FallenX
|
Posted - 2006.08.29 22:10:00 -
[106]
Queue jumps will kill the game
I have 3 accounts, now if queue jumps stay ingame... i will kill all my accounts ... and im not joking
|
ReaperOfSly
Gallente Lyrus Associates Interstellar Starbase Syndicate
|
Posted - 2006.08.29 22:11:00 -
[107]
So instead of fixing the covert ops bug, you're turning it into a nerf. That's absolutley mind-bogglingly hair-rippingly rage-inducingly insane! --------------------------------------------------------------------
|
Karash Amerius
Amarr O.E.C
|
Posted - 2006.08.29 22:11:00 -
[108]
CCP, you have got to address the game mechanic problem that Insta-bookmarks solves if you plan on nerfing the copying time. YOU HAVE GOT TO FIX THE GAME MECHANIC. Right now, fleet commanders that do not have a good set of Insta-bookmarks are seriously disadvantaged against those that do. It is a game breaking issue that needs addressed, not with nerfs and incremental "fixes" like this...But a real comprehensive Navigation system that allows players to master their movements on a larger scale.
The cloak "fix" is a huge mistake. Who called for this?
Merc Blog |
insanebe
Caldari carebear Corp
|
Posted - 2006.08.29 22:13:00 -
[109]
Originally by: kieron
Originally by: Spider Kauphman
Originally by: Patch Notes
* If a ship that is being targeted, and cloaks, the lock will now guarantee the uncloak effect occurs. * Bookmark copying is now limited to 5 bookmarks at a time. Attempting to copy more than 5 bookmarks will result in only 5 being copied.
What what?
The cloaking fix is the first part of a larger fix that will be coming in the near future.
The limitation on bookmark copying is to prevent some players from exploiting game mechanics to lag opponents or crash nodes by copying insane amounts of bookmarks.
arn't GM's supposed to be there to stop and ban exploiters like this,
wouldn't active enforcement of existing rules by banning the guilty be better knowledge is power.... guard it well |
Aelena Thraant
Shadows of the Dead Knights Of the Southerncross
|
Posted - 2006.08.29 22:15:00 -
[110]
Ok I tested the cloaking on the test server. The only thing that changed was now the covert ops decloaks on the covert ops ship. In otherwords.... if your close to locking the covert ops you will lock it but if your not then you won't...
Examples: (Using a Normal Lock time: 7 seconds)
A) Covert Ops decloaks Player starts Locking Covert Cloaks within a second or 2 = Target Lost B) Covert Ops decloaks Player starts Locking Covert Cloaks within 4 seconds of lock = Covert Cloaks Player shoots Covert decloaks
In other words... Cloaking ships are no longer a free pass thru gate camps if there is a fast locker... However if it's a slow locker... Well your safe unless you take a long time to cloak.
|
|
Mervent
Caldari RONA Deepspace Rule of Three
|
Posted - 2006.08.29 22:16:00 -
[111]
Quote:
This has got to be a joke.
First off, covops ships which are already iffy to fly because they require a currently 60M module (price direct result of sloppy game design with t2 cloaks and the broken BPO system) become instant road kill if anyone so much as manages to start locking them?
Second, the jump queue system, which already has a near-20-page thread detailing why it's killing pvp in the game, will be left as is?
Do the devs have any idea of what the above two will do to the game? Covops are already screwed due to cloak issues, and now this. And since this thread might actually get some proper dev response (unlike aforementioned N-page thread), how about someone official coming here and telling us how:
a) we're supposed to move gangs system-to-system without them trickling one-by-one into the waiting arms of a gate camp
b) we're supposed to escort anything, when the escorts might get randomly separated from the target at any gate?
c) we're supposed to have tactical warfare in general, when any gate might randomly not function with no way to know in advance?
And don't give me crap about "it only happens in major hub system". It happens all the time, sometimes with systems with only 2-3 other people in them. It happens in 1.0. It happens in 0.4. It happens in 0.0. People are losing ships to it all the time, and there is no way they can fight it. Other than not use jump gates.
Seriously, these two points seriously make me question where CCP is headed right now, and if the people in charge have a clue anymore. Or if there really is anyone in charge, is everyone competent in panic mode scrambling after server performance problems and the rest are making these decisions?
If these changes are intended to stay, we need discussion right now about:
1) the complete plan for covert ops and cloaking, assuming there is one. Why was the cloaking change implemented, what problem is it trying to solve.
2) an explanation of how we're supposed to have tactical PVP in the game with the random gate queues, ideally with a discussion of what real problem this was trying to solve (and why that problem is bigger than the disaster it's causing), and an explanation of what the final system will look like.
We're waiting.
And skip the pseudo-funny "we were drunk at the time" stuff, if ceased to be funny some time ago as a response to serious player issues, and just looks like what it is (an attempt to skirt the issue).
Concur
|
Rabbitgod
Gallente Celestial Horizon Corp. Ascendant Frontier
|
Posted - 2006.08.29 22:17:00 -
[112]
Edited by: Rabbitgod on 29/08/2006 22:19:18 Ok I think it's clear that the community really does not want these things to happen. So IMO CCP needs to either hold off on these changes and/or explain in a dev blog in great detail, why they are doing it, how will these things work in plain english, and, when the "rest" of the fixing is due.
---{24th member of the 23}---
|
Dave White
Beagle Corp
|
Posted - 2006.08.29 22:17:00 -
[113]
Edited by: Dave White on 29/08/2006 22:17:59
Originally by: Kusotarre's Alt
Originally by: Alex Harumichi This has got to be a joke.
First off, covops ships which are already iffy to fly because they require a currently 60M module (price direct result of sloppy game design with t2 cloaks and the broken BPO system) become instant road kill if anyone so much as manages to start locking them?
Second, the jump queue system, which already has a near-20-page thread detailing why it's killing pvp in the game, will be left as is?
Do the devs have any idea of what the above two will do to the game? Covops are already screwed due to cloak issues, and now this. And since this thread might actually get some proper dev response (unlike aforementioned N-page thread), how about someone official coming here and telling us how:
a) we're supposed to move gangs system-to-system without them trickling one-by-one into the waiting arms of a gate camp
b) we're supposed to escort anything, when the escorts might get randomly separated from the target at any gate?
c) we're supposed to have tactical warfare in general, when any gate might randomly not function with no way to know in advance?
And don't give me crap about "it only happens in major hub system". It happens all the time, sometimes with systems with only 2-3 other people in them. It happens in 1.0. It happens in 0.4. It happens in 0.0. People are losing ships to it all the time, and there is no way they can fight it. Other than not use jump gates.
Seriously, these two points seriously make me question where CCP is headed right now, and if the people in charge have a clue anymore. Or if there really is anyone in charge, is everyone competent in panic mode scrambling after server performance problems and the rest are making these decisions?
If these changes are intended to stay, we need discussion right now about:
1) the complete plan for covert ops and cloaking, assuming there is one. Why was the cloaking change implemented, what problem is it trying to solve.
2) an explanation of how we're supposed to have tactical PVP in the game with the random gate queues, ideally with a discussion of what real problem this was trying to solve (and why that problem is bigger than the disaster it's causing), and an explanation of what the final system will look like.
We're waiting.
And skip the pseudo-funny "we were drunk at the time" stuff, if ceased to be funny some time ago as a response to serious player issues, and just looks like what it is (an attempt to skirt the issue).
QFT. Signed. Stamped. Approved. Agree.
This patch, and the initial Dragon patch itself, are very close to gamebreaking. People aren't exaggerating when they compare the CCP of the past month to SOE. It's that bad.
Do the devs even play this game anymore?
QFT.
Mistakes like this are going to make EVE end up like SWG.
|
Gift
Amarr Loot
|
Posted - 2006.08.29 22:18:00 -
[114]
Edited by: Gift on 29/08/2006 22:21:54
Originally by: Aelena Thraant Ok I tested the cloaking on the test server. The only thing that changed was now the covert ops decloaks on the covert ops ship. In otherwords.... if your close to locking the covert ops you will lock it but if your not then you won't...
Examples: (Using a Normal Lock time: 7 seconds)
A) Covert Ops decloaks Player starts Locking Covert Cloaks within a second or 2 = Target Lost B) Covert Ops decloaks Player starts Locking Covert Cloaks within 4 seconds of lock = Covert Cloaks Player shoots Covert decloaks
In other words... Cloaking ships are no longer a free pass thru gate camps if there is a fast locker... However if it's a slow locker... Well your safe unless you take a long time to cloak.
so a frig or fast lock sniper can stop a covert & a frig, fast lock sniper or a cruiser with a sensor booster can stop recons. Am I understanding you correctly?
Yet another BOOST to sniping, it must be how they want us to play.
|
Helison
Gallente Times of Ancar R i s e
|
Posted - 2006.08.29 22:18:00 -
[115]
Very simple: *) Remove Queues! *) Unnerf cloaking! *) Implement a real BM-fix with Kali!
|
Butter Dog
ISS Navy Task Force Interstellar Starbase Syndicate
|
Posted - 2006.08.29 22:20:00 -
[116]
Edited by: Butter Dog on 29/08/2006 22:20:45
Originally by: Aelena Thraant Ok I tested the cloaking on the test server. The only thing that changed was now the covert ops decloaks on the covert ops ship. In otherwords.... if your close to locking the covert ops you will lock it but if your not then you won't...
Examples: (Using a Normal Lock time: 7 seconds)
A) Covert Ops decloaks Player starts Locking Covert Cloaks within a second or 2 = Target Lost B) Covert Ops decloaks Player starts Locking Covert Cloaks within 4 seconds of lock = Covert Cloaks Player shoots Covert decloaks
In other words... Cloaking ships are no longer a free pass thru gate camps if there is a fast locker... However if it's a slow locker... Well your safe unless you take a long time to cloak.
And what gate camp have you been to which doesnt have an interceptor present?
The Cov Ops thing is a f***ing joke. Never mind how its going to effect stealth bombers... they may as well be thrown in the bin.
|
Malkavian Spirit
Minmatar Instant Travel Inc.
|
Posted - 2006.08.29 22:21:00 -
[117]
*Bookmark copying is now limited to 5 bookmarks at a time. Attempting to copy more than 5 bookmarks will result in only 5 being copied.
just lol... there were 10 page discussion topics on how to change the instas and you guys picked the worst way to nerf bms....
|
Jinx Barker
Gallente Federal Bank
|
Posted - 2006.08.29 22:22:00 -
[118]
Oh Boy!
Guys, you at CCP, the Cov Ops change is madness. If there is a fix, and this is a partial fix, then do not implement it till you are ready to go 100%. This pretty much screws Cov Ops pilots, and people who need to use cov ops to transport valuable stuff and evade gank squads.
Bookmarks copying restriction? Oh man, I understand the need to curb the abuse by some people. However, this means that many a player are now royally screwed. I was never a fan of Gate Camping snipers, where you have 10 tempests and apocs and megas sitting 200k away and busting pods.
So, why this half arsed BM fix? Remove the bookmarks from the game, and introduce a skill that allows something like this:
'Warp Target Calibration' (Rank 4) Prerequisites: Warp Drive Operation L4 Evasive Maneuvering: L4 Science: L3
Description: Warp Target Calibration is a skill that allows the user to shave off 3km off his warp-to-gate distance. At level 5 this skill will allow a user to warp to gate at 0km and initiate insta-jump.
Yea, another must-have-skill, but at least it will help with the lag, rather than screwing over a huge percentage of EVE population who do not have bookmarks.
And frankly, the gate campers will adopt, and find some other way of getting the kicks.
|
RobW1
Caldari Iyen-Oursta Salvage
|
Posted - 2006.08.29 22:24:00 -
[119]
Edited by: RobW1 on 29/08/2006 22:24:39 It seems to me the easiest way to fix BM's is :-
a) Remove all BMs currently in game, except those given out directly by agents. b) Add a Warp to 0km option c) For auto-pilot, leave the default of 15km from the gate.
This way people travelling with their eye on the ball, can do the warp to 0 stuff through empire, and 0.0 space, whilst those on AP use the "regular", "slower" way.
Whatever gets implemented crippling the copying ability of BM's is SURELY not the answer?
|
Gift
Amarr Loot
|
Posted - 2006.08.29 22:25:00 -
[120]
Originally by: Jinx Barker
'Warp Target Calibration' (Rank 4) Prerequisites: Warp Drive Operation L4 Evasive Maneuvering: L4 Science: L3
Description: Warp Target Calibration is a skill that allows the user to shave off 3km off his warp-to-gate distance. At level 5 this skill will allow a user to warp to gate at 0km and initiate insta-jump.
Yea, another must-have-skill, but at least it will help with the lag, rather than screwing over a huge percentage of EVE population who do not have bookmarks.
Just make a warp-in 5km from the gate & remove all bm's from the game.
|
|
|
|
|
Pages: 1 2 3 [4] 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 .. 19 :: one page |
First page | Previous page | Next page | Last page |