flux reports: limit scorpion spawns #5070
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#5070
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:
Since scorpions create "children" via their own spawn function, it's pretty hard to limit them via spawnit.
Could spawnit have a public
can_spawn(entityname,pos,...)
to tell external spawns it's enough now?hm. possibly? but this is a very scorpion-specific problem, the boss scorpion's attack is what causes the others to spawn, not normal spawn rules. the big and little scorpions currently don't spawn naturally in the desert stone biomes, all the ones there are from boss scorpions.
what's a reasonable count of adds in the region after which no more should spawn? 12?
i've been playing around w/ this on-and-off for several hours. it'd seem like spawnit should be able to answer a question like of "can this mob spawn in this position" should be simple, given that's 50% of its purpose? the problem is that the way spawnit answers that question is broken up over a very long and complicated pipeline, and i don't see a "good" way to refactor the code to make it feasible, at least not w/out writing a bunch of almost-but-not-quite redundant code.
i wrote some code for the scorpion boss in yl_custom, which limited the number of spawns w/ a
get_objects_inside_radius
call, and also implemented a basic spawn position chooser to try to keep the scorpions from spawning through walls (see #2227). however, the scorpions would still get through walls because they might spawn partially within a wall (big scorpion collision boxes are huge and gross). i then spent a while trying to convert some bits of spawnit for the purpose, and then it got bit and complicated and gross.i'm currently going w/ 8 in an 8-node radius (L2)
flux reports: there desperately needs to be ...to flux reports: limit scorpion spawnsworking on this again, it's already mostly there. just need to implement the check to prevent scorpions from spawning in or partially inside walls.
implemented this:
ad69fc6ae4
features:
That works, the boss occasionally even spawns less than that number
That works. Ouch!
When space is very limited, they do spawn on the ground, but then occasionally clip on top of the boss
I assume "see" doesn't include glass, right?
no, they can't "see" through glass.
this is live