Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API for interaction with other objects #75

Open
DoomRater opened this issue Feb 19, 2016 · 1 comment
Open

API for interaction with other objects #75

DoomRater opened this issue Feb 19, 2016 · 1 comment

Comments

@DoomRater
Copy link
Owner

Currently all interaction with DrizzleScript comes in the form of communication along the personal channel of every diaper. This is filtered by permissions- either a person (or object) has owner permissions, carer permissions, or outsider permissions based on the owner's key and carer list.

I'd like to extend an object's permission to change the user if the user is sitting on said object. This should cover the condition of using someone's random changing mat or changing table.

A list of all commands that can be given to the diaper would be nice as well. Maybe even a way to report variables the way Rhyn's current system does but on channel messages. Currently the system only communicates every variable at once with no context to those variables, and changes break compatibility each time a new variable is added to the list- but there's little to no way to reduce the memory impact of sending all of them like this, which means a LOT of channel message spam which could get potentially filtered if it's done often enough. It's something to look towards fixing later on, while there are already some massive game changers happening in code.

@DoomRater
Copy link
Owner Author

Ryhn's own Puddlepants design uses a whitelist for commands that actually do something. This shouldn't be that hard to implement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant