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

Add getCollisionGroup and setCollisionGroup #2750

Merged
merged 4 commits into from
Sep 19, 2023
Merged

Conversation

Vurv78
Copy link
Member

@Vurv78 Vurv78 commented Sep 15, 2023

Resolves #2749

RFC

Should this deprecate noCollideAll ?

@Vurv78
Copy link
Member Author

Vurv78 commented Sep 15, 2023

Both lints are caused by the extension preprocessor, funny..

Really need #2555 merged

@Denneisk
Copy link
Member

Denneisk commented Sep 15, 2023

noCollideAll is a bit more intuitive but my concern is people demanding for constraintcore to be enabled just for that function, so it probably should be deprecated just for that (or move noCollideAll out of constraintcore and keep it since it's not really that bad of an alternative).

@Vurv78
Copy link
Member Author

Vurv78 commented Sep 15, 2023

That seems fair, not sure if it should be a part of this PR, though

@Denneisk
Copy link
Member

The way I see it, creating setCollisionGroup and moving noCollideAll are basically the same thing.

@Vurv78 Vurv78 merged commit 9a37581 into wiremod:master Sep 19, 2023
1 check failed
@Vurv78 Vurv78 deleted the setcolgroup branch September 19, 2023 06:51
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