new feature suggestion
LOCK (GOOD) SFV, like in projectzs for gl:
- user uploads sfv
- ioB does a few little checks to see if the sfv is correct
- if sfv is correct ioB 'locks' it (chmod)
- if sfv is incorrect (weird file names and such) -> rename to .bad
- when user tries to overwrite/resume sfv: tell him sfv is locked and good sfv has already been uploaded
this will fix a well known problem on io:
when you fxp sfv files from a linux env (gl) to io (windows) sfv files are sometimes RESUMED causing ****ups (this is cuz linux/windows use diff method to handle txt)
|