Bug is pretty straight-forward. With serverside loadstring disabled, the LoadString() from data persistance is also disabled. I’d like this to be fixed as soon as possible as I’m using data persistance and would like to have serverside loadstring disabled.
For now, I can enable loadstring because I don’t have any loadstring vulnerabilities. In the long run I’d like to keep loadstring disabled though, just in case exploiters somehow manage to get a vulnerability inserted.
I hate to be that guy, but why aren’t you using Data Store?
switching is hard, just saying
Oh, I know. I just switched stat saving in Multi Pong over from persistent data yesterday, but it was worth it; now I don’t need to worry about player stats being reset due to them losing connection to the game.
Oh, I know. I just switched stat saving in Multi Pong over from persistent data yesterday, but it was worth it; now I don’t need to worry about player stats being reset due to them losing connection to the game.[/quote]
I think regardless, it’s a built in ROBLOX feature that people are going to use, therefore it does need fixing.
DataStores have a hard data limit as far as I know, so it makes little sense to use them for per-player data if they’re going to just stop working if I get enough players. There’s been a thread about this topic recently.
Data persistance also has a limit, but it’s a limit for each player, rather than an overall limit.
Also, as woot3 said, it’s a built in feature and should work properly.
Please provide more details. I tried to reproduce it using this place:
And as far as I can tell it works.
Please provide more details. I tried to reproduce it using this place:
And as far as I can tell it works.[/quote]
It’s possibly filtering enabled, when I tried to call LoadString I came across this issue also.