Skip to content

1.5.9
Compare
Choose a tag to compare
@patrikjuvonen patrikjuvonen released this 01 Oct 16:17
· 1617 commits to master since this release
1.5.9
ea28712
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

After a year of feature development, bug fixing, and bug making; the MTA Team is delighted to announce the release of MTA San Andreas 1.5.9! 🎉

This update is loaded with new features for scripters to build even more immersive experiences with! Servers can now do the following (and much more):

  • allocate custom objects and vehicles
  • edit element bone behavior through 7 new bone functions
  • edit vehicle dummy positions per vehicle
  • use scalable vector graphics (SVG)
  • customize sound effects with effect parameters
  • new client download transfer box features
  • use peds and vehicles as the camera target
  • and much more!

There have also been many synchronization improvements, varying size fixes, quality of life improvements, updates and security enhancements.

Finally:

A big thank you to all that donated, contributed and tested MTA 1.5.9, without all of you, this release would not have been possible. ❤️

Please read our 1.5.9 release announcement for more information.

You will receive an automatic update soon, but if you don't have MTA installed, you can get it from our home page at https://mtasa.com/.

You can also find the latest binaries from nightly.mtasa.com and linux.mtasa.com.

Don't forget to update your server resources! Latest resources can be found from https://mirror.multitheftauto.com/mtasa/resources/.

// NOTE TO FORK DEVELOPERS (and users in general):
Do not pull this tag, it's just a time recording of an outdated "initial release" revision. Instead, we use an "MTA-as-a-service" model where we keep using a master revision as new main release, when our regular testing & QA deems it stable, and more often so when we also have security improvements to push. So what we call a certain major release (like 1.5.9 here) keeps getting lifted regularly, it usually happens 15 times per release number, but we don't announce it: the release in news post & changelog like here then becomes more of a "Heads up" for what MTA developers achieved, while most players already benefited from the changes in "MTA-as-a-service" model updates throughout the year and much quicker than our next major release version announcement. To see our current as-a-service main release revision, go to https://nightly.mtasa.com/ver and look for "Auto-update default", which moves along when it happens. So fork developers should always pull the mtasa-blue master commit that corresponds to the current revision listed in there. They can be matched up to commits by using https://buildinfo.mtasa.com/index.php

Assets 2
Loading