Time |
Nick |
Message |
00:30 |
|
Soni joined #minetest-dev |
00:53 |
|
fluxionary joined #minetest-dev |
01:37 |
|
Baytuch joined #minetest-dev |
02:28 |
|
olliy joined #minetest-dev |
02:51 |
|
Baytuch joined #minetest-dev |
04:00 |
|
MTDiscord joined #minetest-dev |
05:07 |
|
calcul0n joined #minetest-dev |
05:17 |
|
Baytuch joined #minetest-dev |
05:41 |
|
YuGiOhJCJ joined #minetest-dev |
06:19 |
|
Alias joined #minetest-dev |
07:51 |
|
Baytuch joined #minetest-dev |
08:16 |
|
fluxionary joined #minetest-dev |
08:21 |
|
fluxionary joined #minetest-dev |
09:48 |
|
appguru joined #minetest-dev |
10:07 |
|
Taoki joined #minetest-dev |
10:15 |
|
HuguesRoss joined #minetest-dev |
10:17 |
appguru |
sfan5: Why the possible close? |
10:17 |
appguru |
This only fixes the other invalid screenshot resolutions |
10:18 |
appguru |
(which don't match the actual resolutions of the files behind the URLs) |
10:28 |
sfan5 |
well it doesn't make the valdiator happy |
10:29 |
sfan5 |
so I prefer just removing the attributes |
10:57 |
|
fluxionary joined #minetest-dev |
11:25 |
|
Baytuch joined #minetest-dev |
12:19 |
|
proller joined #minetest-dev |
13:36 |
|
Fixer joined #minetest-dev |
14:32 |
MTDiscord |
<luatic> https://github.com/hughsie/appstream-glib/issues/457#issuecomment-1208179863 |
14:50 |
|
lionkor joined #minetest-dev |
17:02 |
|
appguru joined #minetest-dev |
17:04 |
appguru |
"Is hp_max only respected since 5.6 or how did this happen?" - I don't know, probably; I haven't investigated this far. |
19:08 |
|
proller joined #minetest-dev |
19:33 |
fluxionary |
it's documented in the API that the "max value" of move_resistance and liquid_viscosity is 7, however many mods set it to somewhat higher values w/out problem, e.g. ethereal quicksand is 15. however, if you it to larger values, eventually it completely arrests all player motion. even higher*really weird* stuff starts happening |
19:34 |
fluxionary |
@ 96, it seems to put the player into a negative feedback cycle. at 255, it absolutely rockets the player in the direction of their movement |
20:12 |
|
kilbith joined #minetest-dev |
20:12 |
|
Baytuch joined #minetest-dev |
20:55 |
|
Pexin_ joined #minetest-dev |
20:55 |
|
ROllerozxa_ joined #minetest-dev |
20:56 |
|
Noisytoot joined #minetest-dev |
20:57 |
|
beanzilla_ joined #minetest-dev |
20:58 |
|
SoniEx2 joined #minetest-dev |
20:59 |
|
asdflkj1 joined #minetest-dev |
20:59 |
|
behalebabo_ joined #minetest-dev |
21:07 |
|
Taoki joined #minetest-dev |
21:09 |
|
proller joined #minetest-dev |
21:28 |
|
Evergreen joined #minetest-dev |
21:47 |
|
ShadowBot` joined #minetest-dev |
21:48 |
|
Sokomine_ joined #minetest-dev |
21:53 |
|
noodles[m]1 joined #minetest-dev |
21:59 |
|
cheapie_ joined #minetest-dev |
22:01 |
|
asdflkj1 joined #minetest-dev |
22:02 |
|
cranezhou joined #minetest-dev |
22:22 |
|
behalebabo joined #minetest-dev |
22:23 |
|
Fixer joined #minetest-dev |
22:26 |
|
behalebabo joined #minetest-dev |
22:34 |
|
panwolfram joined #minetest-dev |
23:18 |
Zughy[m] |
I was wondering, since 5.6.1 is happening anyway and we have 310 confirmed bugs, how about adding a few confirmed bugs in that milestone? Even one per core dev. Because issues are rising again (1k+) and this time there's nothing much I can do to tamper the situation |
23:19 |
Zughy[m] |
I don't know why I've said "tamper", I meant "contain" |
23:31 |
MTDiscord |
<Ronoaldo> I'm experiencing issues with the 5.6 server and Android clients... Server crashes when the player joins |
23:32 |
MTDiscord |
<Ronoaldo> I'll grab a proper stack trace but it happened in two servers already |