False hostname_rework notice when sv_projectName and sv_projectDesc are correctly set (Windows artifacts b31623 and b31689)

FiveM Discussion Bug Reports
1

Environment

  • Operating System: Windows

  • Previous artifact (working): b30819

  • Current artifacts tested: b31623 and b31689

Description

After updating from Windows artifact b30819 to b31623, the server started printing the following notice during startup:

[ citizen-server-impl] -- [server notice: hostname_rework]
[ citizen-server-impl] You don't have sv_projectName/sv_projectDesc set.
[ citizen-server-impl] These variables augment sv_hostname and fix your server name being cut off in the server list.
[ citizen-server-impl] Use `sets sv_projectName ..` and `sets sv_projectDesc ..` to set them.

The same notice is also present on artifact b31689.

However, both variables are already configured in server.cfg:

sv_hostname "MyServer Test"
sets sv_projectName "MyServer Test"
sets sv_projectDesc "Test Server - Closed for now"

After startup, running cmdlist confirms that both ConVars are correctly registered:

sv_projectName = MyServer Test
sv_projectDesc = Test Server - Closed for now

The exact same server.cfg was used on all tested artifacts.

Expected behavior

No hostname_rework notice should be printed when sv_projectName and sv_projectDesc are already configured.

Actual behavior

The hostname_rework notice is printed during startup even though both ConVars are correctly configured and available after initialization.

Steps to reproduce

  1. Start a server using Windows artifact b31623 or b31689.

  2. Configure the following in server.cfg:

sv_hostname "MyServer Test"
sets sv_projectName "MyServer Test"
sets sv_projectDesc "Test Server - Closed for now"

  1. Start the server normally (FXServer.exe, which launches txAdmin).

  2. Observe the hostname_rework notice during startup.

  3. Run cmdlist.

  4. Verify that:

    sv_projectName = MyServer Test
sv_projectDesc = Test Server - Closed for now

Regression

  • Windows b30819: :white_check_mark: No warning.

  • Windows b31623: :cross_mark: Warning is printed.

  • Windows b31689: :cross_mark: Warning is still printed.

The only change between the working and non-working tests is the FXServer artifact version. This appears to be a regression or a false-positive check introduced after b30819.

2

This is known, just not a high priority.

3

Thanks for the clarification.

I only reported it because I couldn’t find any previous references or reports about this issue on the forum, and I wanted to make sure it was already known.

Thanks for confirming and for the information.

4

It’s all good. Most things are not reported via the forums anymore.

Only happening with newer artifacts and doesn’t actually affect anything.

5

Appreciate you making this post. Same issue here.