BDv20b Error

[Jeimuzu73]

I can't start up BD because of an apparent character error, but I checked line 610 and no such offending character exists.

---

OS: Windows NT (NT 10.0) Build 10586

M_LoadDefaults: Load system defaults.
Using program directory for storage
W_Init: Init WADfiles.
adding F:/GZDoom/gzdoom.pk3, 613 lumps
adding F:/GZDoom/DOOM2.WAD, 2919 lumps
adding F:/GZDoom/Brutal Doom/Brutal Doom - Hell on Earth Starter Pack/brutalv20b.pk3, 8370 lumps
adding F:/GZDoom/Brutal Doom/Brutal Doom - Hell on Earth Starter Pack/brutalv20b.pk3:e2m8.wad, 11 lumps
adding F:/GZDoom/Brutal Doom/Brutal Doom - Hell on Earth Starter Pack/brutalv20b.pk3:e3m8.wad, 11 lumps
adding F:/GZDoom/Brutal Doom/Brutal Doom - Hell on Earth Starter Pack/brutalv20b.pk3:terrain.wad, 260 lumps
adding F:/GZDoom/Doom 2 Maps/dd1024.wad, 98 lumps
adding F:/GZDoom/regeneration3.wad, 5 lumps
I_Init: Setting up machine state.
CPU speed: 2592 MHz
CPU Vendor ID: GenuineIntel
Name: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
Family 6, Model 94, Stepping 3
Features: MMX SSE SSE2 SSE3 SSSE3 SSE4.1 SSE4.2
I_InitSound: Initializing FMOD
FMOD Sound System, copyright © Firelight Technologies Pty, Ltd., 1994-2009.
Loaded FMOD version 4.44.60
V_Init: allocate screen.
S_Init: Setting up sound.
ST_Init: Init startup screen.
Checking cmd-line parameters...
S_InitData: Load sound definitions.
G_ParseMapInfo: Load map definitions.
Texman.Init: Init texture manager.
ParseTeamInfo: Load team definitions.
LoadActors: Load actor definitions.
Attempt to get invalid state See from actor ImpTorso.
Attempt to get invalid state See from actor DeadImp.
Bad hex number: no

Execution could not continue.

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

Line 610:

Code: Select all

BPDL AAAAAAAAA 1 A_FadeOut(0.l,0)

Help will be rewarded with much kudos.

[Hellser]

Look closely. l and 1. That should be 0.1, not 0.l.

[Nevander]

How does an error like that get past testing? Assuming the mod is tested first.

[Hellser]

At one point, 0.l would've worked. But thanks to the mod creator's infinite wisdom, he decided to use 0.l instead of 0.1. There's no reason why anyone would've used 0.l instead of 0.1.

[Jeimuzu73]

Spotted it and fixed it, thanks. Almost looked like a 1 to me due to the font.

[Jimmy]

brb laughing forever

What the heck numeric value does 0.l actually translate to??

[_mental_]

What the heck numeric value does 0.l actually translate to??

It translates to zero. Before scripting merge it was treated as zero of long double type. There is no such type in DECORATE, so Randi removed the L suffix and this expression became an error.

[Kinsie]

Yeah, this popped up recently in the Johnny Doom thread.

Now I know why Graf drinks.

[Redfox123]

[quote="Kinsie"]Yeah, this popped up recently in the Johnny Doom thread.

Now I know why Graf drinks.[/quote
i wonder what Graf thinks of that

[Gez]

It's a quality of life feature; GZDoom is helpfully preventing you from wasting your limited and valuable time on a bad mod.

[Rachael]

It's a quality of life feature; GZDoom is helpfully preventing you from wasting your limited and valuable time on a bad mod.

Sometimes you cannot tell someone that the stove is hot. Sometimes they just have to put their hand on it themselves.

[Graf Zahl]

I find it most troubling that after almost half a year, this bug still hasn't been fixed in the mod. Well, it'll mess up things quite thoroughly when I do the next GZDoom release (which may take a few more weeks because right now it's summer and soon vacation time...)

[Edward-san]

Is the mod author still around the internet?

[Hellser]

Yes, but through ModDB and Facebook. He's been banned from every forum related to Doom that you can imagine.

[Gez]

He's only banned from zdoom.org AFAIK. For example if you look at one of his Doomworld threads he doesn't seem to be banned there.