What and why? This is the result of accidentally locking myself in my room and ultimate boredom ):
This might not really be useful to a lot of people but helpful for anybody who compiles their scripts (at either server or client side) as compiled nut (cnut) files.
Highlights: - Compiles all files in one click, no configuration required.
- Directory structure is retained.
- Errors from all files are displayed after compiling.
Instructions (https://github.com/vancityspiller/.nut-Compile-Tool#readme)
Preview: [spoiler=Server Side Compiling](https://i.imgur.com/6LXsAGw.gif)[/spoiler]
[spoiler=Client Side Compiling](https://i.imgur.com/AdU3p2d.gif)[/spoiler]
[spoiler=Error Handling](https://i.imgur.com/etZm03f.png)[/spoiler]
Links: Virus Report. (https://www.virustotal.com/gui/file/ce7db19ce74cef6b51ae4f10dd5dd18df4b0a2b8ab91560d8bd0a9134e9e961c/detection)
GitHub Repository. (https://github.com/vancityspiller/.nut-Compile-Tool)
Download. (https://github.com/vancityspiller/.nut-Compile-Tool/releases/tag/v1.1)
Nice work.
As a bonus provide a parameter or a way to retain the actual file extension as nut even once compiled. Some people (including myself) just like to keep the file extension same for my compiled files.
Quote from: DizzasTeR on Dec 11, 2020, 09:08 AMNice work.
As a bonus provide a parameter or a way to retain the actual file extension as nut even once compiled. Some people (including myself) just like to keep the file extension same for my compiled files.
Thanks,
Added support for extensions, compiled files will have whatever extension you provide in extension.ini. (both client and server side)
Quote from: UncleRus on Dec 12, 2020, 07:14 AMYou can send for 32 bit os?
(https://i.imgur.com/aESzbGi.jpg)