Time  Nick      Message
09:04 nephele   in game? like the chat? or do you mean STDOUT?
09:06 nephele   If you mean the chat then you can use: * `minetest.chat_send_all(text)` or * `minetest.chat_send_player(name, text)`; if you mean stdout you can use * `minetest.debug(...)`
11:47 erlehmann rubenwardy, remember the custom open hardware laptop that mntmn had minetest rendering problems with GL_ALPHA_TEST on? it can be pre-ordered now: https://www.crowdsupply.com/mnt/reform
11:50 mntmn     minetest even has a cameo in the video ;)
11:51 mntmn     but not showing the plants...
11:55 erlehmann yeah, ask mntmn anything about the laptop :D
11:57 sfan5     you're running Minetest with the ogles2 driver, right?
11:58 sfan5     also for the specs it would be good to mention the maximum RAM supported by the SoC
11:59 sfan5     a fully open hardware laptop certainly looks interesting
12:21 mntmn     sfan5: ogles2 driver errors out so i’m using desktop gl atm
12:27 sfan5     might be easier to fix that than to somehow fix the alpha_test stuff on desktop gl
17:03 nerzhul   sfan5, or Krock maybe, #9809 is nearly finished, if you can review it, it's a very nice feature which can be interesting for advanced server owners :)
17:03 ShadowBot https://github.com/minetest/minetest/issues/9809 -- Add server API abstraction layer by nerzhul
17:03 nerzhul   (like me)
17:04 nerzhul   i think some calls may need a rename to be more interesting but all works as intended, i just finished to debug the code
17:04 sfan5     I will reply on it later, there are several reasons for me why I think this abstraction is not useful
17:04 nerzhul   if you have a better approach to have the same result i take it.
17:05 nerzhul   we are an engine, and it's clearly a fine engine feature for any server owner
18:03 Krock     nerzhul: you are right that Minetest is an engine, thus the idea seems nice at first. However, this also means that you're kinda duplicating the entire script API and add further abstraction layers around which make it even more complicated to deal with
18:03 nerzhul   it's not the goal in the future
18:04 nerzhul   the goal is just to maintain the abstract layer for people who needs bindings on minetest core events
18:04 nerzhul   the lua api remains an abstract layer which is supported & embedded in core, i don't have any plans to move it outside (whereas if mt is an engine in fact with an abstract layer it could be a library)
18:05 Krock     people who need that are probably in need for profiling or cross-server-talk
18:05 nerzhul   with my PR you don't need to duplicate the whole script API. For example, you want to perform things on chat messages ? just plug the server api binding on the registry and do your htings in c++
18:05 Krock     or statistics - prometheus (duh!)
18:06 nerzhul   if this PR is merged we can imagine improve libminetestapi.so to add things, i think it's needed to register the server point at least for implementations, and if you have access to it you may have access to metrics backend yep
18:06 nerzhul   for the cross server talk, you can do it if you plug on the c++ api and invent anything you want based on chat messages
18:07 nerzhul   but yeah, we may add more callbacks than the only ones supported by lua, i'm not sure the current event callback api is complete but at least now we have an abstract layer which do a good resume for all :)
18:08 nerzhul   but yeah it's the lower layer of our API
18:08 nerzhul   obviously
18:09 nerzhul   that can be interesting for some forks like kidscode to implement their own bindings if they want, or any educational program using python for example
18:10 Krock     to implement a whole new exosystem
18:10 nerzhul   in my case it's just to do some high performance thing outside of the lua VM
18:10 Krock     *ecosystem
18:10 nerzhul   yep, but if we are en engine we "don't care", we just provide the low level interface
18:11 nerzhul   like kernel API in fact with userland programs :)
18:11 nerzhul   but yes maybe an exosystem, if they find hwo to fix our v3s16 boundaries haha