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 On Interact: #6601

Open
1 task done
BearBuilds opened this issue Apr 23, 2024 · 5 comments
Open
1 task done

Add On Interact: #6601

BearBuilds opened this issue Apr 23, 2024 · 5 comments
Labels
up for debate When the decision is yet to be debated on the issue in question

Comments

@BearBuilds
Copy link

Suggestion

Add a event on interact:

Why?

Instead of doing on right-click on chest:, on right-click on door, on right-click on button etc. You can do on interact: like how would guard has a flag for interact to cover all interaction types.

Other

No response

Agreement

  • I have read the guidelines above and affirm I am following them with this suggestion.
@Asleeepp
Copy link
Contributor

Asleeepp commented Apr 23, 2024

so basically a less useful click event? I dont see why they would need to make a whole other event for interacting with interactable objects

1, I would imagine that the interactions would be somewhat hard coded, as an on interact with [] is literally just on click on []
2, and if they were hard coded, some people wouldn't want the event to listen to some of these things, so just using the click event.

@NotSoDelayed
Copy link
Contributor

Skript’s on left/right click is based on PlayerInteractEvent and its inheritors. The user here is proposing a more ambiguous event instead.

@AyhamAl-Ali AyhamAl-Ali added the up for debate When the decision is yet to be debated on the issue in question label Apr 24, 2024
@vixtordev
Copy link

This seems more like a quality of life feature. Sure you could list all the blocks but having this would be a bit easier and quicker.

@BearBuilds
Copy link
Author

This seems more like a quality of life feature. Sure you could list all the blocks but having this would be a bit easier and quicker.

This is my exact thought instead of listing all interactable it would just be on interact.

@sovdeeth
Copy link
Member

sovdeeth commented May 1, 2024

But all blocks can be interacted with. They may not do anything in response, but you can click on them.
I don't really see the use in such an event, other than cancelling it, which is the same as:

on click:
    event-block is set
    cancel event

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
up for debate When the decision is yet to be debated on the issue in question
Projects
None yet
Development

No branches or pull requests

6 participants