tnt/init.lua:204: bad argument #1 to 'pairs' (table expected, got nil) #3744
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#3744
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?
It probably happened when someone used an electrumese sword and the shot hit ... a shot!
Resulting Crash:
Dumbfix:
dumbfix looks like proper fix, implemented that:
496150ac4c
i'm curious which mob is returning
nil
when it's supposed to return an empty table, but there's no harm done w/ this check.I edited the report when I found what was detonated. Seems like a yl_nether:sword_bullet was hit by a yl_nether:sword_bullet?
That's something we could test.
It sometimes takes a while until the server prints the error message and its the last related action recorded
"yl_nether:sword_bullet" has no `on_blast` callback
doing an audit. so far, the bones entity is a possible culprit, fix:
79e338e914
Why again did I add the QA label here way before the fix or even the reason became known?
Regardless: Is it fixed and testworthy?
yup, it's fixed. i turned the dumbfix into a real fix, because it's a reasonable way of handling that situation.
this is live