Proposed changes for Elwynor: Difference between revisions
No edit summary |
No edit summary |
||
| Line 2: | Line 2: | ||
* [https://github.com/elwynor/elwge/commit/4b1aee3c05c8fb7cd03d14f32a249e6833803aba warp rotation bounds check fix] – When specifying a direction to rotate when using the warp command, if an out-of-bounds degree is entered (outside of -180 to 180), the "helm is damaged" error will show. This restructures the command to avoid that. | * [https://github.com/elwynor/elwge/commit/4b1aee3c05c8fb7cd03d14f32a249e6833803aba warp rotation bounds check fix] – When specifying a direction to rotate when using the warp command, if an out-of-bounds degree is entered (outside of -180 to 180), the "helm is damaged" error will show. This restructures the command to avoid that. | ||
* [https://github.com/elwynor/elwge/commit/3ddefff629389296c9705c616051156abf342f37 fix for cybs not pursing user on channel 0] – Once a game has loaded all NPCs, Cybertrons will not pursue a ship on user channel 0. Before a Cyb is dispatched to a ship, notclaimed() in GECYBS.C will check to see if this ship is already claimed ("cybmine") by the maximum amount of pursuers. However, since Droids do not set a cybmine value, they default to 0, and notclaimed() counts them. As such, Cybs will never claim this ship. This adds a specific Cyborg check to notclaimed() and adds a cybmine=255 to all new Droids, correcting the problem. | * [https://github.com/elwynor/elwge/commit/3ddefff629389296c9705c616051156abf342f37 fix for cybs not pursing user on channel 0] – Once a game has loaded all NPCs, Cybertrons will not pursue a ship on user channel 0. Before a Cyb is dispatched to a ship, notclaimed() in GECYBS.C will check to see if this ship is already claimed ("cybmine") by the maximum amount of pursuers. However, since Droids do not set a cybmine value, they default to 0, and notclaimed() counts them. As such, Cybs will never claim this ship. This adds a specific Cyborg check to notclaimed() and adds a cybmine=255 to all new Droids, correcting the problem. | ||
* | *[https://github.com/elwynor/elwge/commit/88056e9bd8ce4bb700527de409f6e22bb67ea245 cyberbases should never move] – Cyberbases should never move, but if you attack one and flee without destroying it, it will attempt to pursue using cyb_check_lockon(). Since its max_accel value is 0, it is unable to rotate. Therefore, it will set itself to a high warp speed, never find the ship it is attempting to pursue, and crash into the galactic barrier. This excludes all cybs with max_accel == 0 from movement routines. | ||
Revision as of 15:55, 27 December 2025
- fix MAXPLSE off-by-one – MAXPLSE is the maximum amount of planets in a sector. By default this is 5, but an off-by-one issue in GEPLANET.C causes it to be one fewer. This fixes the issue and changes the default to 4 so there is no change in actual gameplay defaults.
- warp rotation bounds check fix – When specifying a direction to rotate when using the warp command, if an out-of-bounds degree is entered (outside of -180 to 180), the "helm is damaged" error will show. This restructures the command to avoid that.
- fix for cybs not pursing user on channel 0 – Once a game has loaded all NPCs, Cybertrons will not pursue a ship on user channel 0. Before a Cyb is dispatched to a ship, notclaimed() in GECYBS.C will check to see if this ship is already claimed ("cybmine") by the maximum amount of pursuers. However, since Droids do not set a cybmine value, they default to 0, and notclaimed() counts them. As such, Cybs will never claim this ship. This adds a specific Cyborg check to notclaimed() and adds a cybmine=255 to all new Droids, correcting the problem.
- cyberbases should never move – Cyberbases should never move, but if you attack one and flee without destroying it, it will attempt to pursue using cyb_check_lockon(). Since its max_accel value is 0, it is unable to rotate. Therefore, it will set itself to a high warp speed, never find the ship it is attempting to pursue, and crash into the galactic barrier. This excludes all cybs with max_accel == 0 from movement routines.