General Questions - Help: Bomb Damage Settings in Server .cfg? Anonymous - Mon Feb 21, 2005 3:49 pm Post subject: Help: Bomb Damage Settings in Server .cfg?
Hello,
I'm wondering how I go about changing the bomb damage levels for a particular arena (in this case, lets just say server.cfg).
I don't think its listed under [bomb], or any of the individual ship settings. Any help is appreciated.
By the way, before I get one of those "I use the search button" posts, I did search, but after going through ~7 pages, I couldn't find anything that helped, so I lost hope
Thanks in advance.
Smong - Tue Feb 22, 2005 6:58 am Post subject:
[Bomb]
BombDamageLevel=750
Since all bombs do the same damage at the center point, the only way to get varying damage is with BombExplodePixels, ProximityDistance and BombExplodeDelay. When further away from the blast less damage is taken. (Ok, so this isn't 100% true since prox and damage radius both increase with bomb level, meaning a L3 bomb exploding far away would do the same damage as an L1 bomb exploding nearby).
Shadow-Assassin - Wed Mar 30, 2005 1:37 am Post subject:
I'm having troubles with my bombs. I have the bombDamageLevel set to 800, and yet, by bombs still don't do any damage. What's going on?
Thanks in advance
numpf - Wed Mar 30, 2005 1:32 pm Post subject:
check
[Bomb]
EBombDamagePercent
BBombDamagePercent
These control the percentage of damage that EMP and bouncing bombs do. The number is divided by 10, so 1000 = 100% (normal), 575 = 57% (or just over half damage). 0 would mean those bombs do no damage. You might have forgotten division by 10 so the bombs are doing 80 damage (close to 0).
-numpf
Mine GO BOOM - Wed Mar 30, 2005 2:02 pm Post subject:
Try using an old script I made a while ago for playing around with how much damage bombs do at different distances.
http://www.shanky.com/cgi-bin/ryan/bomb.cgiD1st0rt - Wed Mar 30, 2005 8:29 pm Post subject:
Try turning on *watchdamage and see if it says anything
Shadow-Assassin - Thu Mar 31, 2005 2:27 am Post subject:
Oh, I figured it out. It was the BombExplodeDelay and the BombExplodePixels.