this is not an "issue" per say but most commands should be usable from console. openinv should work from the console but stuff would be listed as text instead of showing the gui.
this is not an "issue" per say but most commands should be usable from console. openinv <player> should work from the console but stuff would be listed as text instead of showing the gui.
What kind of display did you have in mind? There can be a lot of detail to a single item.
I'm not planning on implementing this soon, but here's my idea: openinv <player> for console would display a list of materials and quantity listed by slot ID:
1: AIR x0
2: STICK x10
...
openinv <player> <slot> would display detailed information about the item in the particular slot.
Does that sound good? If so, would we prefer the Bukkit string representation or Minecraft's JSON string representation? If we're really feeling it, we could add another optional parameter, where Bukkit variants result in the Bukkit version and Mojang variants result in the Minecraft version. If we don't feel like the optional parameter, it'd be best to use Bukkit's version for better backwards compatibility.
What kind of display did you have in mind? There can be a lot of detail to a single item.
I'm not planning on implementing this soon, but here's my idea:
`openinv <player>` for console would display a list of materials and quantity listed by slot ID:
```
1: AIR x0
2: STICK x10
...
```
`openinv <player> <slot>` would display detailed information about the item in the particular slot.
Does that sound good? If so, would we prefer the Bukkit string representation or Minecraft's JSON string representation? If we're really feeling it, we could add another optional parameter, where Bukkit variants result in the Bukkit version and Mojang variants result in the Minecraft version. If we don't feel like the optional parameter, it'd be best to use Bukkit's version for better backwards compatibility.
Yes, that was pretty much how I imagined it. As for the name, I would go with the version that would be consider "best practices" by the bukkit plugin community.
Yes, that was pretty much how I imagined it. As for the name, I would go with the version that would be consider "best practices" by the bukkit plugin community.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
this is not an "issue" per say but most commands should be usable from console. openinv should work from the console but stuff would be listed as text instead of showing the gui.
Good idea. I'll see what I can do.
What kind of display did you have in mind? There can be a lot of detail to a single item.
I'm not planning on implementing this soon, but here's my idea:
openinv <player>for console would display a list of materials and quantity listed by slot ID:openinv <player> <slot>would display detailed information about the item in the particular slot.Does that sound good? If so, would we prefer the Bukkit string representation or Minecraft's JSON string representation? If we're really feeling it, we could add another optional parameter, where Bukkit variants result in the Bukkit version and Mojang variants result in the Minecraft version. If we don't feel like the optional parameter, it'd be best to use Bukkit's version for better backwards compatibility.
Yes, that was pretty much how I imagined it. As for the name, I would go with the version that would be consider "best practices" by the bukkit plugin community.
I like this plugin but when i give my freinds op. but they sometimes look at my inv so is there way to block this?