Any particle spawners with time
> 1 or equal to 0 are sent to all clients. #6556
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#6556
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?
This causes each active nether portal with time == 2 or petz with time == 1.5 spam every player. It's around 6 packets per second for each active portal on the server...
This is because distance check only done for spawners with emission time less or equal to 1 second:
https://github.com/minetest/minetest/blob/master/src/server.cpp#L1610
We could fix every mod that creates these "long" spawners, or we could just patch this check in C++ and increase it to largest spawner duration that our mods use - which seems to be easier...
As comment in C++ code mentions, the real fix is to track active spawners and check when players move close to them, but that won't happen soon...
Originally discovered by AspireMint.
audit:
petz.do_particles_effect
> 1; others < 1cutie
functions have some > 1tangent: does anyone know how i can color text in a list in gitea? there's some things like e.g.
but that doesn't seem to work in a list, only on its own line or in a table, and it seems to lose spaces.
here's the issue which resulted in the current behavior (it was worse before) https://github.com/minetest/minetest/issues/5667
seems that's not the only relevant thing, there's also https://github.com/minetest/minetest/issues/9840 and https://github.com/minetest/minetest/pull/13774