Ten Ton Hammer: The GM staff that you have on hand for the first stage of closed beta; can you talk a little bit about how they’ve been getting ready for closed beta?
Stew: They’ve been busy. Even our first stage of closed beta is, in relative terms, still a fairly small population. So we’re talking about roughly a thousand new players plus a thousand or so carryovers from our alpha program. So our staff isn’t huge on that side; we do have CMs, we actually brought on someone to take on a GM-specific role last January. So we’ve had someone getting fully up to speed, getting ingrained in the community, making sure they know the ins and outs of the game, since then.
We have some pretty nice tools that the developers have made for the GMs; not only in-game tools but also a website that’s only accessible inside the studio that’s just absolutely remarkable in terms of what you can do with it. For example: what should the statistics on this weapon be, when should people be leveling.? All of those sorts of things are data driven inside of our dev process, so there’s a website that provides a lot of that information plus shows a lot of the game in real time. So I can use our set of tools to see that you’re playing the game, see exactly where you are, all of those types of things. It’s an area that we’ve been staffing for, plus I think the developers have done a great job of anticipating what our needs will be.
Ten Ton Hammer: So would you say that the GM staff’s chief function so far has been the balancing angle, making sure weapons are doing the right amount of damage, that sort of thing?
Stew: At this stage a lot of what we’ve used our GMs for is to be an education point, honestly. In early stages of development, we haven’t had all of the mechanics in place, obviously, in terms of educating the players on what comes next. So a lot of it’s been kind of help in navigation to what’s ready to test, what’s not ready to test. We’ve had a couple folks playing that role to get more deeply ingrained in the community as well - understand what players’ issues are and be a voice back to us and say ‘Hey, an uprising is brewing in the community around xyz, and xyz might be a balance issue.
But on balance issues, to be perfectly honest, we listen to the feedback from our community but we’re pretty empirical on our choices there. We tend to rely much more on the statistics coming out of our gameplay rather than what people might be saying. What sometimes happens is that we have very good testers that do a very empirical study around things, and we’ll tend to listen to that kind of feedback. But balance is something we see in the numbers. Our tools give us some really cool analytics that come out of the gameplay right now.
Ten Ton Hammer: With these empirical studies and broader feedback, do you ever feel like you’re wrestling with players’ perceptions about how the game is, rather than what you’ve actually designed?
Stew: Absolutely. I don’t know if I would make a claim that we wrestle more than any other game, but I think that one of the things that makes our game stand out is that we’ve been very meticulous around the idea that there are “countermeasures” - if the robotics class has “x”, recon class should have a countermeasure for how to play x. What we see at times even through the alpha is that we release a change and there’s a day or two of “OMG, I can’t believe you did that!” And then if you just let it rest, the community finds that there are more than suitable counters. It just that you had to learn what the new countermeasures are, and you have to play well as a team.
So far, GMs have been tasked with guiding players and being player advocates to the dev team. |
We focus a lot of our internal testing on balancing. What we’re really trying to say is: when a player runs this tactic or equips these devices, is there a suitable counter to it, what level of teamwork is required, and is it realistic to expect that from our playerbase.
Ten Ton Hammer: Let’s talk a little bit about the unsung heroes of game development, the systems engineers. Can you talk at all about efforts to reduce lag and ping? Maybe it’s early to be talking about that kind of thing - is it something that you’ve had to address.
Stew: We’ve done a number of things in that area. Just from a systems and infrastructure standpoint, the basic mechanics of getting the servers up and running and efficiently engineered with all the right alerting so you know when there are problems, that’s a big job in and of itself, before you try to make it perform well. What we’ve done as of last February was form a partnership with Internap Network Services. Additionally, we have on-staff personnel dedicated to getting the infrastructure right.
What Internap has brought to the table - and we now have operations up in two of their data centers, one in North America, one in Europe - is a thrilling amount of network bandwidth and low latency. There’s always work to be done, things to tune, but I think we’ve been very happy from that side. We’ve made great progress even in the last two to three months in terms of getting additional infrastructure in place that we feel will help us scale our operations around the managing of operations around the servers more efficiently.
The place where we know we still have work to do, where we have some folks diligently working on now that a substantial amount of the feature set has gotten into testing, is on server side optimization. Our development staff is starting to spend a lot of time on client side optimization - making sure that we’re only using the CPU cycles and RAM that we need to, and keeping a very smooth player experience. I think on all those angles we still have work to do, but the good news is we have folks that are quite good on both the development side and the network side, so I’ve been pleased with the progress so far.
Ten Ton Hammer: It’s great to hear that optimization is getting some good attention this early in the testing process. I know it’s a busy week there and we wish you all kinds of luck with the first stage of Global Agenda closed beta testing.
Stew: Thanks a lot!
Comments
Post your comments »
Add your thoughts to the discussion! »