Page MenuHomeFeedback Tracker

worldname returns different depending on which DS exe you are using
Acknowledged, WishlistPublic

Description

If you run your mission from the Steam tools dedicated server executable, worldname returns, for Altis, "altis" <--- note case.

But if you run your mission from a client install running as a DS, world name for the same island returns "Altis"

Details

Legacy ID
834160327
Severity
None
Resolution
Open
Reproducibility
Always
Category
Dedicated Server
Steps To Reproduce

http://puu.sh/hgtFQ/13e5e49df5.png
This is the steam tools exe that I'm on about, one near the bottom of the screenshot. Using this will make worldnames return in all lower case.

Additional Information

Tried with and without addons. At first, we thought CBA was to blame, but we quickly cleared that. The above issues were confirmed with a vanilla game.

Event Timeline

Tankbuster edited Additional Information. (Show Details)
Tankbuster set Category to Dedicated Server.
Tankbuster set Reproducibility to Always.
Tankbuster set Severity to None.
Tankbuster set Resolution to Open.
Tankbuster set Legacy ID to 834160327.May 8 2016, 11:57 AM

Like we discussed, a test on a config entry shouldn't be case sensitive, using toLower should be enough to bypass this issue.

Tom, I want to thank you for taking the time to contact me personally about this. That's very much appreciated.

Like we discussed, that's a good workaround and I had already put code in place to unbreak this, but it's for an issue that shouldn't have arisen in the first place.

It's not just about gettext config entries. The worldName command returns data with these inconsistencies too.

There's no reason for this to be like this, other than an oversight. And it's extremely hard to track down. Running identical missions on 2 different servers, one worked, one was busted - and the operators of both servers just happened to have been discussing the existence of the steam tools DS exe.

If that random conversation hadn't happened before hunting this bug down, we might never have arrived at this issue report and would still have a broken mission.