X-Git-Url: https://jxself.org/git/?a=blobdiff_plain;f=tests%2Ffillvase.log;h=3192144a23fbf94889f5d1b8901148a4fca144eb;hb=7ddbe04632222914fd5d73ecde3f8ed3c7863d62;hp=ba6309e2d9b4df4e4dd62d7755e0a36ec3dfe1c5;hpb=92ddbba2120c614f073ad3ccbf4c5c83597dea12;p=open-adventure.git

diff --git a/tests/fillvase.log b/tests/fillvase.log
index ba6309e..3192144 100644
--- a/tests/fillvase.log
+++ b/tests/fillvase.log
@@ -1,4 +1,15 @@
 ## Fill the vase
+# Arthur O'Dwyer <arthur.j.odwyer@gmail.com> writes:
+#
+# (4) Lastly, here's a test case for you! Go get the VASE; then get the
+# PILLOW; then go back to the stream (any stream) and DROP PILLOW; then FILL
+# VASE. What should happen? This is a trick question, because literally every
+# historical version of Adventure has *some* bug here. They duplicate
+# messages (MCDO0551), or the vase shatters and then shows up re-formed but
+# immobile (WOOD0350, WOOD0430), or the vase shows up shattered but still in
+# your inventory (KNUT0350), or... So you get to pick your behavior! From the
+# code, I think you're faithfully emulating WOOD0430's bug.
+#
 n
 seed 1838473132
 in
@@ -243,3 +254,6 @@ fill vase
 carry vase
 read vase
 fill vase
+inven
+look
+take vase