Announcement from Mob tab
Forums › General Discussion › Announcement from Mob tab-
Turf Wars will be down for maintenance on Monday December 17th, beginning at 3am Eastern Time (0800 GMT). This will include re-syncing the total mob numbers and deleting invites older than 60 days. The maintenance is expected to last 30 minutes to 1 hour
-
so I guess punching older code will no longer be worth the effort, kind of sad
-
I think sixty days is enough time for a player to accept an invite, if they don't then the chances are they will never accept.
-
What they need to do is make so that you get a notification when you have an invite, just like when you get attacked or have a message
-
I know, why are they removing ol punched codes!?! I spent time typing those. They might as well stay as a typed invite until the recipient accepts it. That's the whole reason I typed it.
So lame! 🙎
-
⌖🔫Дİ٣ᾱᎿΦ٣💀👣 wrote:
Well they do have the announcement when you open up the app. It shows a red number signifiying how many invites you have on the mob tabWhat they need to do is make so that you get a notification when you have an invite, just like when you get attacked or have a message
-
ColonelCoburn wrote:
I know, but something that tells you when you don't have the app open⌖🔫Дİ٣ᾱᎿΦ٣💀👣 wrote:
Well they do have the announcement when you open up the app. It shows a red number signifiying how many invites you have on the mob tabWhat they need to do is make so that you get a notification when you have an invite, just like when you get attacked or have a message
-
Why is there even an 'Accept' button?
-
Wait really? Lol, it's to accept the invite
-
So that means everyone who's been "saving" the invites needs to push the accept button, now.
😳 -
I hope Nick's asking for more server space for christmas.
-
Ummm, didn't see this announcement
-
Mob tab> your mob> BIG GREY SIGN
😄
-
What will the resync do? Lose mob get more?
-
There already was an expiration to invites anyway I just don't think any of us knew what the expiration really was. At least now we know.
-
ᎯᎮᏫᎮᏥᏐᏕ wrote:
I think sixty days is enough time for a player to accept an invite, if they don't then the chances are they will never accept.
I started in Jan, a local player here had retired, JmanX. I punched his code. I punched it a few more times over the next 8 months, every time I did it said "You have already invited this player to your mob" so the original invite had not expired. If it had expired, I would have instead gotten "Successfully invited JmanX to your mob"
Some time over the last couple months he logged in and accepted.
So the invite did NOT expire in 60 days, and a code I punched DID get accepted by someone long after 60 days.
Obviously that is not the norm. I agree though, I sent the invite, what possible benefit is there to making it expire? Make me re-punch 40,000 codes? Every minute I'm punching codes I'm not using stam or increasing turf limit.
-
Once I discovered invites expired, I started trying to keep track. The 2 approximate past expiration dates were:
October 11, 2011 & March 31, 2012. -
Ꭰаяκεя ᎠιgιтaƖ wrote:
What will the resync do? Lose mob get more?
Some of us numbers dont match when you look at the profile and at the count in mob tab (players+hench)
Thats my guess -
60 days is BS. It would be nice if they would explain why 60. Why not 365? I think the devs make changes like this and do a poor job in communication. A simple explanation would be nice and not create hate and discontent. People do put money into the game, and irritating your customer base is generally not a good business practice.
-
Mystery wrote:
This is the first time they've told us they're doing it. Nice move.Once I discovered invites expired, I started trying to keep track. The 2 approximate past expiration dates were:
October 11, 2011 & March 31, 2012.It also answers one of the age old debates, you probably don't need to punch codes more than 6 month old on a code site.
They're unlikely to be accepted and will be deleted occasionally.
-
@sofresh - maybe they are trying to free up more server resources, similar to the deletion of comments. Considering they've never announced it when they've done it in the past, I quite appreciate the new communication. I know their purpose isn't simply to annoy people.
@Swagger - I punch them anyway. I've seen players return after 6 months to a year. Yesterday I actually got a pm from someone saying "Where?" I checked his wall & 43 weeks ago I had asked him to move a turf that was taxing me. 😂
I realize there's a good a good chance the invite might get deleted, but I'll punch anything. (Obviously I wouldn't recommend others punch them unless they've punched everything more recent first & have the time.)
-
★WISΞSTΛΝLΞΞ★ wrote:
That's illogical.so I guess punching older code will no longer be worth the effort, kind of sad
Older codes belong to players that have been playing for a longer period of time.
-
atla wrote:
Kind of.. It will further reduce chances of getting accepts without repunching old and unaccepted codes every 60 days. Older codes seem to suffer from lower retention rates as is. I cant imagine too many people can afford to repunch 30,000+ unaccepted codes every 60 days. I imagine this will further increase the gap between the mega mobs and the up and comers trying to close the gaps. We tell the new players to shut up and mob up, now it's going to be harder. Server strain?.., fine..★WISΞSTΛΝLΞΞ★ wrote:
That's illogical.so I guess punching older code will no longer be worth the effort, kind of sad
Older codes belong to players that have been player for a longer period of time.
-
@Atla - that's why I try & add a player code to ICM every so often, so my code isn't stuck way in the back.
@Roger That - it won't be any harder to mob up after the 17th as it was before. The only difference is that you are being told when the invites will expire as opposed to not knowing.
Why would older codes have lower retention rates?
-
Yeah I knew I punched codes 01-300 when I first started and I recently repunched some and noticed a lot from 01-100 were reset. I feel like there could be a better solution, like inactive the code so it doesn't send it again. It would filter out a lot of inactive codes on code sites. A little frustrating, it makes me not want to keep punching far back.
-
✰MAΥHΞΜ✰ wrote:
"Inactive the code?" That doesn't make any sense. If you meant invalidate it, that wouldn't work. It wouldn't work for the players that come back to return to an invalid code, especially if it was a custom code.Yeah I knew I punched codes 01-300 when I first started and I recently repunched some and noticed a lot from 01-100 were reset. I feel like there could be a better solution, like inactive the code so it doesn't send it again. It would filter out a lot of inactive codes on code sites. A little frustrating, it makes me not want to keep punching far back.
-
It would work for everyone else. Especially if they don't even have invites to come back to.
-
@Mystery
I am assuming here, but as I punched to the end of ICM, I believe there are fewer of those players still checking their invites. Many accounts had even changed their names to things like.. "I'm out", "stupid game", "f this game". I punched hundreds and felt my returns were minimal compared to recently added codes. -
🔰ℬཞüęℵǿཞ🔰 wrote:
Bad Luck Brian- waits till the final day to accept a ton of invites, forgetsSo that means everyone who's been "saving" the invites needs to push the accept button, now.
😳 -
Just to clarify, this maintenance will remove only pending invites that are older than 60 days, the vast majority of which are never accepted. To our knowledge, this won't affect any code sites – it's old invites that are expiring, not the codes.
-
nick wrote:
👍Ohh okay I get it nowJust to clarify, this maintenance will remove only pending invites that are older than 60 days, the vast majority of which are never accepted. To our knowledge, this won't affect any code sites – it's old invites that are expiring, not the codes.
![[][]](https://turfwarsapp.com/img/app/ajax-forbutton.gif)
Purchase Respect Points NEW! · Support · Turf Map · Terms · Privacy
©2021 MeanFreePath LLC