http://tmc.castleparadox.com/ohr/statusmenu.sliceguo wrote:Could you please upload the slice collection for the default status menu?
Import it into the slice collection editor by pressing F3. Note that it contains lots of special embed codes like ${HERONAME}, none of which will work outside of the builtin status menu, so you will have to replace all of them.
${...} embed codes do work in menu item captions. But by "captions for inventory items" I guess you mean descriptions of inventory items? I don't think they work in item descriptions.When I asked if you could plug ${#V} into menu items, I meant the items that constitute a menu, not the captions for inventory items. Doesn't seem to work unfortunately :(
Aside from menu item captions, which is already implemented, I nearly finished implementing support for embed codes in text slices, so that will be in Fufluns.It would be really nice if we could just display strings in menu items and slice text without having to run extra commands.
Yes, that's pretty natural, but it requires knowing which hero to grab the stat from. It can work inside the status menu because the status menu provides a "context". I'm working on something for this too.Even better would be an option to display a hero stat with a simple #{$nameofstat}. Mind you, I am fairly lazy.
So what you're asking for is, firstly, the ability to use of the name of the global variable in the embed code, rather than the ID number. Yes, that's something I want to allow too. I doubt that this would make it into Fufluns. And you also want hamsterspeak expressions in embed codes, rather than just variables. That's something I've considered too. But I would probably only allow that in strings you put in a script, not text slice contents, which is a lot more complexity because hspeak can't be used to parse those expressions in-game. I'll consider that a vote in favour of it, though.Is there a way to run operations on strings like #{$V} ?
For example, the text slice would read:
"Attack Old: #{$gv_attack} new: #{ ($gv_attack ++ 1) }"
Is this coming across clearly? It would save having to create so many globals for displaying things like old and new values of a stat.