Compatibility-breaking changes between 1.16 and 1.17/1.18

The place to post your WML questions and answers.

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.
User avatar
Ravana
Forum Moderator
Posts: 3012
Joined: January 29th, 2012, 12:49 am
Location: Estonia
Contact:

Re: Compatibility-breaking changes between 1.16 and 1.17/1.18

Post by Ravana »

.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
User avatar
octalot
General Code Maintainer
Posts: 786
Joined: July 17th, 2010, 7:40 pm
Location: Austria

Re: Compatibility-breaking changes between 1.16 and 1.17/1.18

Post by octalot »

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&).
User avatar
Ravana
Forum Moderator
Posts: 3012
Joined: January 29th, 2012, 12:49 am
Location: Estonia
Contact:

Re: Compatibility-breaking changes between 1.16 and 1.17/1.18

Post by Ravana »

So it is only visual difference not compatibility.
Post Reply