[5.0.0] Breaking change merged: Settable player collisionbox

[paramat]

This feature has been added to MT 0.4.16dev https://github.com/minetest/minetest/pull/6007
More details of the issues can be found here https://github.com/minetest/minetest/pull/2738
The MTGame PR that was also merged is https://github.com/minetest/minetest_game/pull/1785
This is a breaking change as part of 0.5.0 changes, as warned about in viewtopic.php?f=18&t=17929

The breaking commits are in MTEngine https://github.com/minetest/minetest/co ... 26e2a523ca
and in MTGame https://github.com/minetest/minetest_ga ... 2c506fd6a6

This breaks new server-old client and old server-new client compatibility. Using incompatible server and client causes players to be shifted vertically by 1 node.
Because there was also a change to the player model in MTGame you need to make sure to use the corresponding version of MTGame, it is not backwards-compatible over this change and can also cause a 1-node vertical player offset.
Also, any mod that provides a player model, such as armour mods, will need updating to remove the vertical 1-node offset, which has just been removed from the MTGame player model.

It is recommended you stay on a version of MT 0.4.16dev just before this change (21 July) until you update to 0.5.0 when it is released.

[Wuzzy]

Yes!

:D

[kaadmy]

Wheee!

[wilkgr76]

YESSSS :D

[azekill_DIABLO]

oh year!!

[paramat]

I forgot to mention: because there was also a change to the player model in MTGame you need to make sure to use the corresponding version of MTGame, it is not backwards-compatible over this change.
As there will now be other breaking changes (now is the ideal time to make any useful compatibility-breaking change) it is recommended you keep your servers, clients and MTGame all on versions before 21 July.

To be clear though, we are not dropping support for existing worlds, they will not be broken by moving to 0.5.0.

[BBmine]

No! Minetest is....ARGH! I might stay on 0.4.15 forever! 0.4.16 was when minetest started this BAD trend.

[wilkgr76]

"BAD trend" LMAO

You do realise that the network protocol coming in 0.5 is breaking compatibility with 0.4.x clients? I mean, it's not an issue if you constantly play singleplayer, but anytime you want to play online, you'll have to use a 0.5.x client.

Also, you don't seem to have backed up your statement at all. Do explain further, but in a place that is more appropriate, such as a PM or Hangouts. Thank you.

[firefox]

"BAD trend" LMAO

You do realise that the network protocol coming in 0.5 is breaking compatibility with 0.4.x clients? I mean, it's not an issue if you constantly play singleplayer, but anytime you want to play online, you'll have to use a 0.5.x client.

that should lock out all the WorldCraft, ExploreCraft, FreeCraft, BlockCraft, <insert random android app name here> from our servers, right?
yay~ :D

[wilkgr76]

Until they update their codebase. *sigh*

[v-rob]

Until they update their codebase. *sigh*

We delete all posts connected to breaking changes and don't tell anyone. (Devious laugh)

[Sires]

Until they update their codebase. *sigh*

We delete all posts connected to breaking changes and don't tell anyone. (Devious laugh)

Better, make a feature that locks the player from playing the game if he is using a copy client like "Multicraft, Blockcraft and stuff" and make a mod that checks if the player has this feature, if the player don't have, kick the player with the following reason: "You should have the MINETEST client to play, not a copy of it"

:)

**EDIT**
Woah my idea may work maybe if every server use this mod, we would only need to make the feature that checks the app name, bruh maybe not, they will create features with the same name and it won't work, but maybe it could be a client sided mod that the server sends to the play, that somehow checks the name of the app and sends it back to the server and the server kicks if it's a copy

[Sires]

Maybe a dumb question but, will lua mods be able to change the collisionbox?

[twoelk]

Maybe a dumb question but, will lua mods be able to change the collisionbox?

read pull 1785 from the link list from the first post?

[paramat]

This 'BAD trend' is called a major new version of MT, the same bad trend gave you lua modding when we moved from 0.3 to 0.4.

[philipbenr]

Some people will always find progress bad.

The devs wouldn't be changing it unless there was a legitimate reason to change, so its for the best I'm sure (I haven't read the change-notes myself yet)

[azekill_DIABLO]

Some people will always find progress bad.

Yeah, but sometimes they just shouldn't talk of it. No but really this is SUPER useful! We can finally do morphing mods!