DRD Team

The latest GIT builds of GZdoom (13 april 2016) seem to crash when trying to load brutal doom or its affiliates (ketchup etc.)

The log is as follows:

Execution could not continue.

Script error, "brutalv20b.pk3:blood.txt" line 610:
Expected ',', got 'l'.

If anyone could provide context from a more experienced or competent mind, I would be much grateful.

Yours Faithfully, (and apologetically),

-RoastyMytosis

Hi,

I had this issue a couple of days ago.

Its an issue with the "brutalv20b.pk3" file itself. If you open the pk3 file using winzip or any other popular compression tool and open blood.txt in a text editor.
Goto line 610 and you will find that it has a fadeout(0.l) value.

the "l" value should be a number one "1" not a lowercase "L" like it is currently. Save the changes and save it back into the pk3 file.

It should work then

There's no file named "blood.txt"; however, it looks like you meant "BLOOD.txt".

(Mutter, grumble, WIndows users assuming case-insensitive filesystems…)

In GZDoom's context the contents of a PK3 are case insensitive!


About this problem. I find it really disappointing that after more than 3 months this got reported to BD, they still haven't made an update.

Sorry to bump a fairly old thread but Thank you for that fix, changed line 610 as well as 633 and I can play again.

I am having the same issue with the ketchup mod, only its line 545, not 610. The problem is the one is where it's supposed to be and I am not entirely certain what to edit to fix the line.

My 545 looks like this: BPDL AAAAAAAAA 1 A_FadeOut(0.1)

The script error says it expected ',', got 'I'

I know this is for brutal doom, but i figured since ketchup seems to be just the gore effects from brutal doom i figured I'd at least ask if any of you can offer some insight on what to edit.

The line does not say '0.1', but '0.l' but due to a parser error in the GZDoom version the mod was made for the bug went unnoticed.

mine does say (0.1). I copied that line exactly as it was in the code. I did not edit that at all, and yet that is the line that messes up.

Post whole error message or even better complete console log.