| Time |
Nick |
Message |
| 00:16 |
|
The4spaceconsts1 joined #luanti |
| 00:32 |
|
mrcheese joined #luanti |
| 00:36 |
|
tzenfore joined #luanti |
| 01:24 |
|
SFENCE joined #luanti |
| 01:31 |
|
illwieckz joined #luanti |
| 01:42 |
|
SFENCE joined #luanti |
| 02:25 |
|
SFENCE joined #luanti |
| 02:54 |
|
puzzlecheese left #luanti |
| 03:00 |
|
SFENCE joined #luanti |
| 03:06 |
|
Verticen joined #luanti |
| 03:27 |
|
tzenfore joined #luanti |
| 03:35 |
|
SFENCE joined #luanti |
| 04:10 |
|
SFENCE joined #luanti |
| 04:19 |
|
AliasStillTaken joined #luanti |
| 04:30 |
|
SFENCE joined #luanti |
| 05:00 |
|
MTDiscord joined #luanti |
| 05:02 |
|
SFENCE joined #luanti |
| 05:14 |
|
Spookan joined #luanti |
| 05:27 |
|
SFENCE joined #luanti |
| 05:43 |
|
SFENCE joined #luanti |
| 06:05 |
|
SFENCE joined #luanti |
| 06:16 |
|
BadGuyAlex joined #luanti |
| 06:19 |
|
SFENCE joined #luanti |
| 06:31 |
|
SFENCE joined #luanti |
| 06:45 |
|
SFENCE joined #luanti |
| 06:47 |
|
cmc2 joined #luanti |
| 07:01 |
|
FeXoR joined #luanti |
| 07:22 |
|
SFENCE joined #luanti |
| 07:48 |
|
SFENCE joined #luanti |
| 08:13 |
|
GNUHacker joined #luanti |
| 08:56 |
|
GNUHacker joined #luanti |
| 09:19 |
|
YuGiOhJCJ joined #luanti |
| 10:37 |
|
GNUHacker joined #luanti |
| 10:49 |
|
andycallisto joined #luanti |
| 11:10 |
|
imi joined #luanti |
| 11:37 |
|
Spookan joined #luanti |
| 12:52 |
|
The4spaceconsts joined #luanti |
| 13:04 |
|
tzenfore joined #luanti |
| 13:44 |
|
SFENCE joined #luanti |
| 13:45 |
|
PoochInquisitor joined #luanti |
| 15:06 |
|
SFENCE joined #luanti |
| 15:32 |
|
crazylad joined #luanti |
| 15:32 |
|
crazylad joined #luanti |
| 15:43 |
|
mmuller joined #luanti |
| 16:07 |
|
SFENCE joined #luanti |
| 16:09 |
|
pounce joined #luanti |
| 16:30 |
|
GNUHacker joined #luanti |
| 16:52 |
|
fling joined #luanti |
| 17:01 |
|
GNUHacker joined #luanti |
| 17:20 |
|
ireallyhateirc joined #luanti |
| 17:36 |
|
panwolfram joined #luanti |
| 17:52 |
|
[MatrxMT] joined #luanti |
| 18:03 |
|
ireallyhateirc joined #luanti |
| 18:04 |
|
jaca122 joined #luanti |
| 18:09 |
|
lumidify joined #luanti |
| 18:15 |
|
SwissalpS joined #luanti |
| 18:16 |
|
tzenfore joined #luanti |
| 18:16 |
|
Spookan joined #luanti |
| 18:17 |
SwissalpS |
are there any plans to allow entities to be light sources? |
| 18:18 |
sfan5 |
not really |
| 18:20 |
|
tzenfore joined #luanti |
| 18:21 |
|
GNUHacker joined #luanti |
| 18:27 |
|
Mantar joined #luanti |
| 18:27 |
|
Menchers joined #luanti |
| 18:43 |
|
izzyb joined #luanti |
| 18:44 |
|
GNUHacker joined #luanti |
| 19:06 |
SwissalpS |
OK. Too bad. |
| 19:09 |
|
GNUHacker joined #luanti |
| 19:14 |
|
GNUHacker joined #luanti |
| 19:27 |
|
GNUHacker joined #luanti |
| 19:30 |
|
GNUHacke` joined #luanti |
| 19:41 |
|
GNUHacke` joined #luanti |
| 19:46 |
|
crazylad joined #luanti |
| 19:46 |
|
crazylad joined #luanti |
| 20:12 |
|
mrkubax10 joined #luanti |
| 20:18 |
|
YuGiOhJCJ joined #luanti |
| 20:37 |
mrkubax10 |
Is it possible to allow usage of tool with wear in recipe? |
| 20:41 |
|
HuguesRoss joined #luanti |
| 20:43 |
|
GNUHacker joined #luanti |
| 20:43 |
Krock |
mrkubax10: the only special recipe that I know of is 2x the same tool to repair it |
| 20:43 |
Krock |
aside from that, I think you could use almost broken tools in recipes |
| 20:48 |
|
GNUHacker joined #luanti |
| 20:50 |
|
imi joined #luanti |
| 20:58 |
|
crazylad joined #luanti |
| 20:59 |
mrkubax10 |
Because the situation is that I have a tool that cannot break (on purpose) and would want to have an upgrade recipe, but if that tool was used before it can't be used in the recipe which is something I wouldn't want |
| 21:20 |
|
cmc2 joined #luanti |
| 22:13 |
calculon |
mrkubax10: maybe something you can do with register_on_craft() |
| 22:14 |
mrkubax10 |
but on_craft happens after the recipe was matched with the result |
| 22:15 |
calculon |
yes but you can change the result by returning another ItemStack |
| 22:16 |
mrkubax10 |
but I have the issue where nothing shows in result slot so it's not even getting there |
| 22:18 |
calculon |
mmh, so your recipe is wrong? |
| 22:18 |
calculon |
my idea is register a recipe upgrade+tool=new tool and check if it's ok in the handler, then change the result if it's not |
| 22:19 |
|
MTDiscord joined #luanti |
| 22:21 |
mrkubax10 |
the recipe is not wrong, in the situation when tool was never used it can be used in the recipe, but when it's used at least once it is not possible to use that particular item in the recipe as maybe there is some information in metadata that I'm not aware of |
| 22:23 |
calculon |
it could also be playing with register_craft_predict then |
| 22:23 |
mrkubax10 |
To make it simpler, let's say that you have a pickaxe and a recipe which allows you to craft something using that pickaxe. As long as it was never used to dig node you can put it in crafting grid and you will get the result, but when there is wear on pickaxe you can't anymore. This is what I'm trying to workaround to allow using tool with wear |
| 22:24 |
mrkubax10 |
craft_predict cannot modify the result |
| 22:24 |
calculon |
ah yes |
| 22:25 |
mrkubax10 |
it's not that I absolutely need this to work, just making sure if there isn't something that I missed |
| 22:26 |
calculon |
last thing i see is it's changing the item after the first use |
| 22:26 |
calculon |
like new_pick becoming worn_pick or something |
| 22:27 |
calculon |
modders can be very creative to workaround api limitations :) |
| 22:30 |
bgstack15 |
Perhaps you can perform this crafting at a special node, like a custom workbench? That way, it can check input inventory slot 1 and input inventory slot 2, and if the discovered tool has any wear, it will not produce/offer the final object. |
| 23:11 |
|
Thermoriax joined #luanti |
| 23:33 |
|
panwolfram joined #luanti |
| 23:57 |
|
sparky4 joined #luanti |
