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
Pete's Punkin Junkinator
Museum Heist
All Through the Night
The Day Program
Trick or Treat
Three Monkeys One Cage
Finn's Big Adventure
The Fortress of Fear
Skybreak v. 1.4
Jacaranda Jim
 
Latest Forum Posts
5.0.36 out now
Need help! : Installing Adrift on a new computer
ADRIFT 5 SETUP
Getting Adrift 4 to ignore "and"
Happy birthday, Rotter
CYS New Year's Prompt contest
Short story contest for the forum?
Text Adventure Literacy Jam 2026
Merry Christmas!
Constellaris Court
 
Latest Reviews
DRAM 321 Final
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

Make a donation

Cursor  When using a restriction with only a textoverride as output, the parser doesn't give output

Issue Type: Status: Priority: Date Submitted: Votes:
Bug Open Low Wed 1st May 2013 1 vote Vote Up Vote Down
 
Found in version: Last Updated: Completed in version: Date Completed: Track Changes:
5.0.30.1 Wed 1st May 2013 Log In
 
Wed 1st May 2013 12:01
When using a task with a restriction, and only using a textoverride for the output of the restriction, the parser gives this: "Task does not pass and also has no output, therefore will continue to execute lower priority tasks". In-game, you get: "Sorry, I didn't understand that command." instead of the textoverride which should be shown.

When you add a space or any other character after the textoverride in the restriction output box, the restriction will parse correctly.

Example:

I used <TOOEARLY> as a text override with "It is too early for that" as the text to be shown.

When using literally, only

"<TOOEARLY>"

(without typing the two "'s!) as the output the text override is not displayed.

"<TOOEARLY> "

(without typing the two "'s!) works however.

 
campbellWed 1st May 2013 12:07
This will be because <TOOEARLY> normally wouldn't output to screen, so it is not deemed to have output. If you change your replacement to use TOOEARLY instead of <TOOEARLY> then it should work.

I will still look to fix this however.
 
Wed 1st May 2013 14:35
Thanks!
© 2013 Campbell Wild. All rights reserved. | Contact the Webmaster