Compatibility-breaking changes between 1.16 and 1.17/1.18
Moderator: Forum Moderators
Forum rules
- Please use [code] BBCode tags in your posts for embedding WML snippets.
- To keep your code readable so that others can easily help you, make sure to indent it following our conventions.
Re: Compatibility-breaking changes between 1.16 and 1.17/1.18
.png is not redirected either, so if using same way it wont be compatibility breaking.
$ filesystem.have_asset("images","maps/titlescreen.png")
false
$ filesystem.have_asset("images","maps/titlescreen.webp")
true
$ filesystem.have_asset("images","maps/titlescreen.png")
false
$ filesystem.have_asset("images","maps/titlescreen.webp")
true
Re: Compatibility-breaking changes between 1.16 and 1.17/1.18
Although it isn't redirected for have_asset, .png is redirected when it gets to src/picture.cpp's load_image_file(const image::locator&).
Re: Compatibility-breaking changes between 1.16 and 1.17/1.18
So it is only visual difference not compatibility.