Page 8 of 12

Posted: Thu Jan 31, 2008 10:16 pm
by Andon
On another note - Miners may need their mass increased. I boost-rammed an IC miner the other day in an IC light int. Podded myself but sent the miner over 500m from the rock, IIRC.

Posted: Fri Feb 01, 2008 3:01 am
by Lykourgos
You rammed it the wrong way.

Posted: Tue Feb 05, 2008 4:15 pm
by Malicious Wraith
Repeat: Make large con in r4 rammable.

Posted: Tue Feb 05, 2008 6:05 pm
by Dogbones
Malicious Wraith wrote:QUOTE (Malicious Wraith @ Feb 5 2008, 11:15 AM) Repeat: Make large con in r4 rammable.
To Repeat the earlier repeats... This is NOT a code issue, it is a core issue. We fixed a fairly obvious bug (thanks to Factoid) that impacts all collisions not only cons. It makes no sense to either put the bug back or make it apply just to ramming cons, or any other code change that would make them rammable.

Now I'd need to revisit the code and see if there is a scaling factor for mass as well as hull HP and shield HP when dealing out damage to the rammer. If mass is not a factor in the damage equation lowering the large con's mass in the core will not make them rammable again. You will still go 'poof' based on the damage. Now you may nudge them a bit further on that suicide run (if their mass is dropped), but again another look at the code needs to be done to see if the impact still effects the con even if you die.

The current R4 code should allow them to be rammed, you just cannot do it more than once /tongue.gif" style="vertical-align:middle" emoid=":P" border="0" alt="tongue.gif" />
The effect of that initial ram should not have been changed unless the impact calculation is not done in the event of the rammers destruction.

Dog

Posted: Tue Feb 05, 2008 6:08 pm
by Malicious Wraith
Dogbones wrote:QUOTE (Dogbones @ Feb 5 2008, 01:05 PM) To Repeat the earlier repeats... This is NOT a code issue, it is a core issue. We fixed a fairly obvious bug (thanks to Factoid) that impacts all collisions not only cons. It makes no sense to either put the bug back or make it apply just to ramming cons, or any other code change that would make them rammable.

Now I'd need to revisit the code and see if there is a scaling factor for mass as well as hull HP and shield HP when dealing out damage to the rammer. If mass is not a factor in the damage equation lowering the large con's mass in the core will not make them rammable again. You will still go 'poof' based on the damage. Now you may nudge them a bit further on that suicide run (if their mass is dropped), but again another look at the code needs to be done to see if the impact still effects the con even if you die.

The current R4 code should allow them to be rammed, you just cannot do it more than once /tongue.gif" style="vertical-align:middle" emoid=":P" border="0" alt="tongue.gif" />
The effect of that initial ram should not have been changed unless the impact calculation is not done in the event of the rammers destruction.

Dog
I did not say "Dev's, fix it."

I said "Fix it."

Someone, ANYONE, needs to fix this.

Posted: Tue Feb 05, 2008 6:10 pm
by guitarism
He doesn't get it Dogbones, don't bother.

Posted: Tue Feb 05, 2008 6:41 pm
by Raveen
Malicious Wraith wrote:QUOTE (Malicious Wraith @ Feb 5 2008, 04:15 PM) Repeat: Make large con in r4 rammable.
They are rammable. Thanks for your interest.

Posted: Tue Feb 05, 2008 7:52 pm
by Dajimmy10101
Yes you can ram into them just fine... you don't like phase through them the only problem is you'll be the one to bounce off.

Posted: Tue Feb 05, 2008 9:08 pm
by Malicious Wraith
guitarism wrote:QUOTE (guitarism @ Feb 5 2008, 01:10 PM) He doesn't get it Dogbones, don't bother.
Guitarism. Please leave quietly. Stop trying to speak for me, and about me, when you dont understand the situation, or me.

Here, let me give you some hints to help you grasp what I was asking.

ANYONE = Includes Noir.

Noir = Controls the DN Core.

Controlling the DN Core = You can change large con mass.


I hope that makes it easier for you to understand. Perhaps not.

Posted: Tue Feb 05, 2008 10:02 pm
by spideycw
Isn't this a code issue not a core issue?