Skip to content

Script Fix for Parent call that does not use %this #1752

Merged
Azaezel merged 1 commit into
TorqueGameEngines:developmentfrom
marauder2k9-torque:ScriptFix-ParentCallWithoutThis
May 31, 2026
Merged

Script Fix for Parent call that does not use %this #1752
Azaezel merged 1 commit into
TorqueGameEngines:developmentfrom
marauder2k9-torque:ScriptFix-ParentCallWithoutThis

Conversation

@marauder2k7
Copy link
Copy Markdown
Contributor

@marauder2k7 marauder2k7 commented May 30, 2026

Have explained this in the commented section above the commented out check but callArgv[1] usually refers to %this being passed into a Parent::function, this was creating a state where all parent calls that had arguments but didnt utilize %this it was expecting the first argument to always be an object. Hence if you tried to call a method that took a different argument it incorrectly reported with a misleading error of "unable to find object"

There may be a better way to enforce this rule without commenting it out entirely but due to the nature of the callArgv handle it is always either an object or it isnt. Forcing a break on null causes an issue that shouldnt have been one in a parent call.

Bug Reported by Abbey: https://discord.com/channels/358091480004558848/783127087820439582/1509827504402333848

@Azaezel Azaezel merged commit ebd409c into TorqueGameEngines:development May 31, 2026
2 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants