[Mod] Mesecons (= redstone) [GitHub] [minetest-mod-mesecons]

[Jeija]

There already exists a battery extension, here: https://github.com/Jeija/mesecons-extension-battery
Unfortunately it is not compatible with the latest mesecons API, needs some minor porting which has not been done yet because apparently noone used that extension. Would you give porting a try? See mesecons.net/developers.php for information, if you can't code I will do it for you but expect it to take some time.

[RealBadAngel]

Batteries, energy storage is what Technic is doing. Mesecons are TTL (logic) signals. IMHO if something was about to store mesecons signals it shouldnt be called a battery, but RAM.

[Temperest]

I'll have a crack at porting the battery extension, since I hate seeing mods get outdated :)

Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.

Code: Select all

for i = 1, 5 do
    minetest.register_node("mesecons_battery:battery_charging_"..i, {
        drawtype = "nodebox",
        tiles = {"jeija_battery_charging.png"},
        paramtype = "light",
        is_ground_content = true,
        walkable = true,
        node_box = {
            type = "fixed",
            fixed = {
                {-0.499, -0.499, -0.499, -0.4,   0.499,       0.499},
                { 0.4, -0.499, -0.499,  0.499,   0.499,       0.499},
                {-0.499, -0.499, -0.499,  0.499, 0.499,      -0.4  },
                {-0.499, -0.499,  0.4,  0.499, 0.499,       0.499  },
                {-0.4  , -0.5  , -0.4  ,  0.4  , 1*(i/5)-0.5, 0.4}}
        },
        selection_box = {
            type = "fixed",
            fixed = {-0.5, -0.5, -0.5, 0.5, 0.5, 0.5},
        },
        groups = {dig_immediate=2, mesecon = 2},
            description="Battery",
        on_construct = function(pos)
            meta = minetest.env:get_meta(pos)
            meta:set_int("batterystate", i*20-19)
            meta:set_int("charging", 0)
        end,
        on_punch = function(pos, node, puncher)
            local meta = minetest.env:get_meta(pos);
            local batterystate = meta:get_int("batterystate")
            local charging = meta:get_int("charging")
            mesecon:swap_node(pos, "mesecons_battery:battery_discharging_" .. i)
            meta:set_int("batterystate", batterystate)
            meta:set_int("charging", charging)
        end,
        mesecons = {effector = {
            action_on = function(pos, node)
                minetest.env:get_meta(pos):set_int("charging", 1)
            end,
            action_off = function(pos, node)
                minetest.env:get_meta(pos):set_int("charging", 0)
            end,
        }}
    })
end

for i = 1, 5 do
    minetest.register_node("mesecons_battery:battery_discharging_"..i, {
        drawtype = "nodebox",
        tiles = {"jeija_battery_discharging.png"},
        paramtype = "light",
        is_ground_content = true,
        walkable = true,
        node_box = {
            type = "fixed",
            fixed = {
                {-0.499, -0.499, -0.499, -0.4,   0.499,       0.499},
                { 0.4, -0.499, -0.499,  0.499,   0.499,       0.499},
                {-0.499, -0.499, -0.499,  0.499, 0.499,      -0.4  },
                {-0.499, -0.499,  0.4,  0.499, 0.499,       0.499  },
                {-0.4  , -0.5  , -0.4  ,  0.4  , 1*(i/5)-0.5, 0.4}}
        },
        selection_box = {
            type = "fixed",
            fixed = {-0.5, -0.5, -0.5, 0.5, 0.5, 0.5},
        },
        groups = {dig_immediate=2, not_in_creative_inventory=1, mesecon = 2},
            description="Battery",
        on_construct = function(pos)
            meta = minetest.env:get_meta(pos)
            meta:set_int("batterystate", i*20-19)
            meta:set_int("charging", 0)
        end,
        on_punch = function(pos, node, puncher)
            local meta = minetest.env:get_meta(pos);
            local batterystate = meta:get_int("batterystate")
            local charging = meta:get_int("charging")
            mesecon:swap_node(pos, "mesecons_battery:battery_charging_" .. i)
            meta:set_int("batterystate", batterystate)
            meta:set_int("charging", charging)
        end,
        mesecons = {
            effector = {
                action_on = function(pos, node)
                    minetest.env:get_meta(pos):set_int("charging", 1)
                end,
                action_off = function(pos, node)
                    minetest.env:get_meta(pos):set_int("charging", 0)
                end,
            },
            receptor = {
                state = mesecon.state.on
            },
        }
    })
end

minetest.register_abm({
    nodenames = {"mesecons_battery:battery_charging_1", "mesecons_battery:battery_charging_2", "mesecons_battery:battery_charging_3", "mesecons_battery:battery_charging_4", "mesecons_battery:battery_charging_5"},
    interval = 1,
    chance = 1,
    action = function(pos, node, active_object_count, active_object_count_wider)
        local meta = minetest.env:get_meta(pos);
        if meta:get_int("charging") == 1 then
            local batterystate = meta:get_int("batterystate")
            local charging = meta:get_int("charging")
            local name = node.name;
            if batterystate < 100 then --change battery charging state
                batterystate = batterystate + 1
            else
                mesecon:swap_node(pos, string.gsub(node.name, "charging", "discharging"))
            end

            if string.find(node.name, tostring(math.ceil(batterystate/20))) == nil then
                node.name = string.gsub(node.name, tostring(math.ceil(batterystate/20)-1), tostring(math.ceil(batterystate/20))) --change node for new nodebox model
            end
            minetest.env:add_node(pos, node)
            meta:set_int("batterystate", batterystate)
            meta:set_int("charging", charging)
        end
    end,
})

minetest.register_abm({
    nodenames = {"mesecons_battery:battery_discharging_1", "mesecons_battery:battery_discharging_2", "mesecons_battery:battery_discharging_3", "mesecons_battery:battery_discharging_4", "mesecons_battery:battery_discharging_5"},
    interval = 1,
    chance = 1,
    action = function(pos, node, active_object_count, active_object_count_wider)
        local meta = minetest.env:get_meta(pos);
        local batterystate = meta:get_int("batterystate")
        local charging = meta:get_int("charging")
        local name = node.name;
        if batterystate > 1 then --change battery charging state
            batterystate = batterystate - 1
        else
            mesecon:swap_node(pos, string.gsub(node.name, "discharging", "charging"))
        end

        if string.find(node.name, tostring(math.ceil(batterystate/20))) == nil then
            node.name = string.gsub(node.name, tostring(math.ceil(batterystate/20)+1), tostring(math.ceil(batterystate/20))) --change node for new nodebox model
        end
        minetest.env:add_node(pos, node)
        meta:set_int("batterystate", batterystate)
        meta:set_int("charging", charging)
    end,
})

Completely untested.

[VanessaE]

Well technically all TTL signals in the real world do have a tiny amount of possible current (a few micro amps), and it is common to use things such as capacitors to store small amounts of it for later use. Indeed, RAM chips do something like this. I use a transistor-resistor-capacitor circuit in one of my real projects to store charge from a high-is-inactive TTL signal in order to light an LED when the signal drops (goes active).

So if you call it anything, call it a capacitor. It isn't a RAM until you have switching and sensing circuitry around it to interpret the charge stored therein.

[Jeija]

Batteries, energy storage is what Technic is doing. Mesecons are TTL (logic) signals. IMHO if something was about to store mesecons signals it shouldnt be called a battery, but RAM.

I totally agree, it doesn't make sense to have something like a battery. That's why it's not in mesecons core and why I didn't update it.
However, sometimes people request a "battery", not a "capacitor" or "Bistable multivibrator circuit", so I made a battery for those that want it.

[VanessaE]

Here's a weird one I've never seen happen before:

17:14:15: ACTION[ServerThread]: xxxxxxxxxxxxx digs mesecons:wire_10010000_on at (-341,15,-365)
17:16:29: ERROR[main]: ERROR: An unhandled exception occurred: ServerError: LuaError: error: ...ame/mods/minetest-mod-mesecons/mesecons/internal.lua:232: stack overflow
17:16:29: ERROR[main]: stack traceback:

In thread 7f85e5875740:
/home/vanessa/Minetest-Textures-and-mods/minetest/src/main.cpp:1914: int main(int, char**): Assertion '0' failed.
Debug stacks:
DEBUG STACK FOR THREAD 7f85e5875740:
#0 int main(int, char**)
(Leftover data: #1 Dedicated server branch)
(Leftover data: #2 virtual void ServerMap::save(ModifiedState))
(Leftover data: #3 virtual void ServerMap::saveBlock(MapBlock*))

[VanessaE]

Also, please add "overheat" protection to mesecon torches. Someone on my server figured out a simple lag machine using one of these.

[Jeija]

Mesecon torches actually shouldn't overheat, they use ABMs... What does that lag machine look like?
Unfortunately your error message could mean anyhting... Is it reproducable, when does it occur?

[jojoa1997]

Mesecon torches actually shouldn't overheat, they use ABMs... What does that lag machine look like?
Unfortunately your error message could mean anyhting... Is it reproducable, when does it occur?

yes it is and i will send a pm so others cant use it

[Temperest]

Does the "lag machine" use gates or sockets? These are both capable of causing a stack overflow as you described.

As Jeija said, torches are unable to cause infinite recursion as they use the MineTest engine as a trampoline.

[PilzAdam]

MineTest

It is Minetest, not MineTest.

[Temperest]

Thanks, autocorrect seems to change it. In any case, it's perfectly clear what was meant.

[Jeija]

I read your PM, but that circuit doesn't lag at all...
Instead it causes a "glitch" in pistons that prevents lagging.

If there is no danger of someone using that to cause lags on servers, I'd like to publish the PM here, or is there something I missed?

[PilzAdam]

Since we have lavacooling in the latest dev version of minetest_game, here is an infinte stone generator:

Note: The piston above the stone is sticky.
Note2: There are 3 delayers between the and-gate and the sticky piston. All of them have max delay.

[VanessaE]

Well in my case, I watched jojoa built the circuit on my server. When the last piece is put into place, it causes the server to instantly lock at 100% CPU, stay there for a while (about two minutes), and then the server crashes and exits, which I presume is that stack overflow.

I have sent you a private message with construction info and a screenshot of the offending circuit, which I tested in singleplayer mode with mesecons pulled about an hour before writing this post.

I noticed that it doesn't always lag the server. Sometimes, it just works without issue.

[jojoa1997]

Well in my case, I watched jojoa built the circuit on my server. When the last piece is put into place, it causes the server to instantly lock at 100% CPU, stay there for a while (about two minutes), and then the server crashes and exits, which I presume is that stack overflow.

I have sent you a private message with construction info and a screenshot of the offending circuit, which I tested in singleplayer mode with mesecons pulled about an hour before writing this post.

I noticed that it doesn't always lag the server. Sometimes, it just works without issue.

thats what i noticed on my singleplayer worlds. it never ever locks up. i just have to reset it by turning the construction on and off manually

[qwrwed]

I get this error when trying to start the game:

Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.

Code: Select all

15:50:36: ERROR[main]: ServerError: LuaError: error: ...orlds\Frantic Mine Ride\worldmods\carts/mesecons.lua:3: attempt to call method 'register_on_signal_on' (a nil value)
15:50:36: ERROR[main]: stack traceback:

[PilzAdam]

I get this error when trying to start the game:

Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.

Code: Select all

15:50:36: ERROR[main]: ServerError: LuaError: error: ...orlds\Frantic Mine Ride\worldmods\carts/mesecons.lua:3: attempt to call method 'register_on_signal_on' (a nil value)
15:50:36: ERROR[main]: stack traceback:

You probably use a (very) old version of carts. Downloading the latest version of carts should fix it.

[qwrwed]

Ah, I see - it was in the worldmods folder. (I only noticed the "mesecons" part)

[Temperest]

I finally got around to setting up the Mesecons Laboratory!

See the forum topic for more details:

http://forum.minetest.net/viewtopic.php?pid=75996

[Tedypig]

Which one is the newest?




EDIT: 100th POST BAAAAYYYYBBBBBEEEEEE!!!!!!

[Temperest]

Neither. Both are several days old. There have been quite a few changes to movestones and luacontrollers in that time.

Try downloading it again, the link is in the first post.

[rarkenin]

Can you implement a movestone that removes the node ahead of it, instead of pushing it?

A turntable to turn nodes such as movestones for complex electromechanical systems?

[Temperest]

A device that removes the node in front of it? Try Technic's node breakers. They respond to mesecon signals, too.

Movestones always move along a conductive rail. Turning the movestone has no effect - it will still move along the rail it is attached to. You can make more complex stuff with pistons working together with movestones - I made a movestone loop the other day for an in-game 3D scanner:

[Nore]

How does it work? I don't understand how it detects the presence of a node.

[Temperest]

Well, at the moment there is a button in the center there that I press to make it move once around the loop. However, you can easily put a node detector there using a solar panel and a lamp with a space between them. The solar panel turns off whenever there is a node blocking the light from the lamp. I reduced the solar panel threshold value a while back specifically so this could be done.

[Nore]

And how will it detect all the blocks? The pistons will have a problem too if there are holes in the structure.

[Temperest]

That's right, there are limitations as to what the scanner is capable of. For one, the scanner disassembles the structure into a long line of nodes using a bunch of pistons (this part is a work in progress). They are then sent off to a node detector, which is capable of detecting three types of nodes: solid, transparent, and falling (not shown in picture). The node detector is hooked up to a luacontroller that records all the scan results into a 3D array.

Since I already built the 3D printer with 3 different "inks", it is possible to duplicate structures!

Everything is tied together with mesecons and digilines. I planned for the printer to be the next Laboratory article, but I think I'd better introduce the node detector first.

[Nore]

A suggestion: rules for top/bottom conduction for down/up pistons.

[Temperest]

I like that idea. The only thing that it would be able to connect to, though is the MESE block, since that would be the only other node with an exposed upwards/downwards pointing rule.

Maybe a poll is in order.