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
The Heritage
Bug Hunt On Menelaus
All Hallows Eve
Finn's Big Adventure
Xanix - Xixon Resurgence
Goldilocks is a FOX!
The Euripides Enigma
Wes Garden’s Halting Nightmare
Land of the Mountain King
Ectocomp 2011 Compilation
 
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
Goldilocks is a FOX!
Xanix - Xixon Resurgence
Finn's Big Adventure
Bug Hunt On Menelaus
Magor Investigates...
Classic Adventure
Private Eye
Roozden's Color Code Module
Wumpus Hunt
Lost Coastlines

Make a donation

Cursor  Item reference is missing many restrictions and actions

Issue Type: Status: Priority: Date Submitted: Votes:
Enhancement More Info Required Medium Mon 6th Oct 2014 2 votes Vote Up Vote Down
 
Found in version: Last Updated: Completed in version: Date Completed: Track Changes:
5.0.32.1 Fri 28th Nov 2014 Log In
 
saabieMon 6th Oct 2014 07:07
If I make a general task with an %item% reference I can then make separate specific tasks for characters and objects using the restriction: Referenced item must be type Character.

But many character restrictions such as:
[Referenced item] [must be] [holding any object]
are not available, which severely limits what the task can do, and also limits the alternate descriptions that can be applied to the text box.
There also do not seem to be any usable actions for items.

Workaround: Make another 3 tasks that uses a character/object/location reference and execute them from the specific task, passing %item% as the parameter.
Each specific task needs a restriction to check the item type.
[Referenced item] [must be] [item type] [character/object/location]
 
CampbellFri 28th Nov 2014 01:48
Hmm, this was deliberate, to try to reduce the number of people trying to do things like go inside characters or carry locations. Do you think I should just add all the options?
 
saabieFri 28th Nov 2014 04:59
Yes, if somebody uses an item reference then it is up to them to put in appropriate restrictions to ensure the task makes sense.
As it is at the moment it is virtually unusable because the only way to do anything useful with the item is to create 3 extra general tasks (one each for objects, characters and locations) and execute them from the item task.
It would be less work to use those for the parser and not create an item task at all.
If we could use any restriction/action with items then a single task could respond appropriately for a certain item type, while still giving customised restriction messages if they try to use that verb on one of the other item types.

The only other option would be to add "any character", "any object" and "any location" to the drop-down list on the %item% reference in the overriding specific task.
If "any character" is selected then the %item% reference would change to a %character% reference inside of that task.
Adding these specific tasks is very quick and easy compared to executing general tasks from actions and passing parameters to them.
© 2013 Campbell Wild. All rights reserved. | Contact the Webmaster