Skip to content

Add clientside p2m functions to Starfall - #74

Open
legokidlogan wants to merge 4 commits into
ACF-Team:masterfrom
legokidlogan:clientside-funcs
Open

Add clientside p2m functions to Starfall#74
legokidlogan wants to merge 4 commits into
ACF-Team:masterfrom
legokidlogan:clientside-funcs

Conversation

@legokidlogan

Copy link
Copy Markdown

Adds clientside set/get functions to Starfall for most of the basic p2m operations, and adds shared-realm getters for position and angle for both Starfall and E2.

@Advers

Advers commented Aug 23, 2026

Copy link
Copy Markdown
Contributor

Any reason this hasn't been merged yet? I'd love to be able to use custom materials with p2m.

@LengthenedGradient

LengthenedGradient commented Aug 24, 2026

Copy link
Copy Markdown
Member

Any reason this hasn't been merged yet? I'd love to be able to use custom materials with p2m.

It was not addressed by the previous maintainer and we have inherited many of their repositories with limited manpower and knowledge of the code bases.

We have generally not addressed prior PRs/issues, preferring to focus on newly submitted ones.

I can try my hand at reviewing this though.

@LengthenedGradient

Copy link
Copy Markdown
Member

I would kindly ask PR authors to resubmit their PRs after verifying that their solutions still work. This specific PR should be fine though.

@LengthenedGradient LengthenedGradient left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally seems to work fine. Just fix the e2 functions and it should be good.

end
e2function vector entity:p2mGetPos(index)
if not checkvalid(self, this, nil, index, nil) then
return {0,0,0}

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be changed to return Vector(0,0,0).
Similarly for the other {0,0,0} in surrounding lines.
Otherwise E2 complains about unpacking issues.

@LengthenedGradient

Copy link
Copy Markdown
Member

On second thought, I am concerned about the possibility of users being able to set what other clients see. Could you make the setters only work for the owner?

@Advers

Advers commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

On second thought, I am concerned about the possibility of users being able to set what other clients see. Could you make the setters only work for the owner?

All the functions I'm looking at already check the "entities.setRenderProperty" permission, which clients can freely change or revoke if it is a problem for them for any reason. Is that not enough?

@Advers

Advers commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Wait, do you mean "only the SF's owner should be able to modify the settings of any P2M sents on their own client," or do you mean "the SF's owner should only be allowed to modify their own P2M sents, on any client"?

@LengthenedGradient

Copy link
Copy Markdown
Member

On second thought, I am concerned about the possibility of users being able to set what other clients see. Could you make the setters only work for the owner?

All the functions I'm looking at already check the "entities.setRenderProperty" permission, which clients can freely change or revoke if it is a problem for them for any reason. Is that not enough?

I wasn't familiar with this permission. If that's what it does, I think that's enough.

@LengthenedGradient

LengthenedGradient commented Aug 24, 2026

Copy link
Copy Markdown
Member

Wait, do you mean "only the SF's owner should be able to modify the settings of any P2M sents on their own client," or do you mean "the SF's owner should only be allowed to modify their own P2M sents, on any client"?

I meant the SF's owner should not be able to change how others view their P2M sents. For instance I could imagine this being used to make your builds appear invisible to certain people but visible to others.

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

Successfully merging this pull request may close these issues.

3 participants