I found several bugs with Magic Mirrors reflecting sword beams in my test quest: http://www.freewebs.com/masterpikachu/ZC%20Content/Incomplete%20Quests/LOZ%2DGeneration4.qst
In these first 4 images, Link shoots the sword beam downward toward the north side of the mirror, but, when it goes left or right, the sword beam sprite is flipped backwards.
Here, he shoots it upwards toward the mirror while standing on the top half of the tile below it, but the sword beam appears one tile above the mirror.
In these last 2 images, Link is standing to the right of the walkable mirror, but he is partially on the right half of it, and the sword beams appears one tile to the left of the mirror.
Sword Beam/Magic Mirror Interaction
To clarify: Wand magic doesn't have the first problem?
_L_ wrote:To clarify: Wand magic doesn't have the first problem?
For your information, wand magic does not have any of these three problems! It's just the sword beams. 🙄
Bugs are still present in Build 788.
Meh don't you read 788 WAS JUST ONLY A UPDATED VERSION OF ZCL? Learn to read please. -_-;;
so all these are to do with ZCL?* Commands: the '(None)' command is now equivalent to the 'Select Command' command. Click it to select a command.
* Favorites: Clicking a Favorites spot that contains no combo will place the currently selected combo - in that case, you need not hold Shift.
* 'Show Squares' - shows the locations of blue Warp Returns, green Warp Arrivals, and yellow Stairs with a square outline. If you use the Tile Warp dialog's Go button, the matching Warp Return flashes white on the destination screen. Oooh. ( _L_, 2008-04-29 03:41:25 )
* Fixed the bug involving entering water while charging the sword, with flippers.
* Fixed the bug that prevents the third and subsequent split Gels from moving.
* A new option in the Tools menu: 'Show Script Names'. The names of the FFC scripts that will run on a screen are shown in the upper-left corner. ( _L_, 2008-04-27 17:38:36 )
* Renamed 'Auto Warp' to 'Auto Side Warp' and 'Sensitive Warp' to 'Auto Tile Warp'.
* Added a few more Integrity Checks for Screens and Warps.
* A new Quest Report: Combo Locations. It tells you which screens and FFCs use the currently selected combo. That'll be useful. ( _L_, 2008-04-25 04:22:26 )
* To make the Quest Reports easier to fathom, screen numbers are now preceded by the name of the default palette of the screen. Now those numbers aren't quite so cold and nameless.
* The 'Item Locations' Quest Report now notes if the 'Enemies->Item' flag is present, and if an enemy is carrying the item. Just a little extra detail.
* One of the Integrity Checks has been given its own Report to itself. Now called 'What Links Here', it lists all screens containing tile or side warps to the current screen.
* A new Quest Report: 'Script Locations'. A complete list of locations where FFC scripts are instantiated in the quest! Groovy. ( _L_, 2008-04-22 09:48:14 )
* Fixed some false positives with the tile warp destinations Integrity Check.
* Enabled the 'Screens' and 'Warps' Integrity Check menu options.
* Fixed the bug where the Item Override subscreen option wasn't properly acknowledged by the weapon sparkles code. ( _L_, 2008-04-20 08:57:32 )
* Fixed the bug where it took too long for Link to exit water with classic movement. ( _L_, 2008-04-19 09:02:19 )
* Now, the SetComboD() and related ZScript functions can be used to alter combos on screens that are also being used as active layers! Though, you do have to know where those screens are located...
* Fixed the bug that suppressed the Quick Sword rule. ( _L_, 2008-04-15 07:25:39 )
And these bugs are still happening in Build 796.:thumbsdn:
There's been no reply in 3 days... Now I'm starting to lose my patience!😡
Confirmed.
Still happens in Build 798.
And these damn bugs still happen in 809!:thumbsdn:
The reason I haven't fixed this is because I'm mystified by it. The sword beams and the wand magic use the same mirror reflection code, but apparantly one works and the other doesn't.
Also I tend to give greater priority to mechanical bugs than a/v bugs.
Okay, now it is fixed.