Dedicated servers don't seem to load profile namespace variables even though they properly save them into <profile>.vars.Arma3Profile file. {F22200}
Description
Details
- Legacy ID
- 1269592235
- Severity
- None
- Resolution
- Fixed
- Reproducibility
- Always
- Category
- Server
- Start profileNamespace_dedi_repro.Altis on dedicated server
- Join and start the mission
- Look into server RPT and look for following lines:
profileNamespace getVariable "test" = <null>
profileNamespace getVariable "test" = *RANDOMSTRING*
It supposed to save this random string as "test" variable into profile namespace
- Restart dedicated server, join and start mission again.
- Look into RPT once more, you will see that
profileNamespace getVariable "test" = <null>
test variable is null again even though value is properly saved in vars.Arma3Profile on dedicated server.
If you repeat same test on non-dedicated server it will work fine.
Event Timeline
"seems like we need loadProfileNamespace command"
Thats not the problem. The problem is that the profile is being overwritten once the dedicated server starts.
Could someone please retest this? I've done some changes to loading profile on dedicated server so it is possible that it will fix this.
It should be in latest DEV 1.17.116429
WOW! Are you a wizard, Nesquick? It works!
profileNamespace setVariable ["test", "fuck yeah"];
saveprofilenamespace;
on server restart
profileNamespace getVariable ["test", ""]; //fuck yeah
Very nice!! I would like to test this, too. Sorry for the noob question, but where can I download dev version 1.17.116429 of the server for linux?
To metafa:
No we don't have any dev version of linux dedicated server. It will be too much steam branches.
Thanks for the info Nesquick!
Any indication when this will be on stable? days, weeks, months? Thanks a lot!
Thank you for the fix Nesquick. If the fix was fairly simple i will LOVE if you could port the fix over to ArmA 2 which still has this bug. Thank you.
Mass closing tickets marked as resolved more than 1 month ago.
If the issue is in fact not resolved, please create a new ticket referencing this one and ask for it to be re-opened.