Time Nick Message 09:34 RealBadAngel bump: #1278 09:34 ShadowBot https://github.com/minetest/minetest/issues/1278 -- Map irrlicht log level to minetest. Allow write irrlicht logs to debug file. by RealBadAngel 09:34 VanessaE morning RBA. 09:34 RealBadAngel hi VanessaE 09:36 RealBadAngel sapier, celeron55 if you can comment current code of above... 10:56 ^Enki^ Hello, I'd like to help with the localization but I'd prefer to start from zero instead of using already partially translated PO files; is there a "base" PO untranslated where to start from? Is it https://github.com/minetest/minetest/blob/master/po/minetest.pot ? 12:36 ivcho_ wath is user function for 12:37 ivcho_ wath is use function for 16:20 crazyR join ##landrush 16:20 crazyR oops 18:51 sapier RealBadAngel what do you think about adding a cmdline param "--console-loglevel=1|2|3" to replace quite,info,verbose? 18:52 sapier that's not meant as an requirement but as an idea to comment ;-) 20:30 BlockMen sapier, was not able to find any bug with hud now ;) 20:32 sapier well I usually don't find my own bugs so this isn't a surprise ;-) or did you want to say you haven't been able to find a new bug? 20:32 BlockMen but i noticed a "problem" when using replacing builtin hud. since you remove first the old bar and then add the new the id is always 0 or 1 (depending what bar you change). but that means its impossible for mods to add a "background" statbar because hud elements with higher ids are down above them 20:32 BlockMen ^ not a "bug" ;P 20:33 BlockMen *s/down/drawn 20:34 sapier hmmm no a mod should be able to add a background statbar by disabling builtin, adding it's own and reenable the builtin ... but I haven't tested this assumption 20:35 sapier I know that'd be a quite special way of doing, but as the request is quite special to I guess it'd be ok ;-) 20:35 sapier at least in case it really works 20:43 BlockMen sapier, its easy to "fix" by adding first the new hud and then deleting the old ;) 20:43 RealBadAngel sapier, well i had such idea too, but there are more switches affecting the logs like trace and speedtest 20:43 sapier ok, no problem it's just been an ide 20:43 sapier a 20:44 RealBadAngel so are you ok with the code now? 20:45 RealBadAngel btw good that you have insisted on mapping the levels, it turned out 1.7.3 and 1.8+ have different ones 20:46 RealBadAngel debug log level was introduced in 1.8 20:46 sapier It's a small fix, I haven't tested it now but I hope to verify it tomorrow 20:47 RealBadAngel btw, i have noticed one "bug" thanks to that patch 20:48 RealBadAngel action log "user placed node" and then facedir = nn 20:48 RealBadAngel text is in actionstream, but facedir goes propably into dstream directly 20:49 diemartin BlockMen, would help to add some kind of "priority" parameter to hud_add? 20:51 RealBadAngel so if console log level is set to quiet (errors only) that facedir message is still here 20:51 BlockMen kaeza, sure, that would work. but someone has to code it and to reach what i request its not necessary at all ;) 20:54 RealBadAngel oops, i meant param2 message, like this 20:54 RealBadAngel 22:53:45: ACTION[ServerThread]: facedir: 0 20:54 RealBadAngel param2 = 0 20:54 kaeza BlockMen, HUD item Z order is basically random because it's implemented as an array; deleting an item NULLs the array but does not shift other items, so gaps are created, then when you add a new item, the first "empty" slot is used 20:55 kaeza of course, first adding the bg then the other item solves it, but it would be useful to have this feature 20:56 kaeza or at least it was implemented that way when I added `offset' and `align' support :P 20:59 BlockMen kaeza, i wont stop you ;P 21:01 RealBadAngel what piece of code prints that "param2 = 0" ?? 21:01 RealBadAngel anybody knows? 21:01 RealBadAngel first is in item.lua, line 263 21:02 * kaeza installs Ubuntu on VBox 21:02 RealBadAngel it prints "facedir =" then the very same information is printed with "param2= " 21:02 RealBadAngel and i cant find where