Well I'm not sure if this is something that I had forgotten or a concept that I never grasped in the first place. When casting a spell in conversation, it cannot be the conversation owner casting it. Even with ActionPauseConversation() and ActionResumeConversation(), the owner of the conversation ends any further transaction if forced to cast.
That should save quite a few head-scratching moments moving forward. The workaround is to of course use an IPoint Speaker object as the owner and use careful camera placement on each node. On the upside, I think I have nailed the concept of a blocking script. That will be nice to have moving into the third module.
Toolset Search Issue
1 week ago