Changes in 1.6
Jump to navigation
Jump to search
MTA:SA Releases | Changelog Pages |
---|---|
1.0 | 1.0.0 • 1.0.1 • 1.0.2 • 1.0.3 • 1.0.4 |
1.1 | 1.1.0 • 1.1.1 |
1.2 | 1.2.0 |
1.3 | 1.3.0 • 1.3.1 • 1.3.2 • 1.3.3 • 1.3.4 • 1.3.5 |
1.4 | 1.4.0 • 1.4.1 |
1.5 | 1.5.0 • 1.5.1 • 1.5.2 • 1.5.3 • 1.5.4 • 1.5.5 • 1.5.6 • 1.5.7 • 1.5.8 • 1.5.9 |
1.6 | 1.6.0 • 1.6.1 |
- GitHub commit log: https://github.com/multitheftauto/mtasa-blue/compare/1.5.9...master
- GitHub milestone: https://github.com/multitheftauto/mtasa-blue/milestone/9
- Resources GitHub commit log: https://github.com/multitheftauto/mtasa-resources/compare/1.5.9...master
- Release announcement on forums: TBA
This changelog is partial and needs updating. It is updated progressively to keep the page always up to date. To be documented: https://github.com/multitheftauto/mtasa-blue/compare/1.5.9...master
5 Backwards Incompatible Changes
Click to collapse [-]
These changes will take effect in this version:
- callRemote callbacks currently set the error code to nil when there is no error. In this version, to be consistent with fetchRemote, the error code reported will be 0.
See GitHub issue #294. - Since July 2016 if you provide an invalid string like "randomstring" when a function expects a number, the string will be treated as 0 and raise a script warning. This will be now an error. You will still be able to provide strings containing numbers (e.g. "100" and "12.34"), this change only affects invalid strings.
See GitHub issue #1043. - When providing a width and height of (0, 0) to createBrowser or guiCreateBrowser you will encounter a script error instead of a warning, introduced in February 2019.
See GitHub issue #1069. - Some functions expect only unsigned integers (positive numbers), and since January 2016 providing negative numbers would be a warning. This will now be an error.
See GitHub issue #1070. - Since August 2015, we replaced the custom mtalocal:// URL scheme with http://mta/resourceName/blah.html. This mtalocal:// URL scheme will now be removed.
See GitHub issue #1071.
- callRemote callbacks currently set the error code to nil when there is no error. In this version, to be consistent with fetchRemote, the error code reported will be 0.
Extra information
More detailed information available on our GitHub repositories: