Minetest logo

IRC log for #minetest-dev, 2018-07-12

| Channels | #minetest-dev index | Today | | Google Search | Plaintext

All times shown according to UTC.

Time Nick Message
00:00 entuland joined #minetest-dev
00:24 Cornelia joined #minetest-dev
00:41 Cornelia joined #minetest-dev
00:51 ManElevation joined #minetest-dev
00:51 ManElevation joined #minetest-dev
02:24 twoelk left #minetest-dev
02:56 rdococ joined #minetest-dev
03:15 shacharr joined #minetest-dev
04:07 ssieb joined #minetest-dev
04:40 rdococ joined #minetest-dev
06:55 nerzhul joined #minetest-dev
07:36 Icedream joined #minetest-dev
07:42 lhofhansl joined #minetest-dev
07:44 lhofhansl Going to merge #7542 in a few.
07:44 ShadowBot https://github.com/minetest/minetest/issues/7542 -- Reduce block load glitches by lhofhansl
07:55 lhofhansl Done
08:21 nerzhul joined #minetest-dev
09:13 proller joined #minetest-dev
09:27 ManElevation joined #minetest-dev
09:29 dok_ left #minetest-dev
10:17 proller joined #minetest-dev
10:48 proller joined #minetest-dev
10:48 Fixer joined #minetest-dev
10:48 entuland joined #minetest-dev
11:13 Fixer joined #minetest-dev
11:19 troller joined #minetest-dev
11:29 troller joined #minetest-dev
11:52 Darcidride joined #minetest-dev
12:31 cx384 joined #minetest-dev
12:40 ensonic joined #minetest-dev
12:58 troller joined #minetest-dev
13:11 AndroBuilder joined #minetest-dev
13:51 troller joined #minetest-dev
14:38 ANAND Does a TOSERVER_ packet need to be in the same index of both the serverCommandTable and the clientCommandFactoryTable?
14:39 ANAND i.e. Does the 0x.. matter?
15:22 antims joined #minetest-dev
15:27 Corvus_ joined #minetest-dev
15:44 troller joined #minetest-dev
16:20 ANAND Why are all packets in server.cpp initialized with a datasize (second param of NetworkPacket()) of 0?
16:21 ANAND Whereas packets in client.cpp have datasizes like 1 + sizeof(v3s16) * blocks.size(), 1 + 3 * sizeof(float), etc.
16:21 ANAND I'm assuming that datasize doesn't matter for server->client packets
16:29 ANAND I'll try to keep it simple. I'll implement server->client fov sending for now, as there no need for the client to send an packet to acknowledge the fov change
16:30 ANAND Maybe that would be useful when the server sends min max and default values; then client->server ack packet would actually inform the server of the fov the client has chosen
16:30 ANAND within the range
16:49 troller joined #minetest-dev
17:04 ANAND joined #minetest-dev
18:00 ssieb joined #minetest-dev
19:00 YuGiOhJCJ joined #minetest-dev
19:19 entuland joined #minetest-dev
19:54 ensonic joined #minetest-dev
20:06 ensonic joined #minetest-dev
20:09 proller__ joined #minetest-dev
20:14 AndroBuilder joined #minetest-dev
20:29 Fixer joined #minetest-dev
20:40 Fixer_ joined #minetest-dev
20:50 Gael-de-Sailly joined #minetest-dev
21:14 proller joined #minetest-dev
22:15 proller joined #minetest-dev
22:32 prawnsalad left #minetest-dev
23:09 troller joined #minetest-dev
23:21 paramat joined #minetest-dev
23:46 paramat game#2173 seems ready
23:46 ShadowBot https://github.com/minetest/minetest_game/issues/2173 -- add evergreen bush by TumeniNodes
23:51 paramat #7532 is now tested and ready
23:51 ShadowBot https://github.com/minetest/minetest/issues/7532 -- Mgvalleys: Make river depth variation and humidity drop optional by paramat

| Channels | #minetest-dev index | Today | | Google Search | Plaintext