Create your own Interactive Fiction

ADRIFT - Interactive Fiction  
Home   |   News ADRIFT News RSS   |   Screenshots   |   Download   |   Games ADRIFT Reviews RSS   |   Forum   |   Help   |   Links
Welcome Guest Register | Login
Popular Games
Skybreak v. 1.4
Skybreak v 1.2
The Fortress of Fear
Lost Coastlines
the virtual human
Classic Adventure
Starship Quest
The Dwarf of Direwood Forest
The Lost Labyrinth of Lazaitch
The Last Expedition
 
Latest Forum Posts
Preventing character property being executed?
ParserComp 2024 site is up
HAPPY BIRTDAY RoozdenScoot!
Copyright limitations?
Search Function Not Working In Windows 11
errors
Forum site error
The Book of Jax - The Adventures of Alaric Blackmoon # 10
HAPPY BIRTHDAY DazaKiwi
HAPPY BIRTHDAY ralphmerridew
 
Latest Reviews
Classic Adventure
Private Eye
Roozden's Color Code Module
Wumpus Hunt
Lost Coastlines
The Lost Labyrinth of Lazaitch
October 31st (Post comp.)
The Euripides Enigma
AI
Hint System Library - Release 1

Make a donation

Cursor  %objects% followed by optional word, e.g. {down} causes problems

Issue Type: Status: Priority: Date Submitted: Votes:
Bug New Low Mon 24th Feb 2020 2 votes Vote Up Vote Down
 
Found in version: Last Updated: Completed in version: Date Completed: Track Changes:
5.0.35.3 Mon 24th Feb 2020 Log In
 
DenkMon 24th Feb 2020 09:19
This bug is best described with an example.

In the library task "Drop Objects" the command field is by default:
[drop/put down] %objects%
put %objects% down

Now change the command field to:
[drop/put/put down] %objects% {down}

In both cases, if you type DROP BASKET then ADRIFT says:
Ok, you put down the basket.

But in the latter case, if you type Look or Inventory you will see that the player is still holding the basket!

The problem is described more in this thread:
http://forum.adrift.co/viewtopic.php?f=14&p=107501#p107501

NB: IT MAY BE DANGEROUS TO FIX THIS AS IT MAY CAUSE EXISTING GAMES TO MISBEHAVE.
© 2013 Campbell Wild. All rights reserved. | Contact the Webmaster