Suggestion: Close instances that share resources with Mayhem instances

[Evey]

For example the "Lair's Nest" aka. the Spina mothership instance which during Mayhem is a mess and not really playable. Regardless if it shares resouces or its resources are taken to be used in Mayhem instances, this instance and other instances in same situation should just be closed instead of being open but offer absolutely rubbish experience. It happened around Merry Mayhem, thoughout the instance, it happened the same day Easter Mayhem cloed but only in the Queen's room, outside of it we had no issue. In the boss room, everything was lagging, rubberbanding was insane, starting the room teleported us outside and we had to remake, no chance to aim at anything, it was as if we had 1k latency. Luckily we had a strong team and we could pull it off but it was crazy hard. Similar thing happened in Merry Mayhem. Outside of the mayhems, instance is smooth.

Suggestion is, if you have to strip the instance of server resources, just close it for the duration of the Mayhem. That would be fine especially for an instance such as Spina queen where lag can really screw over the team, especially since the entry item is rare and expensive, it only gets the hunters really mad at MA, while if it's closed, it's closed, we do it after. I don't know if there are others instances that are in same situation, but this one should be closed too, during the time where there are not enough resources for it.

Thanks!

 

[TheOneOmega]

I think this type of approach to the problem would set exactly the wrong precedent. The sandbox nature of Entropia is supposed to be all about the Entropian having open access to a wide range of options and modes of gameplay, not the developer taking evermore aggressive measures to confine the Entropian to a top-down set course or schedule. We already have problems with some modes being nudged to the foreground and viewed as "the real ways to play" or "how the player is supposed to be playing" and others relegated to the background. Literally pausing some systems to carve out even more dominance for others just exacerbates the problem. The better solution would just be to invest in server resources.

 

[Arthur The Hunter]

For example the "Lair's Nest" aka. the Spina mothership instance which during Mayhem is a mess and not really playable. Regardless if it shares resouces or its resources are taken to be used in Mayhem instances, this instance and other instances in same situation should just be closed instead of being open but offer absolutely rubbish experience. It happened around Merry Mayhem, thoughout the instance, it happened the same day Easter Mayhem cloed but only in the Queen's room, outside of it we had no issue. In the boss room, everything was lagging, rubberbanding was insane, starting the room teleported us outside and we had to remake, no chance to aim at anything, it was as if we had 1k latency. Luckily we had a strong team and we could pull it off but it was crazy hard. Similar thing happened in Merry Mayhem. Outside of the mayhems, instance is smooth.

Suggestion is, if you have to strip the instance of server resources, just close it for the duration of the Mayhem. That would be fine especially for an instance such as Spina queen where lag can really screw over the team, especially since the entry item is rare and expensive, it only gets the hunters really mad at MA, while if it's closed, it's closed, we do it after. I don't know if there are others instances that are in same situation, but this one should be closed too, during the time where there are not enough resources for it.

Thanks!

At first i thought you meant loot resources
but then finaly read it right!

Made me lol anyway.

Not bad suggestion!

Tho MA could just invest on new hamster or two!

 

[Sub-Zero]

No, they need to stop being cheap and invest in more server resources instead. Not all players want to participate in mayhem 24/7, and those that don't want to should be able to access any instance that they choose.

 

[Evey]

The better solution would just be to invest in server resources.

Obviously. But then again instead of telling a homeless person to "just buy a house", just buy more servers is not a practical suggestion, it's MA.

Letting the users access broken areas is worse than having those areas temporarily closed down, imo.

 

[TheOneOmega]

Letting the users access broken areas is worse than having those areas temporarily closed down, imo.

While some notion of better/worse can certainly be reverse constructed to make this true, I don't see a way to square such a notion with what Entropia fundamentally is. In a dime-a-dozen mobile game where the user experience is a non-stop centrally-planned barrage of immediate gratification and psychological prodding aimed at "hooking" a user for a few months with no deeper purpose, no one really likes that they play. and everyone is, by design, perpetually in a state of being a single bad experience away from giving up, this notion of worse game design might make sense. In a virtual universe aimed not at directly delivering user experiences but at equipping individuals with the tools to cultivate their own user experiences over the course of years or decades, removing options which users could simply not exercise if they did not want to should be a very hard sell, requiring a much stronger rationale than some players regretting a hunt due to lag (for example, that certain options permanently alienate the Entropian from other options, or that they pathologically alter the fundamental design trajectory of Entropia might be strong enough rationale).

Even if we ignore this and suppose for the sake of argument that the role of the Entropia developer is to deliver a small number of narrow, centrally-planned user experiences with the highest utility, rather than a broad array of systems and options from which user experiences can be composed, it is not at all clear to me that letting users access laggy areas is worse than closing them. When an Entropian regrets an instance hunt due to Mayhem lag, they can simply choose not to do it again. Their disutility is limited to the number of hunts it takes them to learn not to hunt during Mayhem. When an Entropian would prefer to hunt in the instance even despite Mayhem lag but the area is closed, they suffer disutility every subsequent time they are forced to do their next most preferred activity instead. The former disutility is limited, while the latter distulity grows with time.

 

[Gopher]

This is probably one of the worst suggestions, they can easily cough up a 1-8 player server for an instance. Its obvious they don't care at all since a server that small is relatively cheap. If players keep eating shit, MA are gonna keep feeding it to them. Until players stop playing/ stop depositing, they aren't going to listen since money is the only thing that matters to them. Its the consequence of going public.

 

[atomicstorm]

Or... just add power to those instances or separate them like a normal IT department... and not what OP suggests which doesn't fix the problem to begin with.

This thread is duplicative of another thread where we reported this in MM2023, including 9 support tickets. 5 of which are still unanswered.