Time |
Nick |
Message |
04:01 |
|
Taoki joined #minetest-dev |
05:59 |
|
mizux joined #minetest-dev |
08:00 |
|
ShadowNinja joined #minetest-dev |
08:50 |
|
calcul0n joined #minetest-dev |
09:07 |
|
proller joined #minetest-dev |
09:45 |
|
calcul0n_ joined #minetest-dev |
10:27 |
|
Fixer joined #minetest-dev |
14:06 |
|
twoelk joined #minetest-dev |
15:44 |
|
Shara_ joined #minetest-dev |
16:30 |
|
Taoki joined #minetest-dev |
16:34 |
|
twoelk left #minetest-dev |
17:05 |
|
Jordach joined #minetest-dev |
17:28 |
|
homthack joined #minetest-dev |
19:09 |
Krock |
will merge #10353 in 10 minutes |
19:09 |
ShadowBot |
https://github.com/minetest/minetest/issues/10353 -- Inventory: Protect Craft and Drop actions by SmallJoker |
19:11 |
Krock |
does #10340 need adoption to properly implement the checks? |
19:11 |
ShadowBot |
https://github.com/minetest/minetest/issues/10340 -- Patch fast/teleport vulnerability when attached to an entity by EliasFleckenstein03 |
19:13 |
sfan5 |
dunno but could be done |
19:18 |
Krock |
5.4.0 in december? interesting. |
19:18 |
Krock |
merging |
19:48 |
clavi |
MTG requires the same or higher MT version to run, right? |
19:49 |
Krock |
development MTG needs development engine |
19:49 |
clavi |
sure, but what about say MT 5.2 with MTG 5.3 |
19:50 |
Krock |
might not work, but could. |
19:50 |
clavi |
in my experience it often doesn't |
19:50 |
clavi |
but I just wanted to confirm that this is expected, not something I did wrong |
19:51 |
clavi |
what about new Minetest version with old, or even very old Minetest Game? |
19:52 |
Krock |
old MTG versions generally work better, but they'll lack some features and bugfiyes |
19:52 |
clavi |
could an old MTG version use some engine function that's not there anymore in a new MT and lead to bugs? |
19:53 |
Krock |
Minetest Game is just a bunch of mods, and Minetest has to ensure those have to work for quite a while. No worries there. |
19:54 |
clavi |
okay, thanks |
19:54 |
Krock |
!next |
19:54 |
ShadowBot |
Another satisfied customer. Next! |
20:00 |
MTDiscord |
<Warr1024> Old MTG versions (or versions of anything really) might depend on API features that have been deprecated or even removed. That's probably the biggest risk in trying to use old mod code with newer engines. |
20:01 |
Krock |
I'm assuming we're talking about 5.0.0 until master. wouldn't recommend older versions for security and bug reasons |
20:08 |
|
fluxflux joined #minetest-dev |
20:35 |
sfan5 |
or old mtg versions might have a bug that only breaks with new engine versions |
20:35 |
sfan5 |
like the recent collision info thing with item entities |
21:31 |
|
Lone_Wolf joined #minetest-dev |
21:35 |
MTDiscord |
<appguru> Would like to get an experimental version of #9907 into 5.4 - would identifier sanitation be enough for you? |
21:35 |
ShadowBot |
https://github.com/minetest/minetest/issues/9907 -- Shaders as media files (server-sent shaders) by appgurueu |
21:38 |
sfan5 |
"identifier sanitation"? |
21:39 |
MTDiscord |
<appguru> basically not allowing long identifiers (probably sanitizing them by replacing them with shorter ones) because of bugs on older graphics stacks |
21:40 |
MTDiscord |
<appguru> "The shader section states clearly that shaders themselves are not the problem, you just need to sanitize identifiers to prevent tripping potential bugs in the compiler. This can be as simple as rejecting or mangling alphanumeric blobs longer than a certain length." - hecktest |
21:44 |
MTDiscord |
<Warr1024> Make sure your identifier sanitizer is at least 70% alcohol |
22:23 |
|
T4im joined #minetest-dev |
22:29 |
|
homthack joined #minetest-dev |
23:21 |
|
Fixer joined #minetest-dev |