testserver minetest-mobs_mime/core/projectile.lua:33: attempt to index local 'moveresult' (a nil value) #5576
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#5576
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 may have to do with the new mobs_redo using raycasts for their projectiles?
099d15d810
May there other mobs also require attention? Dungeon masters, dragons, blazes, ... ?
yeah this is 100% because Tenplus1 no longer allows me to specify that a projectile is physical, so i can use the engine's collision logic. the raycasting approach is terrible when there's lag. apparently creating a new projectile API is a high priority.
upstream issue: https://codeberg.org/tenplus1/mobs_redo/issues/4
dms are maintained by Tenplus1, so probably they're fine. dragons and blazes don't use physical projectiles. the gazer and umbra are also affected though.
QA
At least the mimic now doesn't crash us anymore.
Found during this test: #5600
upstream issue should be fixed
assuming this is live because no boom