Gzdoom Nodebuilder fail to parse huge comments.

[ibm5155]

Example wad with more than 4000 chars on a single comment.
Gzdoom builder can load and save that file but gzdoom/nodebuilder doesn't like to read that string.

[_mental_]

What's the error you got? Because I'm getting 'No player 1 start' which means that map was loaded fine.

[ibm5155]

This is what happens when I triy to save the map on gzdoom builder BF.
ZZYZX said it was a bug on Gzdoom NodeBuilder so I posted an example wad here.

[_mental_]

Topic's title is completely misleading.
Report sounds like a bug in GZDoom's embedded node builder but it's about an issue of ZDBSP in fact.

The string length limit is hardcoded indeed. Does someone have write access to this repository?

[Graf Zahl]

It's only in ZDBSP which uses an older version of the parser where the parse buffer is a static array. I can extend it but not unlimit it.

[ibm5155]

if map comments aren't used by zdoom, couldn't the parser just ignore what's inside the string and just jump at the end of the ' " ' looking for a ';' symbol?

[Graf Zahl]

This wasn't a bug in GZDoom. Its parser is well capable of handling long strings.
But the string buffer in ZDBSP was hardcoded to 4096 bytes, which I just expanded to 40960.

I also had to make a clone of its repo because I got no write access to Randi's.

[ibm5155]

Ty Graf