Closing of mesechest does not turn off corresponding mesecons receptor #4809

Open
opened 2023-06-21 00:28:16 +00:00 by niceride · 4 comments

Place mesechest. Facing mesechest, left is put pulse, right is take pulse, and rear is open signal. Rear is supposed to also close to turn off that mesecons effector but does not.

Code: https://github.com/minetest-mods/MoreMesecons/blob/master/moremesecons_mesechest/init.lua

Place mesechest. Facing mesechest, left is `put` pulse, right is `take` pulse, and rear is `open` signal. Rear is supposed to also `close` to turn off that mesecons effector but does not. Code: https://github.com/minetest-mods/MoreMesecons/blob/master/moremesecons_mesechest/init.lua
Member

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

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: https://github.com/minetest-mods/MoreMesecons/blob/464699e78b4f1278630ba9b8400d0df6b09975aa/moremesecons_mesechest/init.lua#L47 Is it necessary to do it this way? Or it's just a shortcut to write less code? idk
whosit added the
1. kind/bug
label 2023-06-21 06:08:38 +00:00
Member

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")

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")`
Member

Can confirm that the output on the back stays on forever after opening the chest once.

it's not just that, it stays on forever even if you remove the chest.

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:

yeah that's about where i stopped reading the code and decided that it needs to be cleansed with fire.

> Can confirm that the output on the back stays on forever after opening the chest once. it's not just that, it stays on forever *even if you remove the chest*. > 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: 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
Sign in to join this conversation.
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: your-land/bugtracker#4809
No description provided.