source = sfs_fslurp(g_fs, filename, NULL, &source_size); code_string = lstr_from_cp1252(source, source_size); free(source);
install(files("main.js"));
Oh wait. I guess game() isn't where Sphere starts by default anymore. Gotta start reading up on the documentation!
Quote from: DaVince on November 05, 2016, 06:39:38 amOh, I know about that, that's why I always run them in a terminal. But it still wasn't outputting anything by using the minisphere command.No, that's what I meant - even if you have a terminal window, if the executable was compiled as a GUI application, Windows won't allow it to print anything.
Oh, I know about that, that's why I always run them in a terminal. But it still wasn't outputting anything by using the minisphere command.
minisphere 4.3 is out, and it includes a ton of new stuff: the new Dispatch API, promises, Reflect, miniRT enhancements, frame-perfect timing, better Sphere 1.x compatibility (it now runs Kefka's Revenge!), API refactoring, and a bunch of bug fixes. Get it today--and get eaten by a giant pig tomorrow! I'm especially proud of the Dispatch API, as it brings the functionality of Sphere 1.x update, render and delay scripts engine-wide. And you can set up multiple update and render jobs, so it ALSO works like the old hook-list script with the added bonus of being able to control the order using priorities. It's quite useful!