Death Warrant Forums

I'd just like the radius and damage of the projectile to appear to have a connection. A number of times I've gotten wacked for 100s of points of lost health from fireballs that appeared from my perspective to miss me completely. Drop the radius to 1/2 to 1/3 or so of what it is now (or whatever it is in UUs that match up with the visual display) and make the damage consistent would be my vote.

Any date to when the pet raptor and razor fly will be fixed?

DW_Ant wrote:Na, it the difference in memory is unnoticeable if the radius is 64 uu and 4096 uu.

The concern is the damage radius seems unrealistically large compare to the size of the fireball. The fire ball stretches up to an average of 128 uu (guessing), but the blast radius is up to 1200 (that's slightly less than the length of the Akbal's double damage room across).

I guess the question should be, do you want the radius (not damage) to be turned down?

I would vote for a radius cap. Many times I've seen players get wiped out from something seemingly unrealistic in comparison to every other blast damage hit possible in the game. $0.02

TigerRaptorFX wrote:Any date to when the pet raptor and razor fly will be fixed?

This weekend most likely.

decrease this fireball radius first ... a friend showed me how it looks like ... disaster, and yes, so unrealistic

Here is th e tracert bombzin asked for. server has epic lag always now since changes ip again. won't let me post it to other thread.

Tracing route to ip220.208-100-49.static.steadfast.net [208.100.49.220]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 6 ms 11 ms 16 ms 10.19.43.1
3 16 ms 12 ms 19 ms 172.30.8.161
4 28 ms 28 ms 25 ms 12.116.225.205
5 21 ms 17 ms 21 ms cr84.cgcil.ip.att.net [12.122.132.162]
6 20 ms 19 ms 22 ms cr2.cgcil.ip.att.net [12.123.7.250]
7 19 ms 17 ms 21 ms cgcil01jt.ip.att.net [12.122.86.41]
8 25 ms 19 ms 22 ms 192.205.35.78
9 18 ms 19 ms 35 ms ae-3.r20.chcgil09.us.bb.gin.ntt.net [129.250.2.2
0]
10 108 ms 211 ms 236 ms po-2.r00.chcgil09.us.bb.gin.ntt.net [129.250.4.1
13]
11 25 ms 30 ms 24 ms xe-8-2.r00.chcgil09.us.ce.gin.ntt.net [128.242.1
79.22]
12 206 ms 253 ms 26 ms vl26.core3.chi01.steadfast.net [208.100.32.25]
13 30 ms 31 ms 32 ms ip220.208-100-49.static.steadfast.net [208.100.4
9.220]

Trace complete.

DW_Ant wrote:The problem with mech queens is that they are resource consuming. When they shoot out 12 mines that don't blow up until a player nears it, and their heath is set to 234k hp, while they never put their shield down...That increases channel counts and reduce player's frames per second. We want to minimize the mech queens.

Is there any chance of bringing back the blood queens and replacing the mech queens especially for wave 15? Wave 15 already has mine titans so there'd still be plenty of enemy mines.

warhead2 wrote:Here is th e tracert bombzin asked for. server has epic lag always now since changes ip again. won't let me post it to other thread.

Tracing route to ip220.208-100-49.static.steadfast.net [208.100.49.220]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 6 ms 11 ms 16 ms 10.19.43.1
3 16 ms 12 ms 19 ms 172.30.8.161
4 28 ms 28 ms 25 ms 12.116.225.205
5 21 ms 17 ms 21 ms cr84.cgcil.ip.att.net [12.122.132.162]
6 20 ms 19 ms 22 ms cr2.cgcil.ip.att.net [12.123.7.250]
7 19 ms 17 ms 21 ms cgcil01jt.ip.att.net [12.122.86.41]
8 25 ms 19 ms 22 ms 192.205.35.78
9 18 ms 19 ms 35 ms ae-3.r20.chcgil09.us.bb.gin.ntt.net [129.250.2.2
0]
10 108 ms 211 ms 236 ms po-2.r00.chcgil09.us.bb.gin.ntt.net [129.250.4.1
13]
11 25 ms 30 ms 24 ms xe-8-2.r00.chcgil09.us.ce.gin.ntt.net [128.242.1
79.22]
12 206 ms 253 ms 26 ms vl26.core3.chi01.steadfast.net [208.100.32.25]
13 30 ms 31 ms 32 ms ip220.208-100-49.static.steadfast.net [208.100.4
9.220]

Trace complete.

Hmm. Silly routing they have you going through colorado to get to chicago

Hop 10 in colorado is where the problem begins ,hopefully they will get their router fixed soon.

omg i am in northern indiana that kind of route is crazy. who's fault is this, my ISP (Mediacom), or something to do with whatever is hosting your box?

warhead2 wrote:omg i am in northern indiana that kind of route is crazy. who's fault is this, my ISP (Mediacom), or something to do with whatever is hosting your box?

Unfortunately, routing is completely out of our hands. So, it's not anything to do with our host. Giving a copy of your traceroute to your ISP would be the first place to start. After that, it's up to your ISP to kick it up the line with -their- providers.

KKat