Killing Floor:Known Issues & Bugs: Difference between revisions

From Tripwire Interactive Wiki
Jump to navigation Jump to search
mNo edit summary
(Added pistol penetration loop bug)
Line 21: Line 21:


This code picks from a random spawn point each time, but doesn't exclude already-tried ones. It means it may waste attempts, and the 'bTryAllSpawns' flag will not work.
This code picks from a random spawn point each time, but doesn't exclude already-tried ones. It means it may waste attempts, and the 'bTryAllSpawns' flag will not work.
==MK23Fire, Magnum44Fire ''Penetration loop'' bug (version 1039)==
MK23Fire, line 41:
<blockquote><pre>While( (HitCount++)<3 )
{
DamageActor = none;
Other = Instigator.HitPointTrace(HitLocation, HitNormal, End, HitPoints, Start,, 1);
if( Other==None )</pre></blockquote>
MK23Fire: line 104:
<blockquote><pre>if( (HCounter++)>=4 || Pawn(DamageActor)==None )
{
Break;
}
HitDamage/=2;</pre></blockquote>
These are both from the penetration loop, and provide conflicting conditions for breaking from the loop. Logically the former block should be checking for a value of 10 (as with DeagleFire.uc), allowing the second block to correctly control the amount of penetrations itself.

Revision as of 01:43, 8 October 2012

ZombieVolume bTryAllSpawns bug (version 1039)

ZombieVolume, line 149:

if( bTryAllSpawns )
{
	// Try spawning in all the points
	NumTries = SpawnPos.Length;
}
else
{
	// Try spawning 3 times in 3 dif points.
	NumTries = 3;
}


for( j=0; j<NumTries; j++ )
{
	TrySpawnPoint = SpawnPos[Rand(SpawnPos.Length)];


This code picks from a random spawn point each time, but doesn't exclude already-tried ones. It means it may waste attempts, and the 'bTryAllSpawns' flag will not work.

MK23Fire, Magnum44Fire Penetration loop bug (version 1039)

MK23Fire, line 41:

While( (HitCount++)<3 )
{
	DamageActor = none;

	Other = Instigator.HitPointTrace(HitLocation, HitNormal, End, HitPoints, Start,, 1);
	if( Other==None )

MK23Fire: line 104:

if( (HCounter++)>=4 || Pawn(DamageActor)==None )
{
	Break;
}
HitDamage/=2;

These are both from the penetration loop, and provide conflicting conditions for breaking from the loop. Logically the former block should be checking for a value of 10 (as with DeagleFire.uc), allowing the second block to correctly control the amount of penetrations itself.