[1.7] aclrequest ACL changes are lost when shutting down server

[ArranTuna]

Describe the bug

I noticed that my 1.7 server keeps telling me do aclrequest on runcode despite already doing it. Works fine in newest 1.6 though. @MohabCodeX do you think the aclrequest change you made could be the cause? Wow that was a weird coincidence, I just got an email that you've changed your ACL change while typing this up, so maybe you just fixed this report seconds before I posted it.

Steps to reproduce

Newest 1.7 nightly server
Have a resource that needs a permission giving
Do: aclrequest allow runcode all
See it says it has changed to allow and you can see in ACL.xml it did it:

<acl name="autoACL_runcode">
        <right name="function.loadstring" access="true" who="Console" pending="false" date="2025-09-21 21:54:26"></right>
    </acl>

shutdown
Look at ACL.xml again after the shutdown and the runcode section has disappeared.

Version

[mtasa-1.7-untested-25596

Additional context

No response

Relevant log output

Security Policy

• I have read and understood the Security Policy and this issue is not security related.

[MohabCodeX]

I’ve started to feel like I’m acting like a robot, but anyway, yes, I made some changes to simplify the logic. I hope this fixes the issue

[ArranTuna]

I've tested the PR and yes it fixes this bug.