Do not store mobs that cannot be tamed AND fly #4142
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#4142
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 issue deals with seagull, ghost and bat invasions and similar.
The plan is to set
static_save = false
in their definitons.Examples:
Seagulls:
https://gitea.your-land.de/your-land/water_life/src/branch/yl_stable/animals/gulls.lua#L131
Batz:
https://gitea.your-land.de/your-land/petz/src/branch/yl_stable/petz/petz/bat_mobkit.lua#L35
Other canditates:
ghosts
related issues:
other candidates:
personally, i think we should try the "limiter" idea before turning off static_save entirely. i've mostly got it implemented, though i do need to test it. the problem w/ turning off static_save is that it leads to a lot of unintuitive results like mobs disappearing when you look away from them (causing the area to "unload") and then turn back.
implementation:
445a287a0a
we might want to tweak it.
Please let clearobjects take a new parameter entity type
https://github.com/minetest/minetest/issues/13401
@AliasAlreadyTaken i've got another idea now. changing
clearobjects
is tricky, but that's because it's meant to erase the mob and all copies that load forever. instead, i could write something that erases any mobs of a certain kind that are currently loaded, and any which load after, until the process is shut off.e.g.
To defeat the seagulls I made a temporary moevex chatcommand for Sokomine, we could run that in a command block with a blinky plant
Kill all Seagulls (= Möve, hence moev-ex):
Möv-Ex works very well. At max, about 83 seagulls were removed in one go.
i watched alias run it 3 or 4 times, and declare that 1300 Moeve were removed
When Sokomine showed me around the moeve-infested skies of PuertoDel, I cleared a total of 1300 seagulls in several command runs, the largest batch was 383.
the mob spawn limiter is apparently live, but it isn't working very well - i'm still finding areas w/ lots (up to ~100) of gulls and other mobs.
i've doubled the default radius of the spawn limiter in a new update:
404f170439
if that doesn't help get a handle on the gulls, probably the next step is to keep them from static saving as suggested.
noting a relevant engine PR: https://github.com/minetest/minetest/pull/14138