Not sure if this has been fixed yet, as I'm currently still on 798.
In Freedom's SwanSong, the sprite for the sword, only the master sword, is basically rotated 90 degrees. The same goes with the beam it shoots at full health- sideways it shoots a sword pointing up, and vertically the beam is invisible.
These are shots of beams while standing and shooting vertical- as you can see, the beam is invisible.
This is a picture of standing sideways and shooting
Again, not sure if this has been fixed as I haven't upgraded betas yet, and again, this ONLY happens with the master sword.
Well, attached is page 0 of SwanSong's tilesheets. The white square is the tile used by the "Sword 4 (Master)" weapon sprite. It doesn't look right to me.
So the bug seems to be that the Master Sword's weapon sprite and its item sprite have had their tiles mismatched by 2 ... or the tilesheet itself has been meddled with, somehow, causing those two tiles and those two tiles to swap places. But that is, of course, [strike]impossible[/strike] improbable.
I don't believe this bug was present when the quest was released _L_ but I'll check in to it for you and post an update here.
SwanSong was built in the 192b183
The bug was not present then.
It's also displayed wrong in his inventory, see his shot.
note my shots played in the 183;
Thank you. But the important question is: what should tile page 0 look like?
Wait a minute...
Tile page 0??
My goodness!
* Changed the way tiles 130 - 134 are handled in old quests. Old quests using these tiles only as tiles for the Goriya enemy, the Goriya guy, or in non-animating combos should work correctly. ( DarkDragon, 2008-02-20 00:48:32 )
Of course!
...But... how do I make that above-quoted fix not apply for this quest?
Make a quest rule that is automatically checked for old quests?
_L_ wrote:Thank you. But the important question is: what should tile page 0 look like?Wait a minute...
Tile page 0??
My goodness!
Of course!
...But... how do I make that above-quoted fix not apply for this quest?
This quest was done with Plith's descendant tileset and that's how it was set up, so I imagine there are probably quite a few others out there that will react this way.
Wasn't there something about "treat as 2.10 quest" or some such thing, meaning if it can't be made to work now maybe loaded as a 2.10.....
Confusing I know.
Freedom wrote:This quest was done with Plith's descendant tileset and that's how it was set up, so I imagine there are probably quite a few others out there that will react this way.
Wasn't there something about "treat as 2.10 quest" or some such thing, meaning if it can't be made to work now maybe loaded as a 2.10.....
Confusing I know.
There is a quest rule of this nature which is set on all 2.10 quests, the "old style Warp Detection." I think what would be better is if ALL elements of 2.10 quests that can't be quite migrated to 2.5 automatically fall under a single quest rule.
Solution: the Goriya tile reordering is no longer applied if the "New Enemy Tiles" rule is already set. That should sort this out, right?
wont that affect every single build prior to the one that fix is featured in? If you don't care about backwards support for earlier alpha's then go for it!
franpa wrote:wont that affect every single build prior to the one that fix is featured in?
No.
To be precise: the Goriya tiles will be reordered IF:
* The quest was made prior to 2.11 beta 7, AND
* The quest does not have the New Enemy Tiles rule set.
* But if it does, the tiles for the Goriya guy will be reassigned to compensate.