0002722: Reports errors that don't exist when loading some mods

Notes
(0014793) S_Andrew_S (reporter) 2016-05-02 07:09 edited on: 2016-05-02 07:25	What the? I wouldn't really call this an urgent priority. Wouldn't even put this up on the tracker either; this has an easy work around that the developers shouldn't be bothered to deal with. Please elaborate more - what does your notes in the additional information even mean? Why are you even running this with 4.0? Putting such high priority on a build that isn't even on the developer's concerns is extremely disrespectful in my opinion. This must be a joke.

(0014794) WaTaKiD (updater) 2016-05-02 08:36	i downloaded brutalv20b.pk3 from'http://www.best-ever.org/download?file=brutalv20b.pk3 [^]' and i see that in blood.txt there are 2 occurences of BPDL AAAAAAAAA 1 A_FadeOut(0.l) that is infact a lowercase L by replacing both of them with a 1, the wad successfully loads up, so i believe this was a combination of wad author error (not noticing the typos) and older engine error (previous versions of zan/gzdoom/zdoom allowing said typos to load, which seems fixed in newer versions, as we see here)

(0014795) Edward-san (developer) 2016-05-02 09:22 edited on: 2016-05-02 09:23	zdoom became more restrictive with the decorate syntax. You can see the number of bug reports specific to brutal doom in either zdoom and gzdoom forums. This must be fixed by the mod author. Also, it's nice to see someone testing the 4.0 branch. It would be nice to see people testing other mods with it (not the gameplay, but more likely the startup) in order to catch other errors like these.

(0014797) Edward-san (developer) 2016-05-02 09:32	The title of the ticket is generic enough that it can be used to fill other mods errors.

(0014802) Ultimate Freedoomer (reporter) 2016-05-02 21:05	I'm gonna be testing a few compatibility mods for errors (I have a mod for the Steam Release of Strife: Quest For the Sigil that lets the "veteran edition" stuff work with Zdoom, so there's 1 mod to test).

(0014803) Dusk (developer) 2016-05-02 21:18	In any case this isn't a problem for us to fix.

**Issue Community Support**
This issue is already marked as resolved. If you feel that is not the case, please reopen it and explain why.
Supporters:	No one explicitly supports this issue yet.
Opponents:	S_Andrew_S

Issue Community Support

This issue is already marked as resolved.
If you feel that is not the case, please reopen it and explain why.

Supporters:

No one explicitly supports this issue yet.

Opponents:

S_Andrew_S

Issue History
Date Modified	Username	Field	Change
2016-05-02 03:00	Ultimate Freedoomer	New Issue
2016-05-02 07:09	S_Andrew_S	Note Added: 0014793
2016-05-02 07:10	S_Andrew_S	Note Edited: 0014793	View Revisions
2016-05-02 07:12	S_Andrew_S	Note Edited: 0014793	View Revisions
2016-05-02 07:23	S_Andrew_S	Note Edited: 0014793	View Revisions
2016-05-02 07:25	S_Andrew_S	Note Edited: 0014793	View Revisions
2016-05-02 08:36	WaTaKiD	Note Added: 0014794
2016-05-02 08:40	WaTaKiD	Priority	immediate => normal
2016-05-02 08:40	WaTaKiD	Severity	major => minor
2016-05-02 09:22	Edward-san	Note Added: 0014795
2016-05-02 09:22	Edward-san	Status	new => closed
2016-05-02 09:22	Edward-san	Resolution	open => invalid
2016-05-02 09:23	Edward-san	Note Edited: 0014795	View Revisions
2016-05-02 09:23	Edward-san	Note Edited: 0014795	View Revisions
2016-05-02 09:32	Edward-san	Note Added: 0014797
2016-05-02 09:32	Edward-san	Status	closed => feedback
2016-05-02 09:32	Edward-san	Resolution	invalid => reopened
2016-05-02 09:32	Edward-san	Status	feedback => new
2016-05-02 20:59	Ultimate Freedoomer	Note Added: 0014800
2016-05-02 21:00	Ultimate Freedoomer	Note Deleted: 0014800
2016-05-02 21:05	Ultimate Freedoomer	Note Added: 0014802
2016-05-02 21:18	Dusk	Note Added: 0014803
2016-05-02 21:18	Dusk	Status	new => closed
2016-05-02 21:18	Dusk	Resolution	reopened => no change required
2016-05-02 21:19	Dusk	Status	closed => resolved
2018-09-30 22:35	Blzut3	Status	resolved => closed

Relationships