renames rp_player to player_api, restores compatibility for most of its functions, updates the model files from MTG, adds mod crafting recipe compatibility code
Mods adding crafting recipes should add rp_crafting to optional dependencies.
mruncreative/Repixture:master into master
renames rp_player to player_api, restores compatibility for most of its functions, updates the model files from MTG, adds mod crafting recipe compatibility code
Mods adding crafting recipes should add rp_crafting to optional dependencies.
No. I want rp_player to remain since it adds new feature. I also reserve the right to add more and incompatible features in future. I do not want Repixture to be restricted by Minetest Game.
My idea is to add player_api as a wrapper instead.
Rejected.
BUT!
I am willing to accept a separate PR with the player model fixed.
I am also willing to accept a separate PR with the crafting compability layer.
(Sorry, I am very strict with what I allow in Repixture.)
I don't think you understood. I didn't take away rp_player. The mod is simply renamed to player_api and compatibility is restored. Your extensions are still there.
Being artificially incompatible doesn't help anyone.
There is a single mod that is rp_player specific
https://github.com/sfence/adaptation_modpack/blob/master/adaptation_repixture/init.lua
Easier to fix it up than to insist upon being incompatible with literally everything else.
Alright. I've named it back to rp_player. You can do compatibility stuff in the metatable function in player_api.lua if you change names of your functions and argument order to whatever you want.
Just noticed that "allow edits from maintainers" is turned off by default on this site. I've turned it on.
Now all compatibility stuff is done in the wrapper. See #190/files
In the meantime, I just did it myself (currently untested).
https://codeberg.org/Wuzzy/Repixture/src/branch/master/mods/player_api
I would like it more if each PR only has one feature, and not multiple features mixed. Makes reviews harder.
I have looked at this again. Here are my comments:
player_api compability layer (so it is no longer relevant in this PR)minetest.clear_craft. I think this function needs to be supportedAlright. Just fix the sitting height on your model's animation and close the pull request. You can copy the sitting height adjustments for the boats from this PR.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?