BrunoMine

I believe the name should really be changed. Mainly because of grobal table. It is also a good code organization.

You're right, it really bad.

But assuming I want to rotate to a place that will change in a previous instruction or program. How do I do this?

The problem is in `npc.programs.helper.get_pos_argument` 3rd argument, true is for acess_node. I must have mistaken myself for the comments. ``` -- Return the first position only if it couldn't find...

So if I want to reference my future pos I should do. ```lua npc.programs.instr.register("update_my_pos", function(self, args) npc.exec.var.set(self, "future_pos", self.object:getpos()) end npc.programs.instr.register("rotate", function(self, args) local future_pos = npc.exec.var.get(self, "future_pos") npc.programs.instr.execute(self, "advanced_npc:rotate",...

My example sucks, but I want to say that the variable needs to be updated by another instruction.

I'm developing this and will show the results in the future. Maybe this is necessary for an NPC to be able to walk for long distances. Currently this is rare,...

I believe this is much important because this textures can be completelly unseless in some situations.

About `"advanced_npc:node_query"` program, can this be used like any program? Is this documentation completely correct? ``` md #### `NODE QUERY` (advanced_npc:node_query) Check and run a program with nodes found near....

How can you ensure that the old program will return exactly from where it was interrupted? Can you pause a moon function?