Note that Magpie will not apply the patch above. If you need assistance patching your Cythera Data with a third-party patcher, send me an email or look for me on #cythera.
Current bug being fixed:
Bug 8: Edible strange device on dividing food (pending replication); Food Dividing Oddities (mushroom steaks &c.)
Fixing queue:
Runic magic.
Fixed so Far:
1. Fetch,
2. Fishing,
3. Aethon not responding to "Ask About..."
4. Aethon not picking locks
5. Darius and Sardis trying to sit in the same chair in the Green Goat
6. Paris' name not being remembered
7. Diomede name not being remembered.
Log of Fixed Bugs:
Quote
Using the spell "Fetch" on an item will only make the item disappear,
it will not appear in the player's inventory. [BWM]
As a further elaboration on this bug report, many sorts of objects that should not really be fetchable can be targeted, e.g. cities and doors.
Fix: I've corrected both problems in the patch. It now gives an appropriate message when trying to fetch something inappropriate like a wall torch or a town. If you find anything that you aren't able to pick up normally that is nonetheless fetchable, please let me know. Also, fetching things is never considered stealing, which might be considered a bug.
As of patch version 0.2, the situation of fetching an item too heavy for your inventory is handled correctly, and the PutInside method of an object is called when it is fetched into the inventory, so e.g. lamps are extinguished when fetched.
Source code of this fix
Resources affected: 1A28 (Fetch Spell)
Quote
There is no deep water in the game, making it impossible to fish. [BWM]
The fishing pole UseAt method now properly detects deep water (defined
as non-shore water on the overworld map in the original code; I do not
know why it you can't fish in towns given that there are many cases of
NPCs fishing in town, but that does seem to be the intended behavior so
I haven't changed it.) Note that fishing is not always successful.
Resources affected: 1091 (Fishing Pole)
Source code of this fix
Quote
Aethon does not respond to his "Asked About..." action.
Now he does. The code for it was simply absent. Many items have an "informed response" coded for him, though, so this doesn't seem to be intentional (and having "Ask About..." but not having it do anything would be a bug in any case.)
Resources affected: 1861 (Aethon)
Quote
Aethon does not pick locks when you tell him to. He says "Work the Lock!"
but he... doesn't actually do anything to the lock.
It appears that AddTask is supposed to be able to add a task consisting of the character using one item on another, but it doesn't work, at least as applied in this case. Perhaps it will be possible to fix it someday after AddTask is better understood. In the mean time, RPGUtil.PickLock is called directly by the skill 1AD5 when its .UseOn method is invoked (note that the player can't use Lock Picking directly, they have to use a lock pick in their inventory, so this only affects how NPCs pick locks.) To keep the lock from being unlocked instantaneously, we have a brief cutscene where Aethon walks over to the lock and says "Work the Lock!".
Resources affected: 1AD5 (Lock Picking), 1861 (Aethon)
Quote
Darius and Sardis try to occupy the same chair at the Green Goat
(ignoring the three empty chairs at that table), from 5pm through 9pm.
[BWM]
Darius now occupies the north chair at the table instead. This was a simple change of coordinates in his schedule entry.
Resources affected: F00B (Schedules Data)
Quote
Paris is always labelled as "man" instead of his name, even after learning
it. [BWM]
Fix:
Added the code to set the character bit on learning his name; it seems
to have inadvertantly been left out.
Resources affected: 1857 (Paris)
Quote
Diomede is always labelled as "woman" instead of her name, even after
learning it. [BWM]
Fix:
Added the code to set the character bit on learning her name; it seems
to have inadvertently been left out.
Resources affected: 182E (Diomede)
Not fixing at this time:
Quote
Reason: Difficulty reproducing the bug completely (it didn't fill with wine like it presumably ought to, but neither did it give an incorrect message.)
This post has been edited by BryceSchroeder: 09 March 2016 - 06:21 PM