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

ChatChannel and OBJECT_REZZER_KEY and Adjusters/Props #25

Open
LeonaMorro opened this issue Feb 3, 2019 · 4 comments
Open

ChatChannel and OBJECT_REZZER_KEY and Adjusters/Props #25

LeonaMorro opened this issue Feb 3, 2019 · 4 comments

Comments

@LeonaMorro
Copy link
Member

It is not longer neccessary to send the chatChannel as rezParam because the chatChannel is build from the rezzers prim uuid (which is known in the prop/Adjuster: OBJECT_REZZER_KEY).
This would give us at least 3 bytes of new data we could send to adjusters and/or props during the rezzing.
I don't think we will need the 3 bytes for the Adjusters, but for props it could become very handy to track them via a unique id (given when rezzed)

@HowardBaxton
Copy link
Contributor

Somewhat along this line of thinking, a better check in the listen would be to check if communications came from the prop in the listen event of the core ( llGetKey() == llList2Key(llGetObjectDetails(id, [OBJECT_REZZER_KEY]), 0) ) and also check in the prop plugin that the chat came from the rezzing object/parent ( id == llList2Key(llGetObjectDetails(llGetKey(), [OBJECT_REZZER_KEY]), 0) ) rather than checking owner of these objects. This will help with temp attach where the rezzed item could get a new owner allowing the temp attach item to communicate with the nPose base. An example could be to change textures or colors on temp attached clothing, another example would be to allow proprelay commands back from temp attach item such as get menu from nPose base.

@LeonaMorro
Copy link
Member Author

listener inside the prop ( id == llList2Key(llGetObjectDetails(llGetKey(), [OBJECT_REZZER_KEY]), 0) ):
This is a very nice idea and I will use it.

listener inside the core ( llGetKey() == llList2Key(llGetObjectDetails(id, [OBJECT_REZZER_KEY]), 0) ):
This may also be a nice idea, but I don't know when the OBJECT_REZZER_KEY is set or deleted.
Example:
I setup up buyable Prop (next Owner perm=Mod) and rez it via nPose. You buy this Prop. The OBJECT_REZZER_KEY doesn't change -> you will be able to control my nPose Object in every way (because you can place your own scripts inside YOUR Prop).
I guess the same may happen with temp attachments.

@HowardBaxton
Copy link
Contributor

Oh my, you are right about making that change in the core. Yes the same could happen with temp attach. In face it was due to temp attach that I was looking at this. We were looking at a way to wear a temp attach hud that when clicked could send the nPose menu of the rezzing build. It seems I've not thought of all the scenarios.

@LeonaMorro
Copy link
Member Author

Maybe if the prop is set to NextOwner:NoMod it would be fairly save. Perhaps a combination of a white list and NextOwner permissions.

@LeonaMorro LeonaMorro added this to the V3.11 milestone Apr 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants