Errors no matter the command.

[aussj4link]

Can anyone please tell me why no matter what I attempt to use, it only produces errors?

[Use]

Hmm, you may need this:

#include "zcommon.acs"

[aussj4link]

That only produces an error too. It seems like the script thing just doesn't work in doom builder. I've tried about a dozen different things all resulting in errors.

[Use]

Get that opening bracket down to line 4, the hudmessage at line 5, and the closing bracket at line 6.

[aussj4link]

No dice. :(

[aussj4link]

Am I using the right settings in DB? I'm going off tutorials on YT and Wiki info, is that a bad idea?

[Use]

No, tutorials tend to be really helpful. Unfortunately my experience with that port are limited so I can't help too much.

[aussj4link]

Which editor do you use?

[Use]

Typically Deepsea but it's not going to help you with GZDoom, GZDoom Builder is much more suited. I only know limited scripting and usually only map for vanilla ports. But don't worry, someone will come along that will look at your script and know what's wrong right away. :)

[Nevander]

Try changing script type to ZDoom ACS.

[aussj4link]

Nevander said:

Try changing script type to ZDoom ACS.

Awesome! Thank you so much. Everyone else I saw doing this had it set to hexen acs.

[scifista42]

Use3D said:

Get that opening bracket down to line 4,

That couldn't possibly have helped anything. The compiler doesn't care whether a whitespace is a space, a tab, a newline, or a randomly mixed sequence of them, it treats all of them the same. The question whether to put the opening bracket onto the same line as the declaration or onto its own next line is just a matter of programming style. I personally prefer putting the opening bracket onto the same line as the declaration, for two reasons: It results in programs with smaller total number of lines, and it's not tempting to accidentally write a semicolon after the declaration if there's already a bracket after it.