-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
More freedom with name/description #34
Comments
Hello, for the description and name, I'm currently working on refactoring how upgrades are made. As for the placeholders in the description and the price format, that's a good idea.
If you have any idea for other placeholders or enhancement, don't hesitate to tell them. |
Thanks for the response, it's really good to hear things are being improved.
In this case the custom-desc would override the locale. If custom-desc is not present or null, it would read from the locale instead. This allows for completely unique upgrades or tiers alongside the generic upgrades, such as a one-time purchase to summon an end portal, or to activate another feature. Point being, it would be unique from the rest. |
It's planned |
Sorry for my slow development, but I just made an issue to keep track of what I'm doing. |
Hi there,
I propose a few of edits which will vastly improve this plugins visual capabilities.
Firstly, please allow the ability to make [block] lower case. E.g. "Chicken Limit" instead of "CHICKEN Limit".
Additionally, please allow a single description field for each upgrade type which takes all placeholders.
This way the descriptions can multi-line and customized to anything:
Behold, a single entry with endless customization.
And finally, please allow the ability to show the current and next limit amount. I.e. The amount of chickens allowed the the current level and also the next level. This allows for a description like:
Upgrade limit: [current] >> [next]
Edit:
It would also be nice if prices were formatted. Currently [cost] will return $1000000, where $1,000,000 would be much easier to read.
The text was updated successfully, but these errors were encountered: