Branch structure for feature improvements / bugfix? about devilution HOT 5 CLOSED

This had crossed my mind earlier today. I thought about making a branch for modding, so people can drop in code snippets of features they want. Having one for OpenGL and linux sounds reasonable too. Most of the major issues with Devilution have been resolved, so it won't be long off before the base code is good enough for porting.

from devilution.

Why not leave this particular github as diablo "as-is" and then either forks/branches/ or new githubs could be started with this as the basis for mods/improvements? This is a great resource for people wanting to work with the original executable (such as myself), and I'd just be worried about it getting mired in changes and being difficult to distinguish what is faithful to the stock Diablo code, and what is new.

from devilution.

@NiteKat - Given that there are currently 352 forks, we're already in this case. However I believe @galaxyhaxz has a particular goal of getting 'stock' Diablo code running on more modern libs (OpenGL, etc) for maximum platform support. For that and any core feature improvements (Rendering model changes, etc) I think a few standard branches on this repo would be a good idea personally.

from devilution.

Yes and yes. Devilution is a clean room reversal so I don't want to mix it with anything not in the original binary. It seems branches might start confusing people and seeing as we have 450 forks now...

Perhaps I'll start a projects page so we can document the needed changes for the time being, keeping it isolated from base project. Wine has thorough documentation on DirectX api -> OpenGL, so maybe we can start referencing the replacements with that.

from devilution.

https://github.com/diasurgical/devilution-plus-plus

from devilution.