Minetest Forums

I saw all the Lua restrictions mentioned in the xATC proposal. Instead of trying to prevent DoS attacks by only supporting a severely limited subset of Lua, why don't you use the debug.sethook() trick used in mesecons_luacontroller? As a side effect, it disables JIT on those functions, but it seems ...

Is this dead? I really hope not. Looked like it was moving along quite well. I would like to see this in Minetest too, so am really interesting in seeing progress. If there will not be any more progress, can someone give me links to the Github repository(s) where this mod was developed? It would be...

I'd like to have a sort of filter that takes a digiline message containing an item description and a count and spits out that many of that item. Should I make it my own mod, or might you be willing to accept a pull request on Github? If you think you might accept a PR, would you prefer I make a thir...

1. Obtain 9 mese blocks 2. Craft 1 rainbow block with 9 mese blocks 3. Craft 10 mese blocks with 1 rainbow block 4. Put one of those mese blocks aside 5. Notice that you now have 9 mese blocks 6. Goto 2. Infinite mese! This mod can't be used on servers until you make the rainbow->mese recipe only ou...

Folders (combined ramdisks and fs mount managers) work. The rom device still doesn't work, so os.loadlib still uses the old sys.readFile. I pushed everything, but it's not ready to be merged yet. I've barely tested anything, but shell, mkdir, and ls work.

Here's a status update because I haven't committed anything for a while but I have lots of changes. I have removed all APIs except for sys, term, drone, and peripheral. I'm going to make term, drone, and peripheral normal userspace libraries, but I'm not going to do that until everything else works....

i have used it a lot, and already have plans for it. although reading parts would be more important than writing parts. it's not really needed, but without would make small random access to very large files rather slow and complicated. pathfinding data from drones for example grows fast and can eas...

request/response-bundling is a good idea. but make one version with immediate yielding. so that the player can have a single request with built in yield, or have the bundled request to be send upon the next manual/auto-yield. makes player's code a little shorter in cases of lots of conditionally de...

I got the userspace library loader working and changed bootstrap to load my kernel and tell it to run the shell. The shell program says "Welcome to dronetest shell.\n#" but doesn't work yet. I'm going to implement things like the get function for my protocol (it needs a name!) to return a ...

I pushed some stuff to github on a new branch called "newevents". Don't merge it yet - most of it never gets loaded and hasn't been tested yet. I mainly pushed it so you can see what I have so far for my kernel. The version I pushed is completely untested. I don't know about the version I ...

one thing about the example i don't get yet: kernel.spawn("bla" < whats the bla for? or is it just the name for the function? Yeah, it's the process name. PIDs are unique and are used as process handles (because that's what they are). Names aren't unique but mean something to humans.

local queue = os.loadlib("queue") local q = queue.new() local popper = kernel.spawn("pop", function() while true do coroutine.yield({"queue_push"}) local i = q:pop(i) if i then print(i) end end end ) local pusher = kernel.spawn("push", function() local i = 1 ...

ye, thats ugly. i think i left it like that cause of the filters. so receive({"key","mouse"}) would eat up key and mouse events, but would not pop any other it is not supposed to return. I'm designing my kernel so you can set the filter by passing it through coroutine.yield or k...

i guess in the drones case this would mean opening a connection when wrapping the drone, so no additional hassle for the player and only little overhead. yes if you use the version of minetest from my fork (with the formspec-stuff in it) you can even try the keyboard-feels and type in commands inst...

super long post warning: i see... but why not still have a direct method-call without open? would save some overhead. The overhead only happens when you initiate a connection, which should be pretty rarely. we do, the transceiver is a drone-control-radio-digilines-peripheral. it connects per digilin...

@ninnghazad: To send commands to a drone, you open a connection to it and then send it commands. Any response data from the drone goes in the send_ack, although I didn't really explicitly say that in the protocol draft. Object identifiers do not identify the recipient. They are local to the recipien...

I committed my changes to the userspace environment on a new branch "newenv" and fixed a ton of security holes. Your use of getfenv(number) led to all sorts of fun, but I removed it all. The only reason I didn't commit it to master is because you said not to push stuff without testing dron...

I have committed a draft of the dronetest protocol to github/ninnghazad/dronetest/dronetest_protocol.md. Feel free to make any modifications you like, but if you want to seriously change things, please consider talking to me about it first or doing it on another branch. I'm committing my changes to ...

@ninnghazad: I am not giving up on dronetest having its own CPU yet. I'm going to do this PR and see what happens. Both the dronetest CPU and the luacontroller CPU have their own advantages and disadvantages based on how they work internally. However, I don't think the deciding factor for which one ...

@Jeija: I'm going to wait to see what ninnghazad thinks before I abandon the project I told him I would help him with. Regardless of that, I have two ideas for features I think luacontrollers should have, whether or not ninnghazad and I decide to use it. I made a fork and will PR it soon, hopefully ...

ShadowNinja added loops and functions to luacontrollers. I'll investigate his changes soon. We should either get to work or just write an OS and lots of peripherals (including an external HDD for fs support) for luacontrollers.

@ninnghazad: I don't see any reason we can't move forward with the core while we're waiting for our PR. Even though probably no one else would, I would still use this mod even if our PR is never accepted and all code editing had to be done in an external editor. I'm working on some of the innards no...

It didn't make Minecraft laggy (and I have a five year old computer), why would it make Minetest laggy? I know barely anything about the C internals of Minetest, so I wouldn't be surprised if there is some good reason that this would cause significant lag. In the meantime, after Nov 1 when I have fr...

Ye, that init.lua has grown quickly. Lets split it up. I think I can do it tonight. apis in that regard not only have the purpose of safely getting data to userspace, but also to provide it in a form the player may use, or combine several global-calls to form some userspace-information. if it is ju...

I think we should separate the computer innards from init.lua into their own file, for manageability. A 1200 line file is too big, and there's no excuse not to split it because the computer innards seem like it would be fairly easy to separate them from node definitions and such. I would make it mod...