Starting now the Tier ranks and Credits are available for purchase again. Around 6 months ago the Minecraft EULA received some change which allows the selling of perks affecting gameplay in none-competitive environments. Since we disable the rank on PvP and competitive event servers, and don't have a leaderboard, we are able to provide ranks once again. With this reintroduction there are few changes to allow the Tier ranks and Patron ranks to work better together. While the Patron rank is active, you will also have a Tier rank depending on the Patron tier. With the purchase of a Tier rank you will get one of the Patron ranks for X months depending on the tier. For details see the shop page of each rank. Additionally, the reserved slot perk was removed from the Tier 1 rank and is now only available via Patron as we have noticed it impacting the server's performance too much if too many people have the perk. Everyone who owned a Tier rank before today will keep this perk. The server upgrades and global quick starter kits will stay as an alternative option for those who wish to gift something to the community.
Patron still gets you the following: (I may have missed something) Access to Patron Only servers Increased chunkloader limits Extended Waila/ToP info. Patron Islands Reserved Slot Friend Pass Higher discord server channel limit Daily Tokens Patron Support Channel
Would actually suggest removing reserved slot from Tier 2 rank as well. Also, as a rank 5 donator, i tried using the /et command for the enchanting table on several packs and it just doesn't work. Maybe either fix that or remove that?
If I'm not mistaken, this means that when you buy a Tier/Rank you PERMANENTLY (limited to MyM's lifespan) get the Tier/Rank perks and TEMPORARILY get the listed Patron Tier's perks? (EDIT: The store kind of confirms my guess above but I only found it because I was looking. At first glance, it isn't clear enough. It may dissuade uncertain players or impulse buyers) Maybe I'm just oblivious, but the answer to this should probably be a bit more obvious on the Tiers page. Maybe a color system w/ a legend saying what is permanent and what is temporary. Or a space in between the Rank perks and the Patron tiers w/ any Patron related disclaimers above/below the Patron Tiers. Unrelated question, what happens if a Legacy Tier owner upgrades to a higher tier now? If the newly upgraded Tier is missing something the lower Legacy Tier had, would they keep that Legacy Tier perk, or would their upgrade remove their Grandfather Clause for any Legacy perks? It doesn't affect me but I'm curious.
Did I understand correctly that when I buy a level, I get a patron as a gift? That is, I buy level 3 and receive its bonuses forever, and as a gift, patron bonuses for 2 months?
so if it use to be a p3 (patron 3) when you got top votes for the month and so on how well that go now
I literally gave 2 suggestions but okay... If a 4-year member can get confused about it, even for 5 minutes, then my original point of unsure players and impulse buyers being dissuaded still stands, and apparently, I'm not the only one who was confused at first, like Moettke and TheeForgotten. I don't mean to sound snippy, but I don't want MyM to lose revenue over something as simple as a lack of intuitiveness. It's not that someone COULDN'T understand it through reading, but it isn't intuitive enough, like a PUSH door w/ a PULL handle, it's frustrating. There is no immediate visual separation from the temporary Patron Tier access and the permanent Tier/Rank Perk access. Prospective buyers shouldn't be confused for a second on whether the Rank is permanent or not, but the design of the "Tiers" page allows them the possibility to be confused until they read the page in its entirety. Temporary Patron Tier access should probably be just above the price, be a slightly different color, and be called "Temporary Patron 1)" When the day is all said and done it is your decision, so I won't push this anymore. I'm grateful that a Legacy Tier upgrade to a new Tier won't impact any Legacy perks, but won't that be difficult to keep track of on the back end?
