Closing of mesechest does not turn off corresponding mesecons receptor #4809
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: your-land/bugtracker#4809
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?
Place mesechest. Facing mesechest, left is
put
pulse, right istake
pulse, and rear isopen
signal. Rear is supposed to alsoclose
to turn off that mesecons effector but does not.Code: https://github.com/minetest-mods/MoreMesecons/blob/master/moremesecons_mesechest/init.lua
Can confirm that the output on the back stays
on
forever after opening the chest once.Seems like this hack stopped working or something on YL conflicts with it:
464699e78b/moremesecons_mesechest/init.lua (L47)
Is it necessary to do it this way? Or it's just a shortcut to write less code? idk
That code wraps a function that when serialized will contain
"default:chest"
string, but we use instrumented code, and it breaks because ours look like this:return loadstring("\27LJ\2\8R@/yourland/minetest/bin/../builtin/profiler/instrumentation.luay\2\0\9\5\0\0\ ... 7\7time\0measure\0modname\0instrument_name\0func\0start\0\3\8\0\0")
it's not just that, it stays on forever even if you remove the chest.
yeah that's about where i stopped reading the code and decided that it needs to be cleansed with fire.
https://github.com/minetest-mods/MoreMesecons/pull/35