ghost
commented
9 years ago (First off, apologies for that mess I just made, apparently my lack of sleep is affecting my ability to use drop-downs >.<)
Hey Rioforce. Thank you for bringing these up. You have very good points, and I hope I can address them.
Yeah, LUNI is very divided. I assume you have been told how that happened, and really the biggest reason why it is still that way is thanks to people holding grudges. I'm trying to attempt to get people to work together more, but there isn't a whole lot I can really do.
Uploading vanilla LU is a moot point. While I haven't dealt with the client much at all myself, I know that it's been stated a number of times that the client was 'patched' at the games closing so that it would no longer be able to function. Modifications were made to allow it to work again, then errors were corrected (namely sound files), and hence the client that is the most functional and actually closest to the original is now 'Nexus2'. I have had no problem whatsoever with getting stuff from Tim, I honestly think that he's just being villanized unjustly for one rash decision he made. Just my perspective though.
Such things are already available, a couple people have done Youtube videos for setup (the most used is probably by Self-Styled Mythran). This GitHub was really meant to be fro people coming from Tim's site (as that's who the founding members are, as well as that being the only real active place of public development), so i had figured that just getting the server itself to work independently from the source was beyond the scope of what should be included. However, being that I have already done this partially already, and I have probably made bad assumptions there, I'll try to add that in soon to the usage instructions.
All the code from 0.6.0 onward should be fully commented thanks to Jon002. Unreleased code (ie new code in the development version) might not be because of the fact that it is still a work in progress, but I do agree people should comment their additions as much as possible. The next step in my mind is for me to finish the Getting Started Wiki page (still working on that, I just haven't had the opportunity to finish), so that way it will be relatively easy for everyone to get the background, one of the hardest parts up until this point. I will be covering some of the basic structure of the server in a video tutorial I'll be including as well. I think it would be a good idea to have 'static' documentation, however it's just a matter of having someone willing to take the time to do it. I'll work on that if I have the chance, however I can't commit to it for a little while (a large issue LUNI has in my mind is developers who have time they can be constantly devote to the progress, most if not all of us are very busy with school, work, life, etc).
Priorities has been kinda a moot point so far, being that there isn't a ton of stuff to do until the RM is able to be implemented, something that anyone with much knowledge of the project knows about. it hasn't been done yet because no one a part of the public LUNI development has either had the time or the skill to set up the framework for it, however I do know that it is in the process of being completed (can't tell you when It'll be available as again there's issue of sporadic work being done thanks to busy schedules and whatnot, but it had made good progress and I'm hoping to try and pick up on some of the work once I get past insanity over the next couple weeks in school and get that to completion sooner).
Again, reviews are primarily an issue of actually having active developers. Anything I do I'll make sure to test, and I'll test anyone else's code that is or wishes to be pushed. At this point, it is really only Jon002 and I here, Jon having the most experience and thoroughly capable of reviewing his own code, and as for myself I'm the person here who is primarily active, though while I do have some knowledge I don't have a ton of experience. I imagine that code will only be pushed from development to release when a couple people have been able to verify it, and in fact I'll add that into the contributing guidelines when I have the chance.
Again, the community in itself is fractured between groups of people, and I would love to see everything join into one central place (and I've suggested it multiple times), however for that to really be effective, everyone would need to agree to work together. That would be quite the feat in and of itself, though I would love to see it happen.
Let me know if you have any further questions or thoughts.
jaller200
Timtech
CDFalcon
Caboose1543
This technically isn't a code issue, but it's a project issue. I'm rioforce, I have followed LUNIServer since it's beginnings, and I see that there are some major problems with it. I applaud you for getting this far in the project. However, I see this project being very divided. I don't really know your structure and system, but to me, it looks quite messy. I was chatting with some members of this in Skype, and learned quite a bit about this project.The problem with most projects is the lack of organization. I propose this plan:
First of all, you need to re-upload LU to your own host. A vanilla copy. No "Nexus2" or anything re-branded. Just the pure original LU game. Having to rely on TimTech for a copy of LEGO Universe is just ridiculous. (Personally, I don't trust downloading things from TimTech)
Second, you need to make simple, yet very specific tutorials on how to get the basics of Luniserver to run. If people can't run the Luniserver, the can't help.
Third, you need to document everything. I don't know if you have documented all of your code, but from here, it doesn't look like it (correct me if I'm wrong). Documentation needs to be more than code comments. It mus be PUBLIC documentation.
Fourth, outline the priorities of the project. You need to figure out what needs to be done first. Are NPCs more important than worlds? Is making a racetrack more important than multi-player? These are just examples. You need a PUBLIC outline.
You might already do this, but you need to review and test each and every pull request before merging it. You need to make sure it works and does not break things.
These are only outside observation. These are just some tips on how to organize. My brother went on Google and found tons of different Luniserver websites. I don't know if all of them are related to this project, but if they are, they need to be deleted and one central hub needs to be made. This central hub could be the wiki on this GitHub or and external website.
Correct me if I;m wrong on any of these points. I hope you can get this project working out, and maybe I can help out a bit (though, I don't know C++, so I cannot code anything). ;)