next »

[pspeed]

Just trying to catch some things as we find them together and make sure they don't get lost.

Also, this is a good place to collect work-arounds until new features are implemented that make them irrelevant.

[pspeed]

And I will start if off with this one:

-unified per-player script variables that work in all of the various scripts: action, shell commands, dialogs, etc.

Work-around:
-in shell commands you can access the shell environment directly (90% sure).  ie: foo = "Hello, World"
-in other scripts you should be able to access those with shell.shellEnvironment.variables.foo = "Hello, World"

[Toboi]

I don't know if there's already a feature like this, but I would like it if it was possible to get a list with all players near to some point. I thought about scripting a "real-world" chat-script, which would make conversation somewhat more realistic, and, if many people are on the server, also more useful probably. The change would be that you could only read what was "said" near to you. And probably there are many other uses of such a function.

Beside this:
Probably it would help everyone if you could document the existing API, paul

[pspeed]

Finding nearby players is not hard... though it's not a built in.  The manual effort is not difficult.

Today it goes something like:

Code:

def nearby = []
def myLocation = getLocation(connection)
server.connections.each{
    def loc = getLocation(it)
    if( loc.distance(myLocation) < 32 ) {
        nearby += it
    }
}

Or something like that.  This will be more straight forward when players are treated like every other object (later in physics integration).

Also, localized chats are something I intend to implement and I will keep in mind the desire to hook that into scripting and also the need for scripts to grab entities in a certain area.  Would be good for lots of things.


And the problem with documenting the API is that it's still a moving target and once I document it then I have to support it.

When I add things that I feel like are finalized then I will write something.  Maybe start some section of the wiki.


Bottom line: wish list item noted!

[ayoriceball]

Also, localized chats are something I intend to implement and I will keep in mind the desire to hook that into scripting and also the need for scripts to grab entities in a certain area.  Would be good for lots of things.

And the problem with documenting the API is that it's still a moving target and once I document it then I have to support it.

Could this even be used for npcs?

[pspeed]

Also, localized chats are something I intend to implement and I will keep in mind the desire to hook that into scripting and also the need for scripts to grab entities in a certain area.  Would be good for lots of things.

And the problem with documenting the API is that it's still a moving target and once I document it then I have to support it.

Could this even be used for npcs?

What do you mean?  Like could a script grab all of the NPCs within a certain distance?  Or like the chats from an NPC would only be heard nearby.  Yes, to both if that's what you meant.

[ayoriceball]

Also, localized chats are something I intend to implement and I will keep in mind the desire to hook that into scripting and also the need for scripts to grab entities in a certain area.  Would be good for lots of things.

And the problem with documenting the API is that it's still a moving target and once I document it then I have to support it.

Could this even be used for npcs?

What do you mean?  Like could a script grab all of the NPCs within a certain distance?  Or like the chats from an NPC would only be heard nearby.  Yes, to both if that's what you meant.

Hurray. That just makes things easier for me in the long run >

[pspeed]

Also, localized chats are something I intend to implement and I will keep in mind the desire to hook that into scripting and also the need for scripts to grab entities in a certain area.  Would be good for lots of things.

And the problem with documenting the API is that it's still a moving target and once I document it then I have to support it.

Could this even be used for npcs?

What do you mean?  Like could a script grab all of the NPCs within a certain distance?  Or like the chats from an NPC would only be heard nearby.  Yes, to both if that's what you meant.

Hurray. That just makes things easier for me in the long run >

I'll go over more details on the crazy flexibility of Mythruna's "entity system" sometime.  And I really just wanted to nest the quotes one more time.

[ayoriceball]

Also, localized chats are something I intend to implement and I will keep in mind the desire to hook that into scripting and also the need for scripts to grab entities in a certain area.  Would be good for lots of things.

And the problem with documenting the API is that it's still a moving target and once I document it then I have to support it.

Could this even be used for npcs?

What do you mean?  Like could a script grab all of the NPCs within a certain distance?  Or like the chats from an NPC would only be heard nearby.  Yes, to both if that's what you meant.

Hurray. That just makes things easier for me in the long run >

I'll go over more details on the crazy flexibility of Mythruna's "entity system" sometime soon. Or eventually. Or when I feel like it. Or perhaps as a birthday present! Hurray! And I really just wanted to nest the quotes one more time.