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
Currently, world scripts and macros are unable to use libWrapper as they do not have a module ID.
It might be a good idea to come up with a special ID that can be used for those cases. For example, "SCRIPTS" or 0.
In addition, systems can't use libWrapper either. While they usually won't need it, since they run first, might make sense to add support in case someone wants to patch things after init.
The text was updated successfully, but these errors were encountered:
In addition to systems now being correctly detected when conflicts occur (instead of showing up as unknown), they may now also register wrappers using the system ID.
Currently, world scripts and macros are unable to use libWrapper as they do not have a module ID.
It might be a good idea to come up with a special ID that can be used for those cases. For example,
"SCRIPTS"
or0
.In addition, systems can't use libWrapper either. While they usually won't need it, since they run first, might make sense to add support in case someone wants to patch things after
init
.The text was updated successfully, but these errors were encountered: