You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: