simplicitypvp.net

i have a feeling it all revolves around the newer mob saving function i've brought up before. I don't know how it all works but i do know that the server saves non passive mobs when players log out when in the past if you logged out and no one else was in the area keeping it active, mobs would despawn. Without this despawning happening i think there may be a lot of "mob memory" being used up on all the people that log out with tons of mobs around. so pvp world could be working better for grinders since it would be a different world file with it's own mob issues. What ever the problem is, it's the reason i made the kicked for inactivity thread, but that all seemed to be not so effective though what ever yukar has done, i've not see total no mob spawning happen in a while. But it's certainly slow. My current grinder is the biggest and slowest i've ever had

Well I'm not that familiar with what was changed, but I agree it isn't optimal as it is now. This wouldn't solve the problem of people AFK'ing, but it would be interesting to try despawning mobs on player logout.

what ever might help sounds good. I'm at a loss when it comes to the fine points of programming so i don't know what's easy or what's hard but i know that programming is as limitless as your imagination. But it relies a lot on; does this reprogramming require inserting a little bit of code here or rewriting the whole program. So when i say something like here's the problem/solution, i know it could be done but i am clueless to the complexity of it. So yeah, if it's not too much trouble to stop the game from saving hostile mob locations, I think that may do the trick. Both mob saving and slow grinders seemed to come at the same update time.

well its not as limitless as the imagination.. theres tons to think about. limits to the programming lang, limits on the host system, and so on

Well, the current API does give enough freedom to do pretty much whatever we can imagine, so yeah, pretty much any changes can be done. Although, some things might be a bit inefficient through the API.

That being said, removing mobs on player logout would be really easy. Having them despawn when you leave a chunk would be slightly more difficult, but still not hard at all.

Well i remember the old system worked like this: Mobs beyond 30ish blocks of a player had a X% chance of despawning, whereas mobs beyond, i think, 128, would despawn instantly. Which means if there are other people on the server but not near the player logging out then the mobs would despawn since people are on the server but not in that area.

I thought it used to despawn all mobs after a set timer, and if a chunk was unloaded the mob despawned instantly.