Chaosforge Forum
DoomRL => Discussion => Topic started by: Kornel Kisielewicz on December 15, 2007, 08:30
-
Here's one strange thing about the way DoomRL works now -- this applies to *all* explosion damage projectiles -- damage is done twice, but in a way that was realy surprising to me!
-- player damage for RL and BFG at a direct hit deals the listed damage first
-- monster damage at hit always deals 1d7 damage
-- after the initial damage explosion damage kicks in based on a internal chart -- only this damage is "splashed"
Now if we take together the figures we have:
Rocket Launcher : 4d4+5d6
BFG : 8d8+8d6
Imp: 1d7+2d6
Caco:1d7+3d5
Knight: 1d7+3d4
Baron: 1d7+4d5
Mancubi: 1d7+4d6
For monsters this isn't bad, the 1d7 impact damage isn't so bad, but for the player, I'd like to rework that because of two reasons:
-- the damage indicator on the weapon is false
-- the splash damage get's calculated only using a part of the damage
Oh, and the initial idea that I had when I was looking for this code was to increase the damage of the Rocket Launcher.
Any idea how to rework them, without throwing the balance off hand? Should direct hit damage be left alone?
-
I would remove direct hit damage for splash weapons but then evasion has to work on splash damage as well.
-
I would remove direct hit damage for splash weapons but then evasion has to work on splash damage as well.
Seconded, though for BFG I'd change splash to that classical 8d8 damage. RL will be better with having 5d6 damage as per splash currently (let's be honest - 4d4 is far too weak for an rocket hit).
-
Duh, this problem is still not solved, please help!
Another facet of the problem has just emerged -- Knockback of the direct target is calculated BEFORE explosion! What does that mean? That in open space a monster would be hit by the 4d4 rocket, and then pushed back out of the 5d6 center of explosion. OTOH if it was with it's back to the wall then it would take full 5d6+4d4 damage. If I would remove the initial impact then what to do with the knockback? An explosion centered on the monster wont knock it back at all...
-
How about leaving initial explosion but making it do 0 damage (and add an random knockback, based on weapon)?
-
*comes out of lurking*
If it just the problem of the weapon damage being shown incorrectly to the player then why not show it as (4d4) + (5d6) instead of just (4d4)?
*goes back to lurking*
-
*comes out of lurking*
If it just the problem of the weapon damage being shown incorrectly to the player then why not show it as (4d4) + (5d6) instead of just (4d4)?
*goes back to lurking*
Because 4d4+5d6 RL would be bah-ro-ken :P
-
*comes out of lurking*
If it just the problem of the weapon damage being shown incorrectly to the player then why not show it as (4d4) + (5d6) instead of just (4d4)?
*goes back to lurking*
Because 4d4+5d6 RL would be bah-ro-ken :P
*Reads the topic again. Still doesn’t get it*
Why would it be broken? Is it just because you won’t always do the 4d4 bit of 4d4+5d6 damage to all the monsters? But then the same applies to shotguns too, you don’t always do the damage indicated either.
Sorry if I’m being a n00b.
-
*comes out of lurking*
If it just the problem of the weapon damage being shown incorrectly to the player then why not show it as (4d4) + (5d6) instead of just (4d4)?
*goes back to lurking*
Because 4d4+5d6 RL would be bah-ro-ken :P
*Reads the topic again. Still doesn’t get it*
Why would it be broken? Is it just because you won’t always do the 4d4 bit of 4d4+5d6 damage to all the monsters? But then the same applies to shotguns too, you don’t always do the damage indicated either.
Sorry if I’m being a n00b.
Because it would be too strong... okay, maby not for RL (as kornel just increased the damage to 6d6 - listed damage mind you), but 8d8+8d6 bfg is sheer overkill.
-
Huh? Isn’t Kornel saying that the 4d4+5d6 thingy is how it works now and he was thinking of changing it so the damage shown to the player is correct, no?
So if that is how it works now, then there can be no balance issues with just a visual change, right?..
*really confused*
-
It is "as it works now" but it isn't "as it should work". Explosions weren't intended to hit twice.