Page MenuHomeFeedback Tracker

Scripts from previous mission still running when joining new server.
Assigned, WishlistPublic

Description

There appears to be an issue, that is most likely causing a lot of false bans. If I join a server, play for a bit and then I go join a different server, I <can> get kicked for a script restriction from a script running from the last server. (That may be hard to understand but the steps to reproduce will make it easier)

Details

Legacy ID
3342475578
Severity
None
Resolution
Open
Reproducibility
Always
Category
Scripting
Steps To Reproduce

1.) Join any server (I used Sa-Matra Stratis in my testing)
2.) Load fully into the game until your character spawns.
3.) Join any other server and you will still have scripts running from previous server.

Additional Information

To test this, after I left the Sa-Matra server, I joined a local server that I had set up to do this test with the scripts.txt file just log everything (1 ""). The very first script I ran was:

"private["_0xk","_0em"];disableSerialization;_0xk=uiNamespace getVariable "Wasteland_IconsHUD";wg5wzh=0;wgswhm=0;_0em=call wgb79v"

Which is code from the Sa-Matra server that I was just on and the server that I Was joining was a test server for Altis-Life which does not contain that code.

This causes people to get kicked/banned for script restrictions on our servers because we have a lot of values in our files to lock them down. We are just now discovering this issue.

Event Timeline

Paronity edited Additional Information. (Show Details)
Paronity set Category to Scripting.
Paronity set Reproducibility to Always.
Paronity set Severity to None.
Paronity set Resolution to Open.
Paronity set Legacy ID to 3342475578.May 8 2016, 12:30 PM
Paronity edited a custom field.