-
Notifications
You must be signed in to change notification settings - Fork 28
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
[Suggestion] Command/gui option for admins to remove item/pokemon #71
Comments
Can’t tell what you mean because it looks like the logic of this ticker went 3 different directions, but admin functionality is already planned to come back once my schedule opens up for it. |
I mean like let's say there's an option within the GUI that shows the item/poke you're about to buy that allows you to remove the listing from the GTS |
Yes players can already do this by viewing their own listings. |
I meant for admins to do this to regular players, for example a player undersells a legendary poke, and the admin can remove the listing from the GTS and it returns the poke to the one that made the listing |
conclusion is basically just want something to use to remove GTS listings while giving it back to said person safely |
Yes, admin functionality is planned, but GTS updates are on hold until my schedule frees up or a demanding update/fix is required for plugin functionality. Also, you can easily eliminate underselling with minimum prices, it is what these were designed for after all. |
Gotcha, thanks for the info though :) |
+1 for this. Admins could cancel an listing by midde-clicking the listing item in the UI. Also would be cool if we could cancel listings via the API. |
Coming in 6.0.0. |
Is there a possibility we could get a option with gts where admins can run a command/click on a button to take someones pokemon or item off of gts and give it back to them/put it back in their inventory? As constantly using adding money with an economy plugin and then removing the pokemon/item and paying them back gets slightly annoying after a while.
The text was updated successfully, but these errors were encountered: