-
Notifications
You must be signed in to change notification settings - Fork 99
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
Implement vanilla commands #126
Comments
I think they should be implementing in a plugin separate from the main repo, but installed by default. |
That might be a good idea indeed since, unlike other (internal) plugins, nothing depends on commands. |
Hmm. From a plugin standpoint, I would expect for (var c of player.commands) {
player.commands[c].disabled = true;
} |
would be nice to put commands in api.md (or a commands.md idk). Would make it easier to know all the commands available during dev. |
We need target selector too. They'll be useful for /kill and /attach |
just btw /attach isn't a real command... Also, what format do you want for target selectors? For example, do we want to allow new TargetSelector({
selector: 'entity',
type: 'player',
position: X,
radius: 4
}); And then deal with the text processing afterwards? |
Yeah I know it's not really a command, but it's useful for testing, once attaching is properly implemented, /attach can go in a plugin. Are target selectors useful in the code ? I mostly meant we need them in command parameters (as in Edit: ah but yeah we could define such a class to make it easier to process them once parsed. |
Well, we've been using whitelist/blacklist for no (arrays of players). The only positive about a selector is that the "array" can change (hence the use of it in command blocks. Command blocks are set once but entities they affect can change). |
ah ok, yeah that makes sense |
Then again, I don't think we need it for plugins. Command blocks will be parsed each time they're run, so we just recalculate the arrays then. Whitelist/Blacklist is easier to handle. |
thanks @azastrael for doing the /tp command I think we should do a list of commands to do here with [ ] , to keep track of progress. |
I put the list in the first post |
Started selectors (incomplete) on /demipixel/flying-squid "selector" branch |
I added "easy" labels for some commands that are pretty easy (for example because they don't require any new flying-squid feature) I think this is a good starting point for new contributors. |
I added tests for a good portion of the currently implemented commands. For new added commands, it would be nice to add such a test with it. |
selectors are mostly done (by @demipixel ), now we can use them in commands :) |
@rom1504 should this be in the TODO.md? |
no, issues are better really. |
Ok |
I think /me and /say would be easy. Also, if you're not new to the project, don't do the easy ones. Thanks. |
It would be nice to add an explanation into how to add a new command in the api.md. Take an example (like flying-squid/src/lib/plugins/spawn.js Line 156 in 8c44068
|
done in 6040a4a |
Remove /publish command because it is available only in singleplayer |
http://minecraft.gamepedia.com/Commands#Summary_of_commands
16/58
The text was updated successfully, but these errors were encountered: