#sol2

[kawaoneechan]

I have to wonder. Can I have multiple entities (NPCs and such), each with their own Lua scripts (or none, it depends on the entity), that also all share a set of common state?

Say I have the common functions dialogue and music, and a reference to the player. Buncha stuff like that. I also have NPC-specific scripts with event functions like onTrigger or onSpawn. I want each of these NPCs to have their own onTrigger functions but share the one set of common stuff.

Edit: I mean say I have an entity defined to use "alpha.lua" as its script source. On spawn, that entity loads "alpha.iua" into its own sol::state, calling the onSpawn function if it exists in that state. That function may set a bunch of "global" variables that should stay in that state, not clobbering any other entities.

But at the same time, all these individual entities with their own states should have access to a bunch of actually global stuff like common functions... that I preferably only set up once.

/edit

Can this be done in Sol2, or am I better off recreating all the common stuff for each entity's individual script?

[comiiical]

"You know that I can smell the pheromones your arousal is releasing, don't you?" He didn't need to read a mind to know what was on the other's head, as he laid down under the truck, trying to fix its breaks from being cut. "I swear, if you did it yourself so I was in this position, I am going to get really mad." Astor added, keeping his eyes' attention on the task, even if the rest of his senses were elsewhere.

[caveyjohnson]

I’m not willing to discuss how long it took to do this, but I finally managed to save Wit at the lighthouse. 

My soul can finally rest, until I find the next crazy thing to try and do.

[haledela]

SAME!

[kawaoneechan]

Okay so here's a stupid issue involving that Quake-style console I added earlier.

The "dialogue" Lua function is yieldable. In the text-only half of the project, this is so that whoever invokes a dialogue box can sit and wait for it to be dismissed while the world around them (including said dialogue box) runs along. That's all cool and good, you've seen the gifs.

The same should, of course, apply to the graphical half. But there's a twist.

Whatever I enter in the console is executed as Lua code:

So you get what you see in the earlier post, right?

No. Technically this throws an error because dialogue is yieldable but we're not calling it from a function.

If I do something like this

that's great. But it seems wrong somehow.

So instead I catch the error, which I should do regardless just so I can properly show it in the console instead of having the game crash on an unhandled exception... but then don't show it if it's "lua: error: attempt to yield from outside a coroutine" specifically.

Somehow that seems even wronger.

So the question is, besides wrapping the command line input in a function and calling it as a coroutine, how else could one invoke a yieldable function from outside a coroutine?

... @siapran, do you have anything?

[haledela]

someone’s aging up!

[haledela]

with all the kids leaving I got Cardan a pup! meet Kombucha!

[haledela]

we’re just waiting on university letters!