[Bug] Comments are not ignored in .cfg files

[Jarrrk]

Summary

Comments within server config files (i.e server.cfg - #sv_master1 "") will be read by the server and should be ignored.

To note, this is with comments that have leading spaces:

#sv_master1 "" # is ignored fine
    #sv_master1 "" # is not ignored

Likely not that big of an issue, worth noting this wasn't an problem in legacy.

Issue type

Server

Repro rate

Always

Server build version

b90

OS

No response

CPU

No response

GPU

No response

RAM

No response

Storage type

None

Connection type

None

ISP and bandwidth

No response

DxDiag

No response

Network graph

No response

Platform

None

OS version / distribution

No response

CPU

No response

RAM

No response

Using txAdmin?

None

Hosting provider

None

Machine type

None

/perf endpoint output

No response

DDoS protection

No response

ulimit -n value (Linux only)

No response

Docker Compose file (Docker only)

No response

Steps to Reproduce

1. Start server with comments in server.cfg file
2. example: #sv_master1 ""
3. Line printed in console Error while executing a command from the config, Line: #sv_master1 "", Error: Command name not found ( #sv_master1 "")

Expected Behavior

Don't read comments as options in .cfg files

Actual Behavior

Spamming server console of useless info

Evidence

No response

Additional Context

No response

[Valdarix]

Not sure this an issue with enhanced. It happens in Legacy too when using certain punctuation in the cfg files.

[wolfram-cfx]

Thanks, we are looking into this.

[i20h]

Strings containing a # also pose a problem, even when they're enclosed in "". In my case, it's in my SQL connection string

[Gogsi]

A fix for this bug has been implemented and is available in Hotfix 5. Please try again and let us know if the issue persists. Thanks for your help!