|
|
 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
 |
| |
| 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.
|
| |
| Campbell | | Wed 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! |
|
