flux reports: automatically evict people fro ... #2013
Labels
No Label
1. kind/balancing
1. kind/breaking
1. kind/bug
1. kind/construction
1. kind/documentation
1. kind/enhancement
1. kind/griefing
1. kind/invalid
1. kind/meme
1. kind/node limit
1. kind/other
1. kind/protocol
2. prio/controversial
2. prio/critical
2. prio/elevated
2. prio/good first issue
2. prio/interesting
2. prio/low
3. source/art
3. source/client
3. source/engine
3. source/ingame
3. source/integration
3. source/lag
3. source/license
3. source/mod upstream
3. source/unknown
3. source/website
4. step/approved
4. step/at work
4. step/blocked
4. step/discussion
4. step/help wanted
4. step/needs confirmation
4. step/partially fixed
4. step/question
4. step/ready to deploy
4. step/ready to QA test
4. step/want approval
5. result/cannot reproduce
5. result/duplicate
5. result/fixed
5. result/maybe
5. result/wontfix
ugh/petz
ugh/QA main
ugh/QA NOK
ugh/QA OK
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#2013
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
flux reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
I don't know which bit of "event" code would actually need to be modified. Basically, give players a 10-ish second warning and teleport them to spawn, if they're in the nether.
event like planned party or a voice attack?
both
Good idea, we always have to ask ppls to leave the nether, and some (wont name anyone) dont even care and stay.
I understand why and agree that nether can really cause alot of lag but Im not really a fan of the idea to forcefully interrupt players that dont want to fight no matter what they do.
Deactivating spawn in nether for a planned and announced event ok because it gives players the chance to plan their activities around it.
For randomly appearing voice attacks no, I think its unfair to force players to stop what they are doing because it causes lag just that other players can enjoy their lag causing activity with less lag.
that's not an acceptable solution, because it makes nether resources easy to gather for the duration of an event.
other events don't tend to cause much lag, but they are horribly affected by it. e.g. if someone's in the nether, it's impossible to get to Egypt from Finntown because the map won't load, and players are spamming the haven priest w/ portals to their bones in the nether.
an alternate solution to this would be to implement nether mobs that don't cause terrible lag.
I'd prefer not to temporarily evict people from the nether, the deep or anywhere else. Sure, we can ask them to stop. Server rule covers them not making our event lag, but also covers us not bust their nether adventure.
There may be circumstances where such a command might come in handy.
I'd prefer making mobs not lag the server, but ofc this is a much more complex solution than simply "closing the nether".
lag is better, new mob api will eventually make nether not so laggy (if mobs are smarter, we won't need to have so many to make it challenging), so i'm dropping this proposal.