What's the deal with damaged modules after patch

I've notice 1% damage on my modules, repped them in station, undocked and they are damaged again... My corpmate has them 2.5% damaged

Also, after each undock more and more modules are damaged

First time got all the modules, repped, got 1% back damage on guns and few low, after next undock without repping got all but one 1% damaged...

So what's the deal here? Modules are damaging themselves because of the usage?

I took 2.5% damage on one of my three blasters, and never overheated them. Had to repair them in the station.

Wear and tear on ships equipment is a new feature read the patch notes.

Wear and tear on ships equipment is a new feature read the patch notes.

Wear and tear on ships equipment is a new feature read the patch notes.

and they are fine now? or are they damaged again?

I went back out and ran a mission. When I came back, I had 2 damaged blasters and a damaged rig. Rats never got through my shields. They were all at 2.5% again.

This is likely my fault, I've been tinkering around with the code that applies the damage (I know scary ****) and as a result this might have changed. There has always been a feature where damage is supposed to leak to the modules but it might very well be that we start leaking a bit too early now.

What ships were you guys flying and did you take a lot of hull damage?

nvm some of you said only slight shield damage. I'll take a look tomorrow morning.

This is likely my fault, I've been tinkering around with the code that applies the damage (I know scary ****) and as a result this might have changed. There has always been a feature where damage is supposed to leak to the modules but it might very well be that we start leaking a bit too early now.

What ships were you guys flying and did you take a lot of hull damage?

nvm some of you said only slight shield damage. I'll take a look tomorrow morning.

This is likely my fault, I've been tinkering around with the code that applies the damage (I know scary ****) and as a result this might have changed. There has always been a feature where damage is supposed to leak to the modules but it might very well be that we start leaking a bit too early now.

What ships were you guys flying and did you take a lot of hull damage?

nvm some of you said only slight shield damage. I'll take a look tomorrow morning.

Jesus...This is where the probelm lies.

Why, just like the inventory, would you even screw with something that was never broken?

This is likely my fault, I've been tinkering around with the code that applies the damage (I know scary ****) and as a result this might have changed. There has always been a feature where damage is supposed to leak to the modules but it might very well be that we start leaking a bit too early now.

What ships were you guys flying and did you take a lot of hull damage?

nvm some of you said only slight shield damage. I'll take a look tomorrow morning.

Its actually been broken for years now. modules getting damage after bleeding structure was supposed to be in YEARS ago.

This is likely my fault, I've been tinkering around with the code that applies the damage (I know scary ****) and as a result this might have changed.

Same here, mods and rigs dmged. This is one buggy update, I'm rly confused about what the update was for now O_o
Useless inventory boxes, added lag for missle smoke trails, which is ridiculous, cause there would be no smoke trails in the void of space. WTF is goin on there over at ccp?

If your trying to win an award for "Worst update ever released by a software company", I think u may have won it with this P O S

Wait youre saying its partially intentional? IS this meant to be a new ISK sink then?

And how often is it SUPPOSED to be happening? Cause seriously, how shittily made ARE these modules O.o

Or are we getting new Star Trek shields?

Seriously, watch Undiscovered country some time. When the hole is BLOWN THROUGH THE SAUCER someone says theyre down to 25% shields lol

Smoke is essentially particles of matter and gases.. what about that wouldn't be visible in space? Besides, I watched the Falcon9 launch last night and there was definitely smoke trails of a sort coming off the booster when the were achieving orbit before deploying the solar panels and heading off to the International Space station.

Smoke is essentially particles of matter and gases.. what about that wouldn't be visible in space? Besides, I watched the Falcon9 launch last night and there was definitely smoke trails of a sort coming off the booster when the were achieving orbit before deploying the solar panels and heading off to the International Space station.

This is likely my fault, I've been tinkering around with the code that applies the damage (I know scary ****) and as a result this might have changed. There has always been a feature where damage is supposed to leak to the modules but it might very well be that we start leaking a bit too early now.

What ships were you guys flying and did you take a lot of hull damage?

nvm some of you said only slight shield damage. I'll take a look tomorrow morning.

Wait youre saying its partially intentional? IS this meant to be a new ISK sink then?

And how often is it SUPPOSED to be happening? Cause seriously, how shittily made ARE these modules O.o

Or are we getting new Star Trek shields?

Seriously, watch Undiscovered country some time. When the hole is BLOWN THROUGH THE SAUCER someone says theyre down to 25% shields lol

Let me clarify. Every layer leaks a bit of damage to the next layer when it is sufficiently damage. You start taking a little armor damage while still having some shield remaining and you start taking some hull damage even though have some armor left. This is especially obvious when shooting some structures in missions. However a little known fact is that when your structure gets low then your module take damage. However by that time your structure is so low that you likely exploded and there is a chance that the ship exploded before there was chance to damage the modules. So to sum up, yes this is a feature and always has been but you've likely never noticed it.

As to why mess with stuff that isn't broken. Well it may not seem like broken to you guys but it was broken to us. The code was so complex and weird (and not a single comment in sight) that nobody dared touch it. That is usually not a good place to be in because it means if we want to make any changes to it we need to either, hack it in to the current code and hope it works or simply rewrite it in a way we understood. We opted for the latter.

lol, no it's not.

Let me clarify. Every layer leaks a bit of damage to the next layer when it is sufficiently damage. You start taking a little armor damage while still having some shield remaining and you start taking some hull damage even though have some armor left. This is especially obvious when shooting some structures in missions. However a little known fact is that when your structure gets low then your module take damage. However by that time your structure is so low that you likely exploded and there is a chance that the ship exploded before there was chance to damage the modules. So to sum up, yes this is a feature and always has been but you've likely never noticed it.

As to why mess with stuff that isn't broken. Well it may not seem like broken to you guys but it was broken to us. The code was so complex and weird (and not a single comment in sight) that nobody dared touch it. That is usually not a good place to be in because it means if we want to make any changes to it we need to either, hack it in to the current code and hope it works or simply rewrite it in a way we understood. We opted for the latter.

Let me clarify. Every layer leaks a bit of damage to the next layer when it is sufficiently damage. You start taking a little armor damage while still having some shield remaining and you start taking some hull damage even though have some armor left. This is especially obvious when shooting some structures in missions. However a little known fact is that when your structure gets low then your module take damage. However by that time your structure is so low that you likely exploded and there is a chance that the ship exploded before there was chance to damage the modules. So to sum up, yes this is a feature and always has been but you've likely never noticed it.

As to why mess with stuff that isn't broken. Well it may not seem like broken to you guys but it was broken to us. The code was so complex and weird (and not a single comment in sight) that nobody dared touch it. That is usually not a good place to be in because it means if we want to make any changes to it we need to either, hack it in to the current code and hope it works or simply rewrite it in a way we understood. We opted for the latter.

Let me clarify. Every layer leaks a bit of damage to the next layer when it is sufficiently damage. You start taking a little armor damage while still having some shield remaining and you start taking some hull damage even though have some armor left. This is especially obvious when shooting some structures in missions. However a little known fact is that when your structure gets low then your module take damage. However by that time your structure is so low that you likely exploded and there is a chance that the ship exploded before there was chance to damage the modules. So to sum up, yes this is a feature and always has been but you've likely never noticed it.

As to why mess with stuff that isn't broken. Well it may not seem like broken to you guys but it was broken to us. The code was so complex and weird (and not a single comment in sight) that nobody dared touch it. That is usually not a good place to be in because it means if we want to make any changes to it we need to either, hack it in to the current code and hope it works or simply rewrite it in a way we understood. We opted for the latter.

Let me clarify. (...)

As to why (...)

Sorry mate don't take it personal but thats a lot of BS and a lot of words. Our mods NEVER EVER did take damage when we undock/dock er our shields are up. there might be some crazy code that got used in some rare cases but what happens here is completly different.
Why are you guys always playing around with something you have no idea about ? you have some crazy Code in front of you and have no idea what it does. Just DO NOT touch it. Let anyone who have a clue do the Job and then after some testing you make an entry in the patch notes and everything is fine. Project Managment, Testing and Qualitiy Managment anyone ?

Can some real DEV give a statement about it please ? Is it a bug or a feature and where is the entry in the patch notes about it ?

What ships were you guys flying and did you take a lot of hull damage?

relax mate this is definitely a bug. Like I said the code was always there but is now being run when it should not due to a rounding error. It's fixed internally and should be in todays downtime.

@ CCP Tuxford

My draek got broked

PVE Drake, ran 3 missions with no overheating, no hull or armour damage, pic is of repair quote hope it's helpful

First time I've ever seen rigs take a heat hit.

I have never heard of this feature and I troll the forums quite a bit. Just because the code is there and never ran, does not mean you can just dump it on the players all of a sudden and declare it a bug fix.

I have to say, Mr Tuxford owned up to his error, identified offending code and fixed in 24 hrs (if fixed). From my experience of Game programmers, this is quite exceptional behavior. The fact that the code has sat around for this long and no-one could be bothered to sort it out once and for all is more typical.

I fly my ships into deep structure quite often. I have never, ever, taken module damage because of it. I have never heard of this feature and I troll the forums quite a bit.

Maybe you should....
*glasses*
Troll harder.

It has been around for forever, but the module damage you receive is so miniscule you are quite a lot likely to get blown up way before ever noticing it. If you really fly in structure all the time, you just don't remember getting module damage, because it for 100% sure has always been there.

And I agree with the gentlemen above me, the fact that Tuxford admits he (or someone working under him) made a blunder and that a fix is on the way is more than enough of an apology for me. Not that it was a huge inconvenience anyway, at least to me personally, the repairbills were hardly astronomical ( maybe 100k in all thus far?) even in with some faction/t2 mods.

I have had modules damaged when I escaped a few fights with like 1-2% hull left.

I appreciate CCP's speedy response to this bug.

This is likely my fault, I've been tinkering around with the code that applies the damage (I know scary ****) and as a result this might have changed. There has always been a feature where damage is supposed to leak to the modules but it might very well be that we start leaking a bit too early now.

What ships were you guys flying and did you take a lot of hull damage?

nvm some of you said only slight shield damage. I'll take a look tomorrow morning.

I appreciate CCP's speedy response to this bug.

Question: will CCP reimburse pilots for any repair bills filed as a result of this bug?

Yeah, I've seen it too, in 'skin-of-my-teeth' escpaes, and it makes perfect sense. Once your armor is breached. Or even seriously compromised.

But when you're shileds are still robustly solid? Nuh-uh.


Anyway, I'm confident it's been fixed. But still am disturbed that tinkered code was allowed to roll live without testing. Back when *i* did software development (not all THAT long ago), that was a 'fired day before yesterday' offense.

Same here, mods and rigs dmged. This is one buggy update, I'm rly confused about what the update was for now O_o
Useless inventory boxes, added lag for missle smoke trails, which is ridiculous, cause there would be no smoke trails in the void of space. WTF is goin on there over at ccp?

If your trying to win an award for "Worst update ever released by a software company", I think u may have won it with this P O S

I'd ask about the resculpting option, cause I don't seem to have it. But, I'm assuming this, too, is another bug.
I doubt I've found half of the bugs that this update is likely to have, because I've been mostly docked the whole time. I've gone out to do an L4, that took twice as long to finish due to the lag created by missle "trails"(in the vacuum of space O_o), and the inability to loot wrecks now with this new crappy inventory box setup.
And yes I've disabled and tried the 'no missle trail' option, lag is gone but apparently so is the missle, it apparently is fired and does dmg, but seems to travel in another dimension because its not visible at all :P lol

It's not new dude, calm down, they have always taken damage when your in hull. THIS IS NOT NEW IT"S FOUR YEARS OLD

There are many hundreds, likely thousands, of clips of engine burns in actual space, and you can see that they don't, in fact, leave visually-detectable trails in space. Any particulate dense enough to leave a visible trail at missile speeds in space basically means your missile's engines are full of non-performing particulate matter*, and have been designed by drunken monkeys.


*Read: Waste of mass, adding expense and lowering performance.

The evidence is clear; with the recent degrade of updates and the ancient, Earthly thinking. The developers and coders at ccp are either;
1. Extremly old and have yet to discover a lightbulb.
or
2. Extremly young and not out of diapers yet.
;P

Yeah, I've seen it too, in 'skin-of-my-teeth' escpaes, and it makes perfect sense. Once your armor is breached. Or even seriously compromised.

But when you're shileds are still robustly solid? Nuh-uh.


Anyway, I'm confident it's been fixed. But still am disturbed that tinkered code was allowed to roll live without testing. Back when *i* did software development (not all THAT long ago), that was a 'fired day before yesterday' offense.

Let anyone who have a clue do the Job and then after some testing you make an entry in the patch notes and everything is fine. Project Managment, Testing and Qualitiy Managment anyone ?

Can some real DEV give a statement about it please ? Is it a bug or a feature and where is the entry in the patch notes about it ?

There are many hundreds, likely thousands, of clips of engine burns in actual space, and you can see that they don't, in fact, leave visually-detectable trails in space. Any particulate dense enough to leave a visible trail at missile speeds in space basically means your missile's engines are full of non-performing particulate matter*, and have been designed by drunken monkeys.


*Read: Waste of mass, adding expense and lowering performance.

Sorry mate don't take it personal but thats a lot of BS and a lot of words. Our mods NEVER EVER did take damage when we undock/dock er our shields are up. there might be some crazy code that got used in some rare cases but what happens here is completly different.
Why are you guys always playing around with something you have no idea about ? you have some crazy Code in front of you and have no idea what it does. Just DO NOT touch it. Let anyone who have a clue do the Job and then after some testing you make an entry in the patch notes and everything is fine. Project Managment, Testing and Qualitiy Managment anyone ?

Can some real DEV give a statement about it please ? Is it a bug or a feature and where is the entry in the patch notes about it ?

This is likely my fault, I've been tinkering around with the code that applies the damage (I know scary ****) and as a result this might have changed. There has always been a feature where damage is supposed to leak to the modules but it might very well be that we start leaking a bit too early now.

What ships were you guys flying and did you take a lot of hull damage?

nvm some of you said only slight shield damage. I'll take a look tomorrow morning.

Let me clarify his response for you: There was NO dev who had a clue about this piece of code anymore. It was badly written and uncommented code. Thats why they decided to rewrite it, so somebody could actually usefully work with it (in the future). The rewrite was not supposed to lead to any changes ATM. They rewrote the code, put it on Sisi (and probably tested it somewhat, to see if sth. was broken). They did not notice that some damage-leaking to modules now ocurred earlier than it should (which is a minor issue, anyway). So they are now going to look at it and fix it.

What is the big deal?

I doubt it was with no testing - it was likely that the testers did not think outside of the test case. The code is supposed to damage the underlying stuff when the layer above is low. I bet they tested that and it works fine. They just didn't think to check what happens when the layer above is full.

Anyone working in a complex codeset with screaming customers wanting new features Now Dammit (I do) will understand how it happens. It sucks, and is not a good business practice, but it will happen. At least the damage from this one was minimal, just a tiny bit of ISK compared to the ship you are flying.

Why are you guys always playing around with something you have no idea about ? you have some crazy Code in front of you and have no idea what it does. Just DO NOT touch it. Let anyone who have a clue do the Job and then after some testing you make an entry in the patch notes and everything is fine. Project Managment, Testing and Qualitiy Managment anyone ?

no.. 90% of the players havent quit... I think that award would go to NGE or CU
Compared to THAT this is a non issue

OR the Boot.ini issue

Well I dunno, there was a Japanese (I think) MMO company that deleted all the game data during a downtime and didnt have any backups, so they effective lost the entire game. I dont think it gets worse than THAT



Sorry but they shouldnt have to not update the game cause your computer sucks.
Like that one update that made it so a certain % of the game couldnt play anymore.

Get a better PC

And dude, I have a PC I bought on the cheap (less than $400) like 4 years ago.... and I dont have the issue youre talking about
ATI Radeon 4650 lol my **** is olllld

edit: fixed thanks to dev's explanation

Our modules damage themselves by firing them and you think they werent made by alcoholic monkeys?



Jeez, this guys tears are like an energy drink

Our modules damage themselves by firing them and you think they werent made by alcoholic monkeys?

That make so much sense, seeing as eve runs my life support machines here.

This is likely my fault, I've been tinkering around with the code that applies the damage (I know scary ****) and as a result this might have changed. There has always been a feature where damage is supposed to leak to the modules but it might very well be that we start leaking a bit too early now.

What ships were you guys flying and did you take a lot of hull damage?

nvm some of you said only slight shield damage. I'll take a look tomorrow morning.