MTA 1.5.3 and fileOpen

[Bonsai]

Hey,

with MTA 1.5.3, the fileOpen function got a new "readOnly" argument.

The default value is "false", as it always was.

But for some reason, something is different now.

I have a script that worked fine for month, but now it throws an error when opening a file that has been in use before.

I noticed this on an mp3 file that is played by playSound, and later destroyed again.

If I set the "readOnly" argument to "true", it works as it used to, except that I cannot modify the files anymore. (Which in this case I don't need)

Nothing in my script changed except clients were updated to 1.5.3.

 

Is this possibly a bug?

 

Bonsai

[ViRuZGamiing]

Is the file changed to a read-only file perhaps by selecting readonly as true?

[Bonsai]

18 hours ago, ViRuZGamiing said:

Is the file changed to a read-only file perhaps by selecting readonly as true?

Ehm, whatever it does, the default behavior with readOnly as false causes this problem now which was not happening before the update.

[MIKI785]

Well if you're sure about that then report it on the bugtracker. If you didn't change the script in any way then the behavior should still be the same, so i guess it's a bug on MTA's side.