Time  Nick       Message
07:14 sfan5      huh but did we even change anything?
10:11 [MatrxMT]  <Zughy> Apparently, because I had a user being able to go through a wall in 5.11-dev but not in 5.10 (it was the same wall)
11:01 sfan5      merging #15721, #15750, #15749 in 15m
11:01 pgimeno    https://github.com/luanti-org/luanti/pull/15721 -- Clamp client-sent movement speed control by appgurueu
11:01 pgimeno    https://github.com/luanti-org/luanti/pull/15750 -- Enable relative mouse mode on Android by sfan5
11:01 pgimeno    https://github.com/luanti-org/luanti/pull/15749 -- Revert "Prefer GL3 driver over legacy GL driver" by sfan5
14:35 MTDiscord  <luatic> we should get rid of SAnimatedMesh
14:37 MTDiscord  <luatic> also, something i noticed a lot: irrlicht does a lot of tagged unions at home, e.g. mesh types, but we have RTTI now so we can do safe downcasts & checks via dynamic_cast, and honestly much of it should probably be tackled by moving appropriate methods to the base interfaces and using dynamic dispatch properly
14:55 sfan5      it does a lot of "we have the STL at home" as well as "exceptions or rtti no thanks"
14:55 sfan5      anyway we could release an rc build today
15:06 MTDiscord  <luatic> i suppose so. i would still like to look at #15736 a bit, but it isn't critical enough that it requires delaying the rc.
15:06 pgimeno    https://github.com/luanti-org/luanti/pull/15736 -- Fix buggy behavior in parts of the main menu by siliconsniffer
17:18 wrrrzr     Maybe merge my pr in 5.11? https://github.com/luanti-org/luanti/pull/15517
17:18 wrrrzr     With bash completion
17:18 rubenwardy we're in feature freeze so can't merge any new features
17:19 wrrrzr     ok
17:19 wrrrzr     but why feature freeze?
17:20 MTDiscord  <luatic> wrrrzr: i mean realistically we also have to focus on other things
17:21 MTDiscord  <luatic> but i've been meaning to look at it, i just have to read a bit about bash completions first
17:21 MTDiscord  <luatic> "I think what we should do to further discourage doing version comparisons is to actually provide documentation on which protocol version maps to which engine version"
17:24 MTDiscord  <luatic> I recall the original suggestion also being the addition of APIs. Could a simple table that maps engine version names to protocol versions suffice? So modders could do something like client_proto_ver >= core.protocol_version["5.9"].
17:39 [MatrxMT]  <Zughy> Movement regression might be a false alarm, we'll see with 5.11 rc
17:55 sfan5      @luatic: sure