You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been playing for more than a decade, and since few years ago joined development of a game(CTF). Now as a game developer and also a player, there are many things I want/need in engine. But I always kept it back, as costs vs benefits are not clear for me. There re probably others like me.
If I have never touched engine code, how much effort will I have to put into implementing the feature I want and how do I realize if it would be a better to wait and hope someone else will implement it?
I have low level programming experience but not a C++ user. How does this ffect the decision? For feature X, how much C++ knowledge is required?
Same as above but without low level XP.
The engine has many different aspects, like db, networking, graphics, gui, etc. What background is needed for each?
How is the flow from submitting a PR till when it's merged?
The text was updated successfully, but these errors were encountered:
These things should probably be laid out more clearly but I'm not sure the blog is the right place for that. Blog posts are essentially mostly for "news", for events like releases, "this month / season in luanti" etc.; whereas such an overview of "how development works & how you can get involved" is more or less timeless (except for some occasional updates of course).
I think the proper place for this is the "get involved" section on the website which already has something like a barebones summary of it and some helpful pointers.
I've been playing for more than a decade, and since few years ago joined development of a game(CTF). Now as a game developer and also a player, there are many things I want/need in engine. But I always kept it back, as costs vs benefits are not clear for me. There re probably others like me.
The text was updated successfully, but these errors were encountered: