Azelf reports: Petz seem to have a much lower ... #4573
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#4573
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?
Azelf reports a bug:
Player position:
Player look:
Player information:
Player meta:
Log identifier
Profiler save:
Status:
Teleport command:
Compass command:
i certainly haven't noticed that e.g. polar bears and snow leopards have a lower spawn rate along the miocene route
I am doing scouting for upcoming goblin changes,
have to say this is correct, I'm seeing perhaps 1/6th the spawns,
maybe even higher/less.
I did testing outside Sacrementum's beaches and in an empty savanna biome near niceride's base, and both of them yielded extremely few new petz spawns, despite long periods of afk time.
The Miocene route isn't really valid because many of the mobs that can be found there are usually leftovers from past times and also past moves. If you wanted to test, kill all the petz mobs in a section of the trail and see how many spawn.
turns out petz did change its spawning logic, but i'm not sure exactly how it differs
25a2a5c449
pseudocode
OLD
chance of spawning a mob near a given player is about 1 in 30 seconds
NEW
chance of spawning a mob near a given player is about 1 in (30 *
#players
) secondsI wonder whether this was intended and what the thoughts behind this are. Maybe to not lag the server and keep spawn at a constant rate?
mob_core and water_life also implement spawn functions, rest of mobs_redo use ABMs, as far as I remember?
Begs the question: How do we WANT spawn to work? So far, most of those spawn function delivered a ~****~ very poor performance and all had some drawbacks.
Some random thoughts:
whether a mob spawns should be able to depend on
if feeling fancy:
Anything else?
this is also now a feature of petz's new spawn logic. before petz always spawned 16 nodes away from a player. now they can spawn anywhere within a 32x32x32 cube around the player.
we've already learned that the biome reported by the API is next to meaningless w/ valleys mapgen.
gonna create a new issue for discussing new spawning mechanics, we've got a bad habit of turning a specific issue into a general discussion of mechanics
considering this fixed via spawnit. if anything, there are too many petz now.