After the update to version 1.0, good job by the way, all file I/O done by the modding community seems to have a cap on how big of a file it can read, and write. This causes huge issues for all mod makers, we use File I/O to export information which the server ends up using to load features on start. It has completely broken some add-ons on the workshop, and only limits the imagination of mod makers as time moves on. Please change.
- Operating System
- Windows 10 x64
- Operating System Version
Use EnforceScript to export something like JSON information, or just a huge text file.
Thanks! The update 1.0 introduced some limitations to the file writing capability of the scripts. The file count and individual file sizes are limited. While we could alter the file size limit (reasonably), it's very likely that the overall cap will remain the same.
For instance, we have a json file which holds all of the spawn points the server owners choose to allow their players to spawn at; however, due to either File I/O, or file serialization. Now, we cannot export these files. It simply will not write them, and I would assume that wouldn't read them either.
5MB is still way too small. Instead of doing it per individual file size, make it so there is a cap of 500mb per folder.
Also make it so server owners have the option of modifying the max cap for folder sizes and so they can enable the creation of folders.
If you won't give us native code execution through extensions or CURL support (even through the hive backend), you should atleast do this for us otherwise, like Paul said in the other thread, without this mods such as HypeTrain or Community Online Tools are effectively dead.