Time Nick Message 00:08 paramat your statement is untrue 00:24 MinetestBot 02[git] 04paramat -> 03minetest/minetest_game: README.txt files: Change 'LGPL 2.1' to 'LGPLv2.1+'. Remove 'WTFPL' 13689f0c5 https://git.io/fAT8h (152018-08-22T00:23:00Z) 01:40 librebob[m] like every issue/feature request on the github is met with 'this is too specialized' or 'minetest game is meant to be simple' 01:53 rubenwardy Forget Minetest Game, make your own 01:54 AlienCat :S 01:54 rubenwardy It's also only ever one maintainer that says that 01:55 rubenwardy Because there's basically only one 09:04 MinetestBot Krock: Aug-21 18:34 UTC i know see why we're getting v3f issues 11:19 loveaabb meow! 13:18 Krock <°((((-< 15:50 AspireMint Hello, can anyone help me? This one line mod doesnt work: minetest.register_node("test:test", {description = "TEST", drawtype = "normal", tiles = "test.png",}) it is as unknown node, no error message, nothing.. also when i punch it nothing happen. This: https://wiki.minetest.net/Unknown_Node says "When punched, an error message is shown with the itemstring of the block it actually represents." And looks like it is in minetest.registe 15:50 AspireMint red_nodes["test:test"] (returns table) 15:52 Krock hi. 15:52 Krock is it still the same issue as a few days ago? 15:52 AspireMint (oh, and yeah, 0.4.16) 15:52 Krock then is updating to 0.4.17.1 the first step to do 15:52 AspireMint Noooo 15:53 Krock maybe there was a tweak to fix a similar issue and we're basically hunting ghosts 15:53 AspireMint uh, okay, ill try 15:56 AspireMint still same, client 0.4.17 15:57 AspireMint 0.4.17.1* 16:00 Krock dump the item definition of test:test above the node registrations 16:00 Krock i.e. print(dump(core.registered_items["test:test"])) 16:05 AspireMint { tiles = "test.png", mod_origin = "test", type = "node", name = "test:test", drawtype = "normal", description = "TEST" } 16:08 Krock so you're registering it twice? 16:10 AspireMint no, if yes its MT fault x) 16:12 AspireMint made new world, enabled "test" mod with one line - registering that node 16:25 AspireMint ok, solved. Wiki page is outdated. This is not true : tiles — Specifies the textures used for the node's faces. It's an array (table) of either one or six elements. If only one texture is needed, it can be specified directly as a string instead of a table. 16:26 AspireMint tiles = "blahblah" results in unknown node, should be tiles = {"blahblah"} 16:27 AspireMint yay, but thanks anyway 16:32 scr267 Hi - Would anyone have any idea why I can't convert a bronze block back to ingots as a regular user, but an admin is able to do so? 16:32 scr267 sounds almost like a permission issue, but other blocks like steel and coal work just fine. 16:33 Krock crafting isn't bound to any permission except interact 16:34 Krock but I think the regular user already has got that priv to place nodes and open chests 16:34 scr267 Krock: yeah thats what I thought, I couldn't find anything about this... 16:35 Krock just to make sure. grant the user "interact" and use the very same crafting pattern 16:35 Krock also check for recipes which use a single bronze block to craft an unknown item. 16:36 scr267 in the crafting guide? 16:38 scr267 Krock: you are right, its not one of the recipes listed for a regular user... ill check the admin user 16:41 Krock AspireMint: right. So it wasn't an unknown node after all. F5 should also display the "test:test" node as pointed thing, which does not happen for unknown nodes 16:42 scr267 Krock: the Crafting guide shows that a steel ingot has 2 possible recipes, smelting and breaking up a block - but a bronze block in the same guide has only 1 recipe => smelting. Weird. 16:44 Krock wait what? the bronze block can be crafted by smelting? 16:45 scr267 no, sorry the bronze ingot... 16:45 scr267 I miswrote that 16:45 scr267 I think I may have found the problem - not sure yet, but I'm going to try something and come back. 16:52 scr267 nope that wasn't it... I had some modules from LOTT enabled by themselves... it didn't work well anyway so I disabled them. I wasn't using the subgame... In any case it did not solve this problem... really odd. 16:54 Krock ensure that you're using vanilla minetest_game 0.4.17 and a 0.4.17.1 client (or 5.0-dev). Maybe it's outdated 16:55 scr267 yeah im looking at the minetest_game modules right now too... problem is i'm using a custom compilation to add 'console' so... anyway ill double check that... thanks 17:01 scr267 Krock: is there a way I can specify the path of the sub-game to use? 17:02 Krock no. symlink? 17:06 * twoelk still dreams of configurable paths for data in minetest 17:40 scr267 Krock: So, I found that its definitely a mod causing that... now I just need to isolate it :) 17:55 scr267 For anyone reading this thread: https://github.com/minetest-mods/technic/issues/400 17:55 scr267 The issue I was experiencing was an intended technic_worldgen mod functionality. Bronze is an 'alloy' and therefore needs to be smelted in a furnace. 17:56 scr267 So the default 1 bronze block = 9 bronze ingot recipe no longer registers. 20:33 AspireMint is it possible to change inventory image on tool use? 20:33 sfan5 you can swap the item to a different one 20:33 sfan5 other than that, no 20:33 AspireMint :S thanks 20:39 MinetestBot 02[git] 04paramat -> 03minetest/minetest: Content tab: Fix clipped text in texture pack button (#7667) 1334f940d https://git.io/fAkAd (152018-08-22T20:36:56Z) 21:59 paramat erm, there are at least 2 active mtgame maintainers and several more. the other core devs also disapprove requests for being too specialised or too complex 22:02 paramat if a certain core dev considers many requests to be unsuitable then that is simply because in their opinion many requests are unsuitable. nothing to do with bias against new features. we have a long list of new stuff to add to mtgame and are working very hard to add them