[commander_name] etc. don't work when used in descriptions.plist, they are not expanded.
Is there a workaround for that? Or can they be made expandable also if used in descriptions.plist?
That would come in handy for randomized hails which contain the player's name, or ship name, etc.
using [commander_name] etc. in descriptions.plist
Moderators: winston, another_commander, Getafix
- Commander McLane
- ---- E L I T E ----
- Posts: 9520
- Joined: Thu Dec 14, 2006 9:08 am
- Location: a Hacker Outpost in a moderately remote area
- Contact:
- JensAyton
- Grand Admiral Emeritus
- Posts: 6657
- Joined: Sat Apr 02, 2005 2:43 pm
- Location: Sweden
- Contact:
Re: using [commander_name] etc. in descriptions.plist
This, as stated, is not true. However, descriptions.plist is used in at least a dozen ways. In what context are expansions not working?Commander McLane wrote:[commander_name] etc. don't work when used in descriptions.plist, they are not expanded.
E-mail: [email protected]
- Eric Walch
- Slightly Grand Rear Admiral
- Posts: 5536
- Joined: Sat Jun 16, 2007 3:48 pm
- Location: Netherlands
Re: using [commander_name] etc. in descriptions.plist
Coincidence or not, but I stumbled over this one hour ago. In the console:Ahruman wrote:This, as stated, is not true. However, descriptions.plist is used in at least a dozen ways. In what context are expansions not working?Commander McLane wrote:[commander_name] etc. don't work when used in descriptions.plist, they are not expanded.
Code: Select all
expandDescription("[commanders_name]")
Code: Select all
expandDescription("[who_is_there]")
Code: Select all
"My name is commanders_name"
UPS-Courier & DeepSpacePirates & others at the box and some older versions
- Commander McLane
- ---- E L I T E ----
- Posts: 9520
- Joined: Thu Dec 14, 2006 9:08 am
- Location: a Hacker Outpost in a moderately remote area
- Contact:
Fixed in trunk.
Looking at the code, it left all '[commander_xxx]' tokens unexpanded - 'intentionally' - in 'some' circumstances, like nested string expansion...
Mission variables do expand properly, for the moment you can use those instead.
Looking at the code, it left all '[commander_xxx]' tokens unexpanded - 'intentionally' - in 'some' circumstances, like nested string expansion...
Mission variables do expand properly, for the moment you can use those instead.
Hey, free OXPs: farsun v1.05 & tty v0.5! :0)
- Commander McLane
- ---- E L I T E ----
- Posts: 9520
- Joined: Thu Dec 14, 2006 9:08 am
- Location: a Hacker Outpost in a moderately remote area
- Contact: