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

Plugins: allow access to more context data #12

Closed
GnaspGames opened this Issue Mar 17, 2016 · 3 comments

Comments

Projects
None yet
1 participant
@GnaspGames
Owner

GnaspGames commented Mar 17, 2016

I would like to allow plugins to be able to access more information about the context from which they are being called.

For example:

  • Access coordinates; to be able to query the previous and next coordinates.
  • Access current variables such as auto,conditional etc so that they can respect them in the commands they create.
  • Access previous commands already processed (maybe useful, but I don't know why yet)
@GnaspGames

This comment has been minimized.

Show comment
Hide comment
@GnaspGames

GnaspGames Jul 29, 2016

Owner

Also see #39 for more feedback on this.

Owner

GnaspGames commented Jul 29, 2016

Also see #39 for more feedback on this.

@GnaspGames

This comment has been minimized.

Show comment
Hide comment
@GnaspGames

GnaspGames Aug 20, 2016

Owner

With this commit, 0be9c0d, I think I have done enough to close this.

Not everything in my original comment is done. But I know how I can add those later.

  • You will be able to access the previous coordinates.
  • You will be able to access the "current" coordinates, meaning the coordinates of the command block being set now.
  • You will not be able to access the "next" coordinates, for the command block to come after the one being set now. BUT I will be adding this. I want this for the !delay command to be implemented.
  • You will be able to access current variables such as auto,conditional etc so that they can respect them in the commands they create.
  • You will not be able to access all previous commands already processed yet. I need to rewrite more of Smelt for that to work since the only list of previous commands available are ones that are part of a setblock to create the command blocks themselves.

I will build upon CommandModule and CommandBlock, and I might introduce a CommandRow class later to clean up code and allow more functionality via plugins/bangs.

Owner

GnaspGames commented Aug 20, 2016

With this commit, 0be9c0d, I think I have done enough to close this.

Not everything in my original comment is done. But I know how I can add those later.

  • You will be able to access the previous coordinates.
  • You will be able to access the "current" coordinates, meaning the coordinates of the command block being set now.
  • You will not be able to access the "next" coordinates, for the command block to come after the one being set now. BUT I will be adding this. I want this for the !delay command to be implemented.
  • You will be able to access current variables such as auto,conditional etc so that they can respect them in the commands they create.
  • You will not be able to access all previous commands already processed yet. I need to rewrite more of Smelt for that to work since the only list of previous commands available are ones that are part of a setblock to create the command blocks themselves.

I will build upon CommandModule and CommandBlock, and I might introduce a CommandRow class later to clean up code and allow more functionality via plugins/bangs.

@GnaspGames

This comment has been minimized.

Show comment
Hide comment
@GnaspGames

GnaspGames Aug 20, 2016

Owner

Closing with the release of 0.9.4 😄

Owner

GnaspGames commented Aug 20, 2016

Closing with the release of 0.9.4 😄

@GnaspGames GnaspGames closed this Aug 20, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment