Egoboo Community Forum

This really captures the spirit of Egoboo for me; (I will of course consult the other developers but) I do think this should be the defining ink style for Egoboo . PM is coming soon. In the meantime: We can provide a dedicated asset repository for artists; I don't think GitHub is an optimal solution...

Announcement: As zefz suggested, we are on gitter https://gitter.im/egoboo . @pf Can you make a sidebar on the website with all contact information about the project or eventually make a "community" page on which the forum, gitter, github, sf and everything is listed? @zefz Can you post an...

@zefz thanks. AUTHORS is in the next commit.

I think at the build, the 32- vs. 64-Bit issues resolve themselves by using CMake.
I am not sure if Egoboo contains 32-Bit specific code though. I will mention this in the build system part of the roadmap, though.

Can someone assemble a list of names of all known former and current developers? I'd just put an AUTHORS file (similar to GNU projects) into the project's root directory listing all former and current contributors. The author can use his/her real name and/or a pseudonym. However, if he wants an E-Ma...

A first draft of a roadmap based on everything discussed so far can be found here:
https://github.com/egoboo/egoboo/wiki/Roadmap. Discuss

Nice; obviously pf can update the website. That is, let's definitly assemble the roadmap (I'm on it) and then we can summarize a post from the roadmap. Obviously I am not a native speaker which means, whatever i write up (i.e. the roadmap) should be proof read by a native speaker. I know that things...

If I can manage the repo, then I can also do the updates. So we have a issue/non-issue. I test the access using my normal tools (SourceTree) tomorrow, I think it will work out of course. At least I can sync by hand then. This is sufficient as I can then also get changes from the SF repo into the GH ...

There's nothing in the SourceForge git repo, it looks like we're have to push it by hand. The clone URL's description is "Override the checkout URL with an external one. This is useful if this repository is a mirror of another, canonical repository." Also I don't see a link to GitHub on o...

There is a link on the Egoboo project page to GitHub: https://sourceforge.net/projects/egoboo/ I've added a GIT repository to SourceForge here: https://sourceforge.net/p/egoboo/git/ref/master/ It is currently empty... Excellent solution. Basically we display the GitHub repo from SF? However, this i...

The note that development is going on on GitHub is still missing! There is a link but it is confusing to people what and where they should work on. Please get that done asap, we need more developers and/or attention as soon as possible without confusing potential developers. Basically do something l...

So hand's up. Who will be working on the GitHub version? If there are more people than just pf and me, then I delay further refactorings and work on CMake build files first. I provide a basic CMake file that works for Visual Studio and Code::Blocks systems and then the other devs add the necessary e...

The game logic can indeed be broken easily. We test a lot but in general: Can the old developers check the gameplay once in a while or browse the source code. So far, we have no such issues AS FAR AS WE CAN TELL. Eventually, try to take note how things *should* work and if you feel like something go...

Agree on enet vs. others and yes its hard (but are we here for boring standard tasks?). But i don't have the intention to do that myself at the moment. I want the source to be ready for other developers. Regarding the JSON/XML I have to say I have objections there; let me elaborate: first of all we ...

Porting to SDL2 and preferably C++11 would be major steps towards making this project more maintainable. A long standing problem with the Egoboo codebase has been that it is a complete spaghetti mess. And a lot of hacks for optimizations or portability.... A lot of code cleanup is severely needed t...

Hi bitnapper. we are developing on https://github.com/egoboo/egoboo. Fork it and if you have something to commit issue a pull request. Eventually we can attract more devs on GitHub than on SF. I am going to provide a roadmap as soon as possible. Currently, we fix bugs, convert the source code to C++...