You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 17, 2022. It is now read-only.
Even though cyborg engineer's .droidType JS property is equal to DROID_CONSTRUCT, cyborg engineers don't get enumerated by enumDroid(me, DROID_CONSTRUCT), because enumDroid only considers C-style droid types (so it needs to be called with DROID_CYBORG_CONSTRUCT instead). Same applies to DROID_CYBORG_REPAIR, i think.
Range parameter in enumRange() needs to be converted to world coordinates or something like that.
JS allows placing non-VTOL weapons on VTOLs in buildDroid().
droid.propulsion property returns a body stat name with the same number instead of a propulsion stat name (typo in convDroid()).
Issue migrated from trac:3896 at 2022-04-16 10:49:43 -0700
The text was updated successfully, but these errors were encountered:
.class property should be renamed, since "class" is a reserved keyword.
getWeaponInfo() should return something from time to time.
Probably add some check to make sure psStats in this function is valid, so that the game didn't crash in getStatName but provide a JS assert fail instead.
resolution_fixed
type_bug
| by NoQEven though cyborg engineer's .droidType JS property is equal to DROID_CONSTRUCT, cyborg engineers don't get enumerated by enumDroid(me, DROID_CONSTRUCT), because enumDroid only considers C-style droid types (so it needs to be called with DROID_CYBORG_CONSTRUCT instead). Same applies to DROID_CYBORG_REPAIR, i think.
Range parameter in enumRange() needs to be converted to world coordinates or something like that.
JS allows placing non-VTOL weapons on VTOLs in buildDroid().
droid.propulsion property returns a body stat name with the same number instead of a propulsion stat name (typo in convDroid()).
Issue migrated from trac:3896 at 2022-04-16 10:49:43 -0700
The text was updated successfully, but these errors were encountered: