WaW GSC compiler?
-
Is there some kind of WaW-specific GSC compiler or something I can use to check where the syntax errors are in my Zombies server's GSC scripts? I was expecting lots of errors because I've pretty much just copied the GSC from my BO2 servers, but I was expecting to be told where to look to fix them. All I get is "bad syntax" and "see console for details" (even though that's the console telling me that :D). No line numbers or anything.
The only thing Google is turning up is this xensik / gsc-tool, but there doesn't seem to be a release download with an EXE.
-
Balrog85 waw compiles scripts at runtime and doesn't require pre-compiled scripts like bo2 so there is no standalone compiler for it. Just pasting code from bo2 will 100% not work as many functions that exist in bo2 don't exist in waw. Can you post your script?
-
Thanks, but it's a pretty big script and will have a lot of things that need modifying to work in WaW. I knew it wouldn't work as it is. I just did it for testing purposes and was hoping it would tell me which line numbers contained errors but it isn't for some reason. I'll probably just brush up on the functions in WaW and rewrite it from scratch.
And sorry for posting in the wrong forum. I forgot about the modding forums and just did it quickly.
-
This post is deleted!
-
Yeah, I tried that and it compiled fine
It's ok, I'm gradually working my way through it, replacing BO2 functions with the WaW equivalents. The file is 1700 lines, so doing it a bit at a time. -
Lol, rookie mistake. Turns out my mystery syntax error was the include lines at the beginning where I'd used forward slashes and it wanted backslashes. Should've been one of the first things I checked :B
-
Balrog85 In waw you can use the developer mode to see erorrs in the console. Use Developer 1 to enable dev mode then use devmap to launch any map using the code name and then when it errors in compile you can use shift+~ to pull the console up to see all errors during compile.
-
Yeah, thanks. I figured out I was missing the developer mode line from my config not long after I made that last post. That's why it wasn't giving me any useful information about the original error.
