Building a Better Game
As a follow-up to last week's review of Neverwinter Nights and Shadows of Undrentide, below are three interviews Ron Powell conducted with a few of the people involved in the project.
During the course of researching Neverwinter Nights and Shadows of Undrentide, I had the opportunity to speak with the creator of Nordock, Marc Richter, and the gentleman who hosts the official server, Doug Rhea. Nordock is a persistent world (PW) mod to Neverwinter Nights. You can find more information about Nordock and its official servers at www.nordock.net.
Linux Journal: Can you tell me a little about yourself and the persistent world you've created?
Marc Richter: Sure thing. I'm 36 going on 14, married, have four kids and work as a computer support guy at Merck & Co. Nordock was meant [to be] a simple little hack and slash mod. I would host it on one box while not DMing mods for friends. Well, it turned out that people actually liked the silly thing, so I ended up building on it, much like a weed. Today, it runs on five official severs and countless others as the public release. Anyway, I've played computer games since 1979, and I've played on-line on and off since the late 80s. I got sucked into EverQuest back in 2001. Neverwinter Nights was my chance to own the keys, as it were, but many of the systems and other pieces definitely were inspired by my time in EQ and other MMORPGs (massive multiplayer on-line role playing games), such as Dark Age of Camelot, Anarchy Online, Diablo 2 and Gemstone on Genie.
LJ: Can you summarize the mod for me?
MR: The mod is meant to be run 24/7. People can come and go as they please, kill monsters, get treasure, explore dark and mysterious places and learn trade skills, some involving magic. The players can play multiple races, including the noble dwarfs, witty halflings, stoic humans, nasty drow and so on. There is a main quest that only a handful of people have been able to complete without major help, and this quest ties in all sorts of lore and quests and other things.
Nordock was the first persistent world to be released to the general public as an open-source mod. In other words, back in October , I released the mod to the world, with the offer for people to modify it, host it, do with it as they want. The public release has been updated along with the main mod, and it offers me a way to give back to the community, much like open-source programs in Linux.
LJ: What do you think sets your mod apart from the rest? What keeps players coming back for more?
MR: You know, that's a great question. I sometimes don't know. I suspect the sheer scale has something to do with it. In other words, the world is so big that you can get lost exploring. Also, the Drow provide a player-based foe and the chance for the folk who like that sort of thing to play a darker role. I also like to think that having the trade skill system gives folk some non-combat things to do, and recent addins, such as player housing, give folk more role playing opportunities. Plus, it's got a wicked cool home grown booze system for getting drunk. Ultimately, however, I got in at just the right time--people were hungry for an "EQ replacement". Other PWs weren't moving as fast, some for very good reasons. I had a community reach critical mass in [short] time. I don't ever forget that part, because there's a huge number of people behind the scenes who have contributed to Nordock throughout its life. Plus, my DM staff busts their butts to maintain a good environment for people to play in without being harassed. Quite frankly, I'm amazed at their dedication, so really, it does all come back to the community.
LJ: How long did it take to build the original base of Nordock?
MR: I built the original handful of zones in a night. From July to October, 2002, the module underwent a huge growth. Since that point, into March , various spurts occurred. Since the spring, areas have settled down and most development resources went into Nordock II: A Dawn of Heroes. At this point, Nordock is in "final bug squish" mode. In fact, tonight is the big wipe/consolidation. Nordock 1 will be relaunched on a big Linux server instead of being spread across three Windows boxen. That's funny, because Nordock began on my Mandrake box.
LJ: You use Linux?
MR: Yes, when I can. I actually got into Linux back in 1998. I put up a Web page to help folk get it [Linux] running on Thinkpad 600s, and I've used it at Merck when I can. In fact, I scored some major points with an in-house Web board that I set up in an afternoon using Linux/Apache/PHP stuff, so you might say that I'm fond of the Penguin.
LJ: If you could add one thing to NWN (either for playing or building), what would that be?
MR: Wow...so much has changed in the past year. Honestly, I would love to see a more robust server running the modules. The goofiest little bugs can take down the whole thing, and it's a bear to try and code around it. I'm just not that talented. So that would be the one thing, a truly rock solid server.
LJ: If you could give one bit of advice to a mod builder, what would that be?
MR: Make no areas greater than 16x16! Seriously, have some sort of vision and be willing to stick to it, even in the face of doubters and whiners. Listen to them, but don't be afraid to put your foot down. But the 16x16 thing is pretty important; see my prior point about server stability.
LJ: Any last words?
MR:I would like to thank BioWare for making a great game, my staff for really making Nordock shine and my wife and kids for tolerating living with a major game freak.
I also got to speak with the man behind the servers, Doug Rhea. He took a few minutes to tell us about running Nordock and NWN servers in general.
LJ: Can you define your role in the Nordock universe for me? How did you come to host the Nordock persistent world?
Doug Rhea: I always have been a gamer, since about 1977 when I started playing D&D. I began hosting BBS in 1980; later down the road I hosted Tribes, Tribes 2, Ultima Online, Diablo/Diablo2 and so on. When NWN came out, I loved the way it was supposed to work. I then searched for a good mod and came across Nordock, so I dropped the creator (Marc) a line and offered. He accepted and that was it.
LJ: Several servers were used in the beginning and they have merged. How many were there to start, and how many are there now?
DR: Actually, there was one in the beginning before I came along. About the time I got involved, they had moved to three servers--East, West, South. I picked up West and South rather quickly, East shortly after. The other hosts didn't have the hardware/bandwidth for a good server, and soon I had two Easts. Then, one of the previous hosts and also a scriptor decided to make Difficult, so for a while there were five servers: East, West, South, Difficult and Revenge. As of August 1st, only Nordock 1, Difficult and Revenge will be used. Revenge is my personal server.
LJ: Tell me about the hardware the servers run on and their operating systems. What made you choose this/these setup(s)? How much bandwidth do they take up? What would you consider to be a respectable minimum configuration for an NWN server?
DR: I have a number of servers, so here's the ones used for Nordock prior to the consolidation:
East - Dual Xeon 2.8GHz w/2GB RAM Windows 2000 Server
West - Dual Xeon 2.8GHz w/2GB RAM Windows 2000 Server
Revenge - Dual Xeon 2.8GHz w/2GB RAM Windows 2000 Server
Nordock 1, the new consolidated server, is a Dual Xeon 2.8GHz, w/2GB RAM on Mandrake Linux v9.x. I chose to use Windows 2000 because it was easier and had a graphical interface. Even on these power boxes, Nordock can run slow. The CPUs never go over 30% utilization, but it still lags. I would have to assume this is due to a sorry server application from BioWare, but we won't harp on that; it's better than any other game out there. It does run a bit better on Linux, but this mod is just plain big. NWN wasn't really designed for this type of mod, so we live with the lag and hope we can work around it in NaDoH.
Minimum requirements for a NWN server? Well, I started them on a Dual P3 1.4GHz with 1GB of RAM, and I would say that's the minimum. I would guess a P4 with at least 512MB of RAM would be fine, too. [Using] anything slower is asking for major lag if you have more than eight players.
The Windows server is a lot easier to handle at least for me--I am not a Linux guru. The Linux server does seem to help a bit with lag when there are more users, so Linux is the better of the two, though both have memory leak problems that BioWare needs to fix. I would love to see BioWare redo the Windows server and make something better, especially if it would take advantage of hyperthreading and multiple CPUs. Our new servers will all be Linux at some point, like Nordock 1. Currently the NaDoH server also is a Linux server. As for bandwidth, we have 3/3MBs here, dual T1s.
LJ: What distribution will you be using for the other servers? Mandrake?
DR: Mandrake for the NWN servers, because NWNX2 runs best on it or Debian. We run Red Hat on the Web/forums server that also handles the town criers.
Practical Task Scheduling Deployment
July 20, 2016 12:00 pm CDT
One of the best things about the UNIX environment (aside from being stable and efficient) is the vast array of software tools available to help you do your job. Traditionally, a UNIX tool does only one thing, but does that one thing very well. For example, grep is very easy to use and can search vast amounts of data quickly. The find tool can find a particular file or files based on all kinds of criteria. It's pretty easy to string these tools together to build even more powerful tools, such as a tool that finds all of the .log files in the /home directory and searches each one for a particular entry. This erector-set mentality allows UNIX system administrators to seem to always have the right tool for the job.
Cron traditionally has been considered another such a tool for job scheduling, but is it enough? This webinar considers that very question. The first part builds on a previous Geek Guide, Beyond Cron, and briefly describes how to know when it might be time to consider upgrading your job scheduling infrastructure. The second part presents an actual planning and implementation framework.
Join Linux Journal's Mike Diehl and Pat Cameron of Help Systems.
Free to Linux Journal readers.Register Now!
- Murat Yener and Onur Dundar's Expert Android Studio (Wrox)
- Tech Tip: Really Simple HTTP Server with Python
- SUSE LLC's SUSE Manager
- My +1 Sword of Productivity
- Non-Linux FOSS: Caffeine!
- Managing Linux Using Puppet
- Doing for User Space What We Did for Kernel Space
- Rogue Wave Software's Zend Server
- Parsing an RSS News Feed with a Bash Script
- Google's SwiftShader Released
With all the industry talk about the benefits of Linux on Power and all the performance advantages offered by its open architecture, you may be considering a move in that direction. If you are thinking about analytics, big data and cloud computing, you would be right to evaluate Power. The idea of using commodity x86 hardware and replacing it every three years is an outdated cost model. It doesn’t consider the total cost of ownership, and it doesn’t consider the advantage of real processing power, high-availability and multithreading like a demon.
This ebook takes a look at some of the practical applications of the Linux on Power platform and ways you might bring all the performance power of this open architecture to bear for your organization. There are no smoke and mirrors here—just hard, cold, empirical evidence provided by independent sources. I also consider some innovative ways Linux on Power will be used in the future.Get the Guide