rpg maker mz does not work well with gitHub

[Patroso]

rpg maker mz does not work well with gitHub when two people upload and did not download stuff from the other person before uploading my own stuff does not save my system fix this because it does not encourage me to continue using this engine

 

[caethyril]

You might find this tutorial helpful:

Automatically pretty JSON files for clean git commit diffs using git hooks

(This tutorial and others are available in their original format here) Background: Git is a powerful Version Control System that keeps track of differences in files as well as facilitating collaboration between team members. This isn't a git tutorial, but a tutorial to address an annoyance...

forums.rpgmakerweb.com

 

[ATT_Turan]

fix this because it does not encourage me to continue using this engine

I'm pretty sure you saw zero things in MZ's feature list that said it would work well with GitHub. It's not on anyone to "fix this."

 

[Patroso]

I'm sorry, but I got a little nervous and annoyed, I had to catch up 30 minutes.
I had a bad day

 

[Trihan]

I'm not sure how MZ is unique in this regard. If you don't do a pull from your repository, you're not going to get any changes the other people have made. How were you expecting it to go otherwise?

 

[Andar]

@Patroso that has nothing to do with github but goes for all cloudservices, with only those cloudservices that support branching and versioning being usable at all, other cloudservices (those without versioning) will have a high chance of destroying your entire project on a failed sync.

That is why everyone here on the forum will tell you to never work directly in a cloudsync'ed folder, only work on local copies and manually upload them after closing the editor.

And that is nothing exclusive to MZ either, it has allways been the case for every program that uses databasing file access instead of direct file access - not only the makers (VXA, MV, MZ) but also programs like Microsoft Access, Filemaker and so on.
And those programs CANNOT use direct file saving because that would skyrocket RAM requirements and make saving require dozens of minutes for each save.

 

[AquaEcho]

I imagine the vast majority of RPG Maker users are solo devs so they didn't plan around team development features.