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
The Fortress of Fear
The Lost Children
Skybreak v 1.2
The PK Girl
The Euripides Enigma
Magnetic Moon
the virtual human
Lost Coastlines
Starship Quest
 
Latest Forum Posts
The Book of Jax - The Adventures of Alaric Blackmoon # 10
HAPPY BIRTHDAY DazaKiwi
HAPPY BIRTHDAY ralphmerridew
An' anuvver fing....
Why don't my folders stay where I put them?
Results of The 2023 IFDB Awards are in!
Setting nickname / displaying unique text based on character name
Some excellent loot
ADRIFT 5's rendering API?
Getting Adrift 4 to ignore "and"
 
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  Character Referencing from a Player property via params not working

Issue Type: Status: Priority: Date Submitted: Votes:
Bug No Longer Required Medium Fri 1st Apr 2016 1 vote Vote Up Vote Down
 
Found in version: Last Updated: Completed in version: Date Completed: Track Changes:
5.0.34.1 Fri 1st Apr 2016 Log In
 
DazaKiwiFri 1st Apr 2016 07:05
If you create a character property like CurrentTarget which will only list one character who could be the players current target or character reference.

And if you want to pass that character reference onto another task via params, currently when entering Player.Propertykey.Name it won't be recognized by the task which is expecting a referenced character.

The called task uses;
# %character% in the general, with character reference restrictions. This throws up an error "Sorry, I am not sure which character are referring to".

Passing on character references from a task that does not use a reference specifically is important for interlinked tasks which relies upon referencing such as a character. Being able to do so from a non-referenced task would be handy.

I hope this makes sense?


 
DazaKiwiFri 1st Apr 2016 11:28
Remove this bug report. I discovered Player.PropertyKey.Name needed to be Player.Propertykey without the .name on the end of it in order to be passed by a restriction. Sorry about jumping the gun on this.
© 2013 Campbell Wild. All rights reserved. | Contact the Webmaster