2025-07-21 16:59 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0003861Spring engineGeneralpublic2013-08-22 19:55
ReporterGoogle_Frog 
Assigned ToKloot 
PrioritynormalSeveritymajorReproducibilityalways
StatusresolvedResolutionreopened 
Product Version94.1.1+git 
Target VersionFixed in Version 
Summary0003861: BeamLaser does not hit if it starts within hitvolume
DescriptionBeamLaser weapons do not hit units if they start within the unit's hitvolume. This can make it hard for some units with long guns to defend themselves at close range. In 91.0 beamlasers hit the unit if they start inside it.
Steps To ReproduceZK:
 * Spawn comm_econ_cai on team 0
 * Spawn corpyro next to it on team 1
TagsNo tags attached.
Checked infolog.txt for Errors
Attached Files

-Relationships
+Relationships

-Notes

~0011357

Kloot (developer)

Can't reproduce with 94.0 and zk 1.2.2.4 (see demo).

That same zk version and a 94+ dev-build spams Lua errors and is unusable.

~0011359

Google_Frog (reporter)

The bug is present in 94.1.1-980.

There was a screw up with version numbering. v1.2.2.4 is 6 months old, the latest stable is 1.1.8.2. Also it is best to use the latest test version because it is most likely to work. The current test version works well enough to demonstrate this bug.

Upon retesting I've found corpyro to be unreliable. Sometimes the commander weapon sticks out of the back of the corpyro hitvolume. It is more reliable with a larger unit, the new test is below.
 * Spawn comm_econ_cai on team 0
 * Spawn dante next to it on team 1
+Notes

-Issue History
Date Modified Username Field Change
2013-06-23 12:43 Google_Frog New Issue
2013-06-23 12:43 Google_Frog File Added: screen00310.png
2013-08-22 13:02 Kloot File Added: mantis3861.sdf
2013-08-22 13:02 Kloot Note Added: 0011357
2013-08-22 13:02 Kloot Status new => closed
2013-08-22 13:02 Kloot Assigned To => Kloot
2013-08-22 13:02 Kloot Resolution open => unable to reproduce
2013-08-22 18:04 Google_Frog Note Added: 0011359
2013-08-22 18:04 Google_Frog Status closed => feedback
2013-08-22 18:04 Google_Frog Resolution unable to reproduce => reopened
2013-08-22 19:29 Kloot Status feedback => assigned
2013-08-22 19:55 Kloot Changeset attached => spring develop 4b047a6c
2013-08-22 19:55 Kloot Status assigned => resolved
+Issue History