SPQR Panda

Elite Contributor
  • Content count

  • Joined

  • Last visited

  • Days Won


SPQR Panda last won the day on March 23

SPQR Panda had the most liked content!


About SPQR Panda

Contact Methods

  • Website URL
  • Skype

Profile Information

  • Gender
  • Location

Profile Fields

  • Twitch.tv

Recent Profile Visitors

3579 profile views
  1. It really isn't arrogant to say, and it is for us to decide whether or not we want to release something that doesn't have something we consider extremely important. It's a moot point really, we are going to release it when we feel it is ready, and you berating us for not doing it sooner will not speed us up or do any good.
  2. Making it open source now allows people to have a branch of the code without even the most basic of network security (this isn't about passwords, those are kept safe), so no, it really can't be.
  3. I don't recall this ever being open source, and JC didn't address it in his post so I'm ? on that point. I've contributed and worked on multiple open source projects in the past, but the game engines specifically had one trend: they didn't go open source until it was relatively stable and after some basic design decisions were made. Intersect is stable-ish, but from version to version it is not, and that's an issue that needs to be worked on. Another major problem is structural design and consistent code form. The engine will be open sourced before either of them gets done, but there is one critical infrastructure change that is getting mostly completed before it goes open-source: networking. It's a exhausting to work on, and it has its tendrils everywhere. One of the most important changes that needs to be present before people start poking around is network security, which is what I've been working on. It, and the networking changes to minimize and modularize this code are important, and the latter changes are sweeping. You might disagree, but I was brought on way earlier in the development lifecycle than I was originally supposed to, specifically because I can do this stuff. There are programmers here that are just as good as me if not better, but this is the one domain where I end up being where everyone here goes to with questions, and I'm stressing to you that this has to be in place before anyone starts studying the code and learning from it -- or more importantly making derivations. Like JC said, this is more than just the game engine, especially for me. More or less none of the engines and games from this community or our related communities have any security whatsoever, and getting this network security in before people start branching Intersect is going to be one of few opportunities to get everyone on a more secure platform. If you think security doesn't matter, talk to Adobe. They can tell you all about what happens when "it doesn't matter".
  4. Editor: Only works on Windows, you can see if you can get it working on Wine or not but it's not a supported platform. Client and Server: Already cross-platform with one download (post Alpha), you do need to install Mono on Linux and OSX first though (you should not be running these through WINE or using winebottler for them).
  5. I think JC may have added something in where the first account that gets registered also gets the permission automatically. It certainly wouldn't happen on every user.
  6. Couple of questions: 1. Is the library in the same directory or the lib directory as the server executable? 2. What version of Ubuntu? 3. What directory are you launching the server from/with what command are you launching it?
  7. Presumably, but any data or modifications to the DB tables with a plugin could cause an issue or all of the extra data would be wiped when upgrading.
  8. Well the guide you linked is pretty close to being exactly what I see in your screenshot, so you'd follow its instructions. Also you could look at step 3 on this guide:
  9. Right now your protocol should be TCP.
  10. Copy in fresh language files for Beta 3.1?
  11. There really isn't a comprehensive guide? Like languages used for communication, there are comprehensive grammar and syntax guides, but ultimately if you want to learn to understand and speak you need to learn vocabulary for what you want to say. There's no comprehensive vocabulary guide for programming languages (outside of syntactical vocabulary), since it differs based on the libraries you are using. You need to learn base C# and LINQ syntax, both of which are best learned through using them while learning. Then there's an even more complex and not-comprehensively-covered-in-a-single-source, that being algorithms, design patterns and so forth. Given that you didn't specify a target for what you're trying to use C# for, all I can do is suggest to you once again, MSDN. It has all of the syntax information for base C# and LINQ, with plenty of examples. If you want something more specific you're going to have to name it.
  12. Looks like you have a bad language file.
  13. Can you reword the query? I can think of more than one meaning to this question and none of the answers are short.
  14. Changed Status to Duplicate
  15. This has already been posted and addressed.