I asked five original team members for some insight, Coen Neessen (Lead Game Design), El Drijver (Lead Game Design), Matthew Florianz (Audio Director), Michael Wolf Visser (Lead Quest and Content Designer) and Vincent Leeuw (Lead Content).
"...we were really keen on making the combat more action oriented and closer to an FPS rather then traditional MMORPGs"
First I wondered if the goal was to make a combat game within an amazing setting, or to make a piece of art with combat included? "We wanted to break away from the over used vanilla fantasy setting
," said Coen, "and we were really keen on making the combat more action oriented and closer to an FPS rather than traditional MMORPGs
." This system was also designed to reward a player's skill rather than invested time. And the art went hand-in-hand with the unusual combat. The "organic, dark fantasy, cloak and dagger style worked out great
," said El. I never thought of it that way, but that really describes the game well.
Sound can be just as important as the visuals, and Spellborn
has some of the most moody, immersive sounds you'll ever hear. To give Spellborn
a completely unique twist, pre-recorded sounds were always filtered and many layers usually made up a typical sound or soundtrack. Monsters and mobs were often voiced by members of the team, like the big brute below (voiced by Paul Kuijer):
Matthew provided some detail. "Good sound and music transforms your surroundings where bad sound will give the impression you are in a dry recording studio. To address the linearity of music and to fit it to the randomness of game play, many games will switch between a slow or a fast track depending on whether the player is exploring or fighting. The music for both "modes" still has to be created with an understanding for the randomness of how events unfold.
The team at Spellborn wasn't tiny, hovering around 50 people, but when faced with issues like losing talent to natural turnover, the team faced many problems that might not have affected a much larger team. "There are pros and cons to both large teams and small teams
." says Coen. "We definitely could have used more people to get all the content into the game, but working with this slightly understaffed team was nothing short of awesome
." Vince gave further detail: "A smaller team gets you to the people you need a bit quicker. At the same time you do miss a lot of "brute force," so in the end you always have to scale down ideas and designs. That said, I think we did some amazing things with such a small team
." It sounds like they were a tight bunch.