Pixel Crushers Forum

I think the issue is due to the way LuaInterpreter implements tables. If it's a one-dimensional array, it uses a List<LuaValue>. If it's a hash, it uses Dictionary<LuaValue,LuaValue>. It may be easier to access LuaInterpreter's LuaTable directly through the LuaTableWrapper.luaTable field. LuaTable.L...

The Count property isn't required to use foreach. The Dialogue System only uses hashes, so LuaTableWrapper was originally designed only for hashes: blah = { a=55, b=66, c=12 }; print(blah[a]) In version 1.3.9, which will be available tomorrow, it also supports regular, one-dimensional arrays: blah =...

I tested NLua with Unity 4.3.4f1 and 5.0b13, and it seems to work fine in both versions. Could you please provide details to reproduce the problem? Regarding LuaTableWrapper, for the upcoming v1.3.9 I improved the API documentation for LuaTableWrapper and added a Count property. You'll be able to wo...

Hi,



What version of Unity are you using? (Version number and Pro/Free please)



I'll post some examples for LuaTableWrapper (link is to the API reference). I'll also include an accurate Count property in the upcoming v1.3.9.

This passthrough issue will be resolved in v1.3.9. It will behave like Chat Mapper.

Add an Actor Name Override component to the NPC. The behavior you described is by design. It lets you write generic conversations, such as a general-purpose shopkeeper conversation, that you can assign to any number of NPCs. When an NPC uses the conversation, it will use the NPC's GameObject name ra...

It looks like Zina's "IsPlayer" field is set True (marking her as a PC, not an NPC), since her dialogue nodes are blue. Go to the Actors tab, expand Zina's Fields foldout, and make sure IsPlayer is False. If you want Zina's lines and Zina's Dad's lines to be onscreen at the same time, that...

I'm glad it's working now. I know I've said this before, but your game is looking good!

Are you by any chance using the new Unity UI with the support package that came in Dialogue System v1.3.7? There was a bug in this support package that wouldn't hide the interaction message when a targeted GameObject was destroyed. It's fixed in v1.3.8. However, please be aware that v1.3.8 uses an o...

(The information below will be in the next documentation update.)   The START node has some unique properties:   1. If the Sequence field is blank, it defaults to "None()" instead of the Dialogue Manager's Default Sequence. This tells the Dialogue System to immediately progress to the nex...