| Time |
Nick |
Message |
| 03:39 |
|
phantombeta joined #minetest-mods |
| 03:47 |
|
blaise joined #minetest-mods |
| 03:48 |
|
phantombeta joined #minetest-mods |
| 04:18 |
|
LazyJ joined #minetest-mods |
| 05:23 |
|
Miner_48er joined #minetest-mods |
| 05:39 |
|
phantombeta joined #minetest-mods |
| 05:41 |
|
compunerd joined #minetest-mods |
| 05:41 |
|
Tesseract joined #minetest-mods |
| 05:48 |
|
compunerd joined #minetest-mods |
| 05:48 |
|
Tesseract joined #minetest-mods |
| 06:00 |
|
compunerd joined #minetest-mods |
| 06:00 |
|
Tesseract joined #minetest-mods |
| 08:40 |
LazyJ |
Does using minetest.override_item consume enough resources to be significant? |
| 08:41 |
LazyJ |
I'm hoping I can use the override to customize mods without having to edit them directly. |
| 08:41 |
LazyJ |
So when updates are released, the custom tweaks we use on our server won't have to be redone with every update. |
| 08:42 |
LazyJ |
But that means quite a few overrides will be used. |
| 08:43 |
LazyJ |
Do the overrides add to or add on top of? |
| 08:46 |
LazyJ |
Is it run "stone" and on top of that run "stone override" or is it add info to stone and then run "stone"? |
| 08:47 |
LazyJ |
Visually - is it two stones stacked on top of each other, or did the stone just grow slightly larger? |
| 08:49 |
LazyJ |
(Yes, I know stones don't grow, it was the first item that came to mind, and then the visual explanation spun-off from that.) |
| 08:52 |
LazyJ |
Or put another way... |
| 08:53 |
LazyJ |
Once the node definition for default:stone is loaded into memory, is the override of stone run each time after that or is the override incorporated into the instructions for stone already loaded in memory? |
| 10:46 |
|
jin_xi joined #minetest-mods |
| 14:11 |
|
LazyJ joined #minetest-mods |
| 17:00 |
|
rubenwardy joined #minetest-mods |
| 17:20 |
|
Wuzzy joined #minetest-mods |
| 20:08 |
|
Miner_48er joined #minetest-mods |
| 21:12 |
|
PilzAdam joined #minetest-mods |
| 23:19 |
|
Miner_48er joined #minetest-mods |
