Sometimes you design something and it seems like it is a good solution, efficient, easy to implement, and then there's the reality.
My system for updating entities across the network was based on a simple idea. Everybody who is interested in a particular area gets updates for all entities within that area. Sounds simple right? But here's the problem. The areas are relatively small, so entities move from area to area pretty quickly.
Each time an entity moves to a new area, it needs to be synchronized with everybody interested in that area, ie the game needs to send the full entity definition to the new guys. There are a couple ways to do that, one is to send everything to everybody, the other is to send full updates only to the new guys. I implemented the latter since it is more bandwidth-efficient, but it turned out to be pretty expensive anyway. Too expensive in fact, but not in the way you'd think.
I've been trying to get my camera simulation working. Last week, I realized that the network was misbehaving resulting in multi-second packet round trips. A week of optimization work, and that issue is resolved. Now I looked at the camera motion system I worked out, and I remember that in order for the simulation to be somewhat rational, that all of the servers need to have synchronized clocks.
I was going to try to soldier on with my camera work leaving time for later, but the problem is that I've already figured out most of the time synchronization issues this morning, and if I go back to the camera work, I have to figure that out, then when I come back to the time, figure the time out again. So the efficient solution for a single developer is to do time synchronization first, and put off the gratification of seeing the camera work.
I've been getting anxious about having a playable to show people. It is getting really close now, so this week I expected to be getting the code running to move the camera and synchronize it with the simulation server. But as I was getting that going, I was shocked to discover that a round trip from the client to the simulation server took
I never learned about C++ templates in school. I mostly learned Pascal. Then I went on to C and never really understood the need for templates when I started using C++ features. When I was working at EA, templates were effectively banned for game code, but I was encouraged to read programming books featuring templates which enabled me to finally understand their appeal. And it is strong.
When I went through school, I was taught that computer programs should recover gracefully from every possible error condition. That every function return should be checked, and that only through diligent use of nested error handling would reliable programs be built. As a result, the programs I have written have been largely error handling code, and not so much actual "do stuff" code.
I'm here to tell you, this is a complete waste of effort.
For the last couple of months I've been working on a distributed simulation server for my MMO. Breakthrough today, first units for the user loaded on the server displayed on the client. I've really got to get a more interesting model than that cube.
Every couple of years I mess up with my version control program and delete a bunch of stuff I didn't mean to. It's my own fault for not reading the dialog boxes thoroughly, and for deliberately not saving a backup copy before making the changes, but it still sucks. Yesterday while trying to roll back changes to three files, I accidentally rolled back the changes to the 20 or so other files I had made changes to over the previous two days. AAAAaaaaaaaaarrrrgggghhhhhh!
Ok, I feel better now. And I'm still a strong believer in version control. The ability to roll back changes and track changes over time is just too worthwhile not to do.
Just wanted to say, Greylisting works! I have some old email addresses that have been on my web pages for years. I typically get about 3,000 spam a week. I can see a difference when researchers take out a big spam botnet.
I installed PostGrey this week on my mail server, skeptical of the difference it would make, but wow. Wow! I now get about 30 spam a week. Fan-freaking-tastic!
I needed an account system for my MMO but I couldn't find much info on designing such a beast. Having figured out much of this on my own, cobbled together from stuff I read, I thought I'd put together an article on a few of the things I learned while building my login server, LoginD.
Disclaimer: I am not a security expert, so this system undoubtedly contains flaws. Take the information here as a starting point for your own design, or better yet, hire an expert.
Sounds awesome to me, i like the idea of NPC encounters/quests etc,one thing i found when i played was you are right once you build a base and get harvesters running etc, if noone is there to fight you kinda float about waiting. Dont know what you ...