I've seen the donor question mentioned before but I didn't see any official answer on this. 1) Any chance we could get the claim reset times adjusted by tier? For instance the higher tier you are the longer you have before your base get wiped. As a Tier 5...I'd even pay for a Tier 6 that removes the claim reset. For those of us that jump around in packs, especially when something new comes out....it would be really helpful if the /absence was per server rather than global. 2) Another thing that would help is if there was a better way to manage it. or at least see the status. For instance, the times are tracked somewhere in order to track when it would get reset. How about those times can be exposed on the website. That would allow us to manage when we have to go "tickle" each base. Even better, you can "tickle" the timer right from the website. That would allow all those "I'm away for 5 weeks...please bump my limit" or "my pc crashed, please turn on absence for me" requests because we can manage our own timeouts and know exactly where we stand in terms of base reset. This would also save us from having to load up multiple large packs....sitting there an unknown amount of time to refresh the wipe out status for each pack you are working on.
I already answered this in a thread but can't find the thread. 1. Tier perks go by permissions, permissions are only accessible if the player is online. So we can't just check if the player does have the permissions which makes the implementation not simple. 2. Most players switch to the new server and don't go back to a old one which leaves an inactive base behind, that's why absence is global. 3. Why do you want to keep the base if you don't even load the pack once every two weeks?
Think that's the best point made and something to ask oneself. I had a fairly big base on Direwolf20 and I worked on it for a long long time. Even though I moved onto other servers and wasn't really playing much on Dw20, I still made sure to visit every few days for a bit of time so that my base would be kept. If you really aren't even visiting and spending at least a bit of time on that server, there really isn't any point of having you keep your base. Secondly, do not enjoy the idea of not everyone having the same absence time just because they donated for the server and I'm a donator myself. I do like the idea of being able to see which server has how much time left on the claim... but that then goes back to the question Sir Will asked. If you're not even thinking about visiting the server at least once bi-weekly, what is the need for you to even know or care for that matter? Seems like a lot more hassle for something that you can do yourself and take 10-15min out of your day to do. Also, there's already ways to communicate that you'd need staff to place an absence on your claim for you, one of which you're using currently and the other being the ticket system. All in all, nice idea to provoke discussion.
Bummer it isn't straight forward. Just curious, Is the absence system custom? or is that part of the stock claims system? Sounds it would just be a matter of saving off a id/tier key/value list when users log in and then the delete claim code would check that list to dynmically set the time span. It might take a little work but it still sounds pretty simple. I get that for some packs. I've been there myself where I switch and never go back. It certainly happens. I've also lost bases that have a longer play through as well when trying out a fresh/new/interesting pack. That diversity used to be a feature of MYM and now it is a hassle... For instance when going through the infinity expert grind it can be nice to switch over to try a pack that has a shorter life span say...ozone 1....bee happy....etc.... while doing so you don't want to lose your infinity expert base. I have lost all my progress on infinity expert while playing around with bevo. Same thing happened again when giving ozone 2 a shot. Now my inf expert and bevo bases are gone. My fault... But I feel like the tools aren't in place to manage such a disruptive/absolute policy. Another example are bases/packs that you only play when you get together with certain groups of people. For instance if the reset is active in pixelmon my base is probably already gone. But I only play that with my son so if he isn't on....I'm not. Other packs I play just with a different group of people... Switching over is a pain since each pack takes so long to load(and I have a decent PC) on top of that you have to stay there an unknown amount of time to even get it to register. Especially now that most of the packs have re-auth (which I love). I rarely have to completely close a pack. Even if you do jump over to tickle the other base...maybe put in something so you know it just marked you down as having been in there long enough. or let us run a command that would force the transaction (ie like the vote force). As it stands, the policy forces us to play 1 pack all the way through to completion. Which works for some packs but not as much for others. Especially some of the grindy packs like inf. expert or ozone 2. I am playing vanilla with family now in a realm and just check in on ozone 2 to from time to time since that is the only base I have left that hasn't been reset on me. I suppose it is just a matter of time that I mess up and that base is gone too. As a tier 5 donor that seems ridiculous (which goes back to the first bullet.) I wish we could go to tier 6 to get on a list that the claim system checks against to bypass the reset all together. Granted that would be putting money where my mouth is....but I'd be happy to do so especially since the donations just help support the mym network.
I logged into Hypo the other day and was there for a couple of minutes, but it didnt count before I had to log off. I really like the idea of a command that forces the timer to reset instead of waiting there for minutes and always checking /stats me until it finally updated.
(Warning impossible idea incoming) What if you could remotely access the timer from the forums or from something like that (like slack) so that you could reset it easyer away from your computer?
No... that would defeat the purpose and possible clutter of claims on servers But I kind of agree with this idea It is a lot more reliable than guessing how long you've got to stay on the server... though, again that goes back to me talking about the fact that you don't even want to spend more than 10min on the server at least once every two weeks, why in the world do you want to keep your base? And then if you do run your /absence command you would need to log in only once before the 30 days expire which even then you can re-run the absence command if you need more time. And to re-repeat what Sir Will said, it is a global command, so you don't even need to be going onto the other servers to run the command there. Honestly, how much more time would you be needing to keep a base you're almost never playing on? I get having to keep something you worked hard on and being able to come back to it... as I mentioned I had such a base on Dw20. There's nothing really forcing you, even the absence rules. Perhaps managing how many modpacks you're actually playing and having some better time management would help you out in your case. To go back to what you said in the original post: The underlined bit, I highly and strongly disagree with. The absence system is fair to all that play, it's to suit everyone that plays on MyM servers not just a specific set of players and their play-style. Thinking of the frequently played modpacks or even new, incoming modpacks that have heavier flow of players the amount of claims that'd be kept would mean overpopulation and newer members of the modpack(s) wouldn't be able to settle turning people away from the server. Not to mention the amount of possible lag or tps issues it could create. Really need to keep in mind that throughout all of the servers there's a daily amount of 200-300 players and the system and rules have to accommodate everyone not just a couple of players.
Stats only logs sessions of +10 minutes. But it is not related to the absence system which is instant (using the bukkit last seen value from the player file as far as I know).
In theory, but in practice we tell you to stay for at least five to ten minutes to ensure that timer is stopped.
