The alternative syntax of callExtension (callExtensionArgs) has a limit of 2048 for its argument array.
Removing this limit will get it on par with the original syntax and allow for easier parsing on the extension side.
Description
Details
- Severity
- Tweak
- Resolution
- Open
- Reproducibility
- N/A
- Operating System
- Windows 11 x64
- Category
- Feature Request
Event Timeline
Transfering the state of the entire game and all players, objects, AI, vehicles so it can be shared between servers. Less extensions calls -> less overhead
You could make it a giant string, the limit for that is 9megabytes? With 2048 arguments, you can pass 19GiB in one extension call.
That should be plenty.
We also have toJson now to generate a giant string.
But, passing it to extensions is very annoying because it double-quotes the string. I want to fix that anyways.
Wouldn't removing the double quoting be considered a breaking chnage, as extensions would need to be edited to not handle it anymore.
2.22 and next prof RVFeature_ArgumentNoEscapeString can be used to prevent strings from being escaped.
Making it much easier (and more efficient) to pass and parse large strings, for example json as you don't need to fix the double-quoting.
That shall be enough :u