ZDoom

[quote="Blue Shadow"]Yes, the issue is with the HUD mod itself, not GZDoom (well, GZDoom is to be partially blamed for not erroring out, I'd say).
[/quote]

Well, I had my reasons to declare SBARINFO deprecated. There are just too many problems with its implementation that could never be fixed without breaking the thing, and this is obviously one of them.

Yes, the issue is with the HUD mod itself, not GZDoom (well, GZDoom is to be partially blamed for not erroring out, I'd say).

[quote="NightFright"]Well, I had hoped that the code I copied would be enough.[/quote]
The thing is, that piece of code doesn't show the problem, since it's almost a copy of the one in gzdoom.pk3, so the problem must lie elsewhere, which it does.

Well, I had hoped that the code I copied would be enough. I was about to link to the thread with the statusbar mod, but since it has already been done now, I don't need to do that again. Great that the reason for the issue has been found, though.

I will remove those extra brackets then and hopefully get this fixed for good (if it's really inside the mod and not the native GZD files). Thanks a lot for the assistance!

[quote="Graf Zahl"]And thanks for confirming that posting something to check made all the difference![/quote]
Echoing this.

Mainly because it's so annoying when someone asks for help but they just can't be convinced to help you help them.

Yeah, if I am even going to help anyone, and they provide such little information and detail, I rarely even ask for it nowadays, I just walk away.

You mean inside the mod? I'd never have expected that the parser cannot detect structural errors... :?

And thanks for confirming that posting something to check made all the difference!

Using the file from [url=https://forum.zdoom.org/viewtopic.php?p=1041814&sid=159618e1fd224cc62ed71cf7fa734e5d#p1041814]here[/url], which suffers from the problem, I was able to figure out what's wrong. In line 96 of [b]filter/game-heretic/sbarinfo.txt[/b] and line 216 of [b]filter/game-hexen/sbarinfo.txt[/b], there's an extra closing curly brace which seems to throw GZDoom off. Removing it fixes the problem.

Yes, me. FYI, this was my response:
[quote]
Please continue this discussion in the forum. You may need input by other users.
[/quote]

So the issue still stands:
If you want help, provide a minimal testable example. Those willing to help won't and often cannot do that themselves.

I believe this is the [url=https://forum.zdoom.org/viewtopic.php?p=1062575#p1062575]same thing NightFright PM'd you about a while ago[/url].

[quote="Nicholas Sizzleneck"]Nobody came up with a solution for this until now?[/quote]


How? There's nothing to test here which an interested person could download and check for themselves. Most people seeing a thread like this with some question will just walk away without saying a word because they'd have to construct the test case themselves.

In general, if you have a problem and need help, provide something that can be tested as-is. That very much increases the likelihood of constructive feedback.

Nobody came up with a solution for this until now? This info would surely be useful for more than one person, I believe...

statusbar inventoryfullscreen, fullscreenoffsets
{
	drawinventorybar Heretic, translucent, 7, INDEXFONT_RAVEN, -110+center, -75, -83+center, -53, untranslated;
}

I have modified statusbars for Heretic and Hexen via SBARINFO, but apparently there is a problem with fullscreen inventory bars: Any modification applied to those is not recognized by GZDoom.

My modified SBARINFO code looks like this, the ZDoom fullscreen inventory bar is supposed to be displayed above/on top of the statusbar:
[code]statusbar inventoryfullscreen, fullscreenoffsets
{
drawinventorybar Heretic, translucent, 7, INDEXFONT_RAVEN, -110+center, -75, -83+center, -53, untranslated;
}
[/code]
GZDoom does not recognize the changed coordinates, regardless what I enter there. How can it be done now in most recent GZDoom version (3.4.1) if it does not work via SBARINFO any longer?