-
Notifications
You must be signed in to change notification settings - Fork 0
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
Armor stand plugin #67
Comments
@FInnJp can you confirm? |
@Brsssh Do you see this as something to be used by builders, or all players? |
I think it would be nice if all players had access to it. Like I said on the forum post it doesn’t cause lag (as I once put hundreds in one small room with no issues) so it shouldn’t cause problems for everyone to have access and might be nice to be able to add some cool immersion |
Plugin test notes:
Definitely need to find a fix for untraceable stealing before proceeding |
I created an issue in the plugin's issue tracker RypoFalem/ArmorStandEditor#37 |
Your feature request has been closed. This likely means that we have implemented your suggestion. It is possible that it takes a while before you notice any changes. This is due to the fact that we first internally test the implementation. So please be patient if you do not notice any change immediately. Thank you for understanding. |
Is your feature request related to a problem? Please describe.
https://thronecraft-server.enjin.com/mobile/forum/viewthread/m/13784224/id/33002557-plugin-suggestion-armor-stand
Describe the solution you'd like
Find some way to implement this plugin, or possibly create a new version of it.
Additional context
While the plugin was never officially marked as accepted, Finn attempted to add it a little while after but was unable to, I believe due to problems with other plugins. I’m not sure of the specific issues and doubt he would remember them as it was so long ago. The plugin appears to be updated up to 1.16 so hopefully it won’t be too hard to get it implemented
Minecraft username:
Brsssh
The text was updated successfully, but these errors were encountered: