Time  Nick      Message
05:31 ANAND     FOV setting works! Yay! :D
05:31 ANAND     Now to add call-backs and update documentation...
06:18 ANAND     What is the purpose of RemotePlayer::m_dirty?
06:20 ANAND     All PlayerSAO::set* methods set m_dirty to true
06:20 ANAND     What is this var used for?
06:23 nerzhul   save
08:11 ANAND     Hmm... Which is a good place to save the current FOV of a client (sent by the server)? I was using PlayerSAO::m_fov all this time
08:12 ANAND     But apparently, it's also being used by TOSERVER_PLAYERPOS, which sets it to ClientMap::m_camera_fov (==M_PI)
08:16 ANAND     I'll try using RemotePlayer, since I'm already using LocalPlayer to store the server-sent FOV
09:06 ANAND     Similar to other functions, the get/set fov lua methods work with degrees. Should the server-set FOV be stored as radians or degrees?
09:06 ANAND     It is to be noted that camera.cpp expects fov in degrees
09:42 Krock     the fov setting is in degrees, camera uses degrees. zoom uses degrees. how's this a question after all?
09:44 ANAND     Just wanted to confirm, thanks
10:58 ANAND     Trivial PR: #7554
10:58 ShadowBot https://github.com/minetest/minetest/issues/7554 -- Check if player exists on use of /privs by ClobberXD
15:10 ANAND     Is it possible to get a Server object from RemotePlayer?
15:17 ANAND     nvm, it apparently isn't possible... :/
15:41 lhofhansl Hallo... Planning to merge #7551 soon.
15:41 ShadowBot https://github.com/minetest/minetest/issues/7551 -- Remove old (unnecessary) legacy client handling. by lhofhansl
15:41 lhofhansl #7548 should probably we backported to 0.4.x, agreed?
15:41 ShadowBot https://github.com/minetest/minetest/issues/7548 -- Ensure that legacy mode is correctly disabled. by lhofhansl
15:43 Krock     backporting means that it must be compatible with old 0.4.x clients and servers - and also that there will be another backport release
15:43 Krock     but yet there are no plans for such a release (yet?)
15:47 paramat   could start an issue to collect stuff for a future backport?
15:48 Krock     could start a discussion about the future developemnt?
15:50 paramat   can't see a point yet, we've only just released 0.4.17.1/2
15:51 Krock     notable to say that another backport release will cause more work than we might want
15:52 Krock     it's good enough if we can finish 5.0.0 next spring
15:53 Krock     surely, an earlier release date would be nice - there are yet some rather important bugs to fix (crashes & deleting worlds in Windows)
15:53 nerzhul   i think backporting is useless now. We need to release 0.5.0 at a moment
15:53 paramat   backport is low priority, leave until after 5.0.0 i feel
15:53 nerzhul   we have done two point releases in june, we really need to offer 5.0.0 to players
15:54 Krock     backport is pretty much useless if 5.0.0 is out. Android players will be thankful too
16:14 nerzhul   do we define a period for a such release ?
16:14 nerzhul   august ?
16:14 paramat   i've just learned that securing builtin is not needed until we have server-provided CSM, so not needed for 5.0.0
16:15 paramat   no setting a date is not a good idea, as we learned :)
16:17 Krock     preferably < 1 year since the last release
16:20 paramat   current blockers are: crashes, auth db, some android stuff
16:20 paramat   crashes being the main one
16:33 nerzhul   Krock, the last feature release is 0.4.16
16:33 nerzhul   for me 0.4.17 is not a user interesting release, it's just maintenance release
16:33 nerzhul   yes, authdb and android UX enhancements are in the way
16:34 nerzhul   i didn't see recent reports
17:29 paramat   there are some minor android bugs, plus android shaders which someone is trying to fix, else the option could be removed. but controls are ok now it seems
17:29 paramat   (apart from being too close to screen edge for some smartphones)
17:31 paramat   merging #7543 in 5 mins
17:31 ShadowBot https://github.com/minetest/minetest/issues/7543 -- Make player liquid speed independent of FPS by paramat
17:40 paramat   merging
17:43 paramat   merged
17:44 paramat   is there a way to 'not squash and merge' using the buttons on github?
17:52 Krock     rebase & merge?
18:29 paramat   yeah perhaps
18:34 lhofhansl Merging #7551 now
18:34 ShadowBot https://github.com/minetest/minetest/issues/7551 -- Remove old (unnecessary) legacy client handling. by lhofhansl
18:45 lhofhansl done
18:48 lhofhansl Have a look at #7555?
18:48 ShadowBot https://github.com/minetest/minetest/issues/7555 -- Reduce ABM checks. by lhofhansl
18:49 lhofhansl First step on avoiding too many ABM checks when no ABMs present on any of the node types of a block.
18:49 lhofhansl avoids most of the cache invalidation problem, but also leaves some further optimizations on the table.
18:55 paramat   hmm
19:02 paramat   comments required on #7531
19:03 ShadowBot https://github.com/minetest/minetest/issues/7531 -- Making mgv5 stable for 5.0.0: Alter default tunnel width
19:04 Krock     already tested mgv5 a little after I saw this issue the first time. the tunnels are indeed sometimes too tight
19:06 sofar     lhofhansl: nice, hope it works
21:30 paramat   game#2176 Shara
21:30 ShadowBot https://github.com/minetest/minetest_game/issues/2176 -- Default: Credit schematics and licence as media by paramat
21:44 paramat   merging that in 5 mins
21:51 paramat   merging
21:52 paramat   done
21:54 paramat   just thought about adding logs for emergent jungle trees ..
22:49 paramat   i think that would be fun so i'll do it