18th July 2019, 9:28 AM
(This post was last modified: 18th July 2019, 12:28 PM by Zack6723. Edited 2 times in total.)
(18th July 2019, 3:46 AM)bls1999 Wrote: In theory, it's a good idea; however, this would require a script that looks through every individual level text file and makes the change if the time matches a certain value (999 secs).Alright, so since it's actually possible that a whopping handful of players want a 999 second time limit on their map..
I believe Jiggmin posted back in 2012 when he moved over to PR2hub from jiggmin2.com and said that all of the text files totaled about 80gb in size… just imagine the total now! That operation would take multiple days to finish, and would also have a high chance of causing some serious problems with screwed up level data. Further, if a level maker actually only intended for their level to have 999 seconds, we'd be bypassing that.
I wish I could help you on this, but I think it's probably more trouble than it's worth. :/
Is it possible to filter out maps by publish date? [assuming this data is worth storing]
because if it is, maps published after the update can simply be excluded, as they already had the option and chose not to use it.
This could even go a step beyond and check it against the map creators last active date, if they've been online after the update that allowed for unlimited time then we can assume they chose not to update their map for a reason
[this one is far fetched since some people came back for 5 mins and just vanished again and still don't know but eh.]
Since corruption would be a MAJOR concern and also assuming the above happens to be true, could one not simply take a test batch of say, 10,000 - 50,000 randomly selected levels?
(move these copies elsewhere and test a script against them until it has a 100% success rate?)
If this all goes well, you should almost certainly make a complete backup of every level file while also giving the players a notice not to make map updates/publishes for a period of time [estimate time to complete the process, up to 2 weeks(?)] unless they're fine with that being potentially rolled back.
Backing up 200gb~[Never did get the actual current size.] isn't the end of the world imo, we have fast internet and cheap bulk storage drives these days.
Then run the script on the actual servers. If something goes catastrophic, restore the backup and trash that idea.
End; I understand you've basically already said no, and for some very sound reasons. Gotta make a post tho ;p
