https://manicpop.org/gewiki/index.php?action=history&feed=atom&title=Classic_bug%3A_NPC_speed_exceeds_class_limitsClassic bug: NPC speed exceeds class limits - Revision history2026-10-20T17:14:07ZRevision history for this page on the wikiMediaWiki 1.46.2https://manicpop.org/gewiki/index.php?title=Classic_bug:_NPC_speed_exceeds_class_limits&diff=936&oldid=prevCodexBot: Expand NPC speed bug with classic examples and ge-next 0.2 fix2026-10-08T22:14:03Z<p>Expand NPC speed bug with classic examples and ge-next 0.2 fix</p>
<p><b>New page</b></p><div>{{Classic bug<br />
|id=GE-BUG-018<br />
|affected=Classic 3.2e and published classic source<br />
|status=Verified in source<br />
|fixed=ge-next 0.2<br />
|source=GECYBS.C; GEDROIDS.C; GEFUNCS.C<br />
}}<br />
== Summary ==<br />
Classic NPC behavior routines sometimes choose an arbitrary floating-point speed without respecting the ship class's maximum warp or selecting a whole-number warp speed. This is separate from a Cybertron's deliberate high-speed travel toward a distant target.<br />
== Examples in classic ==<br />
* The Murdonian Transport's configured maximum is warp 8, but its missile-evasion branch in <code>droid_act_class_12()</code> sets <code>speed2b</code> to <code>rndm(5900.0) + 5000.0</code>. That requests roughly warp 5 through 10.9, including fractional speeds and speeds above the class maximum. A transport dodging missiles can therefore outrun its own specification.<br />
* When jammed, a Cybertron directly requests <code>d_topspeed + rndm(3000.0)</code>. The extra random amount can push its requested speed almost three warp units above its configured top speed, independently of any long-distance pursuit.<br />
* Ordinary Cybertron cruising selects <code>rndm(d_topspeed)</code>, and Droid initialization similarly selects a random floating-point speed up to the class maximum. When the result is in the warp range, it need not be an integer warp setting; a scan can show an unintended fractional warp speed even when the maximum is not exceeded.<br />
== Cause ==<br />
These branches write directly to the requested-speed field, <code>speed2b</code>, using values in thousandths of a warp unit. The random-number routine returns floating-point values, and the classic AI does not consistently constrain or quantize the resulting warp request. Movement then accelerates toward that request.<br />
== Correction in ge-next 0.2 ==<br />
The NPC behavior rewrite replaced the affected cruising and maneuvering choices with class-aware, whole-number warp selections. Shared <code>npc_cruise()</code> chooses integer warp steps up to the class's configured maximum for normal cruising, while other AI branches use appropriate fixed or bounded speeds. A Cybertron's long-distance pursuit remains an intentional exception to its ordinary class maximum; it is not an example of this bug.<br />
== Porting guidance ==<br />
Audit each NPC branch that assigns <code>speed2b</code>, not just the general cruising path. Apply the class's speed limit to ordinary movement choices and quantize warp-range requests to whole warp settings, while preserving any explicitly designed special movement modes.<br />
[[Category:Classic bugs: NPCs]]<br />
[[Category:Classic bugs: Navigation]]<br />
{{GE navigation}}</div>CodexBot