Time |
Nick |
Message |
00:20 |
|
YuGiOhJCJ joined #minetest |
00:22 |
|
Sven_vB joined #minetest |
00:29 |
|
YuGiOhJCJ joined #minetest |
00:36 |
|
YuGiOhJCJ joined #minetest |
00:47 |
|
Soni joined #minetest |
01:04 |
fluxionary |
just to make sure, there's no limit on item IDs like there is for node IDs, right? |
01:04 |
MTDiscord |
<FatalError> I would imagine there is. |
01:05 |
fluxionary |
well, outside of general things like memory usage |
01:08 |
fluxionary |
i'm thinking about the framework for a tool enchanting system. the two existing tool enchanting systems use distinct item IDs, but they really should be using itemstack tool capabilities. but there's some things like "range" which might meaningfully affect the tool's capabilities, but which can't be customized per individual tool w/out new item ids |
01:09 |
fluxionary |
i'm wondering whether blowing up the # of item ids combinatorially really matters for anything practical. |
01:11 |
|
fling joined #minetest |
01:11 |
fluxionary |
there's also hacky things you can do w/ a variety of customized hands and monoids to control them, but i feel like that wouldn't feel as nice, particularly in laggy environments |
01:12 |
MTDiscord |
<FatalError> are you designing a mod or a game here |
01:12 |
MTDiscord |
<FatalError> because if you're making a game |
01:12 |
fluxionary |
hm. a framework? |
01:12 |
fluxionary |
which i suppose is somewhere in between |
01:12 |
|
fling joined #minetest |
01:12 |
MTDiscord |
<FatalError> a framework for a game? |
01:12 |
MTDiscord |
<FatalError> or a framework for a od |
01:12 |
MTDiscord |
<FatalError> mod* |
01:13 |
fluxionary |
it'd be a mod that's meant to be used as a library by other mods |
01:13 |
fluxionary |
though i haven't written any of it yet. |
01:13 |
MTDiscord |
<FatalError> ok, well you could always do something a bit more invasive |
01:14 |
fluxionary |
i'm currently working on a way of allowing players to tweak the behavior of the player's hand, and got to thinking about enchanting again |
01:14 |
MTDiscord |
<FatalError> you could re-register the on_use to basically use whatever range you want |
01:14 |
MTDiscord |
<FatalError> using raycast |
01:14 |
MTDiscord |
<FatalError> which is what on_use uses internally afaik |
01:14 |
fluxionary |
that sounds terrible |
01:15 |
fluxionary |
you wouldn't actually be "touching" the target node/object, it wouldn't be able to take advantage of any client-side predictions |
01:15 |
MTDiscord |
<FatalError> what |
01:15 |
fluxionary |
the range of a tool has hard-coded client-side behavior |
01:15 |
fluxionary |
which helps w/ immersion and stuff |
01:16 |
MTDiscord |
<FatalError> I mean, you could just put it at the maximum value it could be at |
01:16 |
fluxionary |
sure you could just swing your pick at the air *towards* some rocks, and use raycasting to find and break things, but you wouldn't know what you were actually aiming at |
01:16 |
fluxionary |
then you'd end up w/ the opposite problem. you think you're breaking something in the far distance but you're actually not |
01:17 |
fluxionary |
honestly things like "range" should be part of the "tool_capabilities" definition, but i'm not quite at the point where i want to actually propose changing such things |
01:17 |
fluxionary |
maybe i should |
01:24 |
fluxionary |
i suppose being able to set a custom range for a "node" also makes sense though... hm. |
02:10 |
MTDiscord |
<MisterE> attached is some log. Im trying to build minetest latest on manjaro linux (arch variation) its failing |
02:10 |
MTDiscord |
<MisterE> https://cdn.discordapp.com/attachments/749727888659447960/993337887720472586/Untitled_Document_1 |
04:00 |
|
MTDiscord joined #minetest |
04:04 |
|
cheapie joined #minetest |
04:07 |
|
erle joined #minetest |
04:15 |
|
fling joined #minetest |
04:26 |
|
Mc joined #minetest |
04:26 |
|
Mc joined #minetest |
04:27 |
|
JerryXiao joined #minetest |
04:29 |
|
fling joined #minetest |
04:37 |
|
BuckarooBanzai joined #minetest |
04:37 |
|
comrad joined #minetest |
04:38 |
|
Krock joined #minetest |
04:50 |
|
Verticen_ joined #minetest |
05:42 |
|
calcul0n joined #minetest |
05:45 |
|
calcul0n joined #minetest |
05:51 |
|
fling joined #minetest |
05:56 |
|
fling_ joined #minetest |
05:58 |
|
Lesha_Vel_ joined #minetest |
06:04 |
|
fling joined #minetest |
06:14 |
|
independent56 joined #minetest |
06:20 |
|
erle joined #minetest |
06:46 |
|
fling joined #minetest |
07:13 |
|
___nick___ joined #minetest |
07:49 |
|
Sven_vB joined #minetest |
08:00 |
|
fling joined #minetest |
08:03 |
sfan5 |
sounds like your build settings are messed up, `make clean && rm CMakeCache.txt` and try again |
08:05 |
|
fling joined #minetest |
08:54 |
|
better_sleeping[ joined #minetest |
09:18 |
|
specing_ joined #minetest |
09:25 |
|
independent56 joined #minetest |
09:27 |
|
independent56 joined #minetest |
10:01 |
|
independent56 joined #minetest |
10:09 |
|
calcul0n_ joined #minetest |
10:15 |
|
better_sleeping[ left #minetest |
11:08 |
|
independent56 joined #minetest |
11:12 |
|
appguru joined #minetest |
11:42 |
|
independent56 joined #minetest |
11:47 |
|
definitelya joined #minetest |
12:06 |
|
dabbill joined #minetest |
12:33 |
|
ronoaldo joined #minetest |
12:40 |
|
toluene joined #minetest |
12:51 |
|
erle joined #minetest |
13:07 |
|
proller joined #minetest |
13:08 |
|
Taoki joined #minetest |
13:36 |
Pexin |
12353, when bros get mad about math |
14:01 |
|
Fixer joined #minetest |
14:15 |
|
proller joined #minetest |
14:32 |
|
independent56 joined #minetest |
14:43 |
|
Sven_vB joined #minetest |
15:01 |
|
proller joined #minetest |
15:25 |
|
independent56 joined #minetest |
15:37 |
|
___nick___ joined #minetest |
15:39 |
|
___nick___ joined #minetest |
15:45 |
|
independent56 joined #minetest |
15:47 |
|
independent56 joined #minetest |
16:04 |
|
peterz joined #minetest |
16:05 |
|
independent56 joined #minetest |
16:08 |
|
peterz joined #minetest |
16:10 |
MTDiscord |
<MisterE> Hey, thx sfan5. It worked |
16:14 |
|
independent56 joined #minetest |
16:27 |
|
___nick___ joined #minetest |
16:41 |
|
sys4 joined #minetest |
16:53 |
|
independent56 joined #minetest |
17:13 |
|
Talkless joined #minetest |
17:19 |
|
debiankaios joined #minetest |
17:24 |
|
independent56 joined #minetest |
17:33 |
|
independent56 joined #minetest |
17:42 |
|
olliy joined #minetest |
18:09 |
|
independent56 joined #minetest |
18:14 |
|
Verticen_ joined #minetest |
18:17 |
|
independent56 joined #minetest |
18:31 |
|
independent56 joined #minetest |
18:52 |
|
independent56 joined #minetest |
19:17 |
|
proller joined #minetest |
19:19 |
|
panwolfram joined #minetest |
19:26 |
|
independent56 joined #minetest |
19:35 |
|
independent56 joined #minetest |
19:38 |
|
independent56 joined #minetest |
20:08 |
|
independent56 joined #minetest |
20:10 |
|
moth__ joined #minetest |
20:11 |
|
sys4 joined #minetest |
20:11 |
|
independent56 joined #minetest |
20:35 |
|
independent56 joined #minetest |
20:57 |
|
independent56 joined #minetest |
21:00 |
|
TheCoffeMaker joined #minetest |
21:05 |
|
independent56 joined #minetest |
21:18 |
|
specing_ joined #minetest |
21:20 |
|
behalebabo joined #minetest |
21:23 |
|
independent56 joined #minetest |
21:26 |
|
independent56 joined #minetest |
21:55 |
|
olliy1or joined #minetest |
21:59 |
|
Trifton__ joined #minetest |
22:01 |
|
Trifton_ joined #minetest |
22:02 |
|
Trifton_ joined #minetest |
22:02 |
|
Trifton_ joined #minetest |
22:02 |
|
Trifton_ joined #minetest |
22:08 |
|
fling joined #minetest |
22:09 |
|
independent56 joined #minetest |
22:20 |
|
fling joined #minetest |
22:21 |
|
independent56 joined #minetest |
22:28 |
|
independent56 joined #minetest |
22:34 |
|
panwolfram joined #minetest |
22:36 |
|
independent56 joined #minetest |
22:43 |
|
independent56 joined #minetest |
22:46 |
|
independent56 joined #minetest |
22:54 |
|
moth__ joined #minetest |
23:45 |
|
Lesha_Vel joined #minetest |