On the one hand, you want to get the community excited enough to join in, but on the other hand you don’t want to reveal so much that when the update is released people don’t see anything new. However, to do so would create an interesting dilemma. Ronin’s vision for Invasion was going to require involving a much larger segment of the community than Robotic Boogaloo ever touched upon. “It was really difficult at first to keep people working or to keep people motivated while not telling them the actual plan” This was a chance to bring together all of the major content-creating communities of Team Fortress 2, with everyone playing their part. He already had friends in the item creation community from his own work there. It’s worth noting that a lot of these plans were hatched before End of the Line was being considered for a community update. Cosmetics are a big part of TF2 and no update would be complete without them, but he wanted to sink his teeth into providing some actual playable content, maps. It was a cosmetics only update with the premise of robotising well-known and popular hats and it broke new ground as to what the community thought of as being possible.įor the Invasion update, Ronin wanted to take things to the next level. Robotic Boogaloo was the first update which was 100% planned and executed by the community. The Ronin (we’re going to call him just “Ronin” from now on) was the proverbial Man With the Plan. Even so, once you’ve convinced them to join in, you still have to keep them on track, keep everyone moving forwards, and try and keep them all together on a journey that has no definite end date or guaranteed reward. A project lead must not only be able to deliver content themselves, but persuade other people to join in making content with the distinct possibility that at the end all their hard work could be for naught. A project lead must do more than merely possess an idea. Anyone can have an idea and write it down, but an idea is just the beginning. Making a community update is a daunting task. In the event that it wasn’t accepted, the idea was to release the community’s work as a big fun weekend. There was never a guarantee from Valve that this update would be picked up and made real. Getting them on-side would prove to be a win-win for everyone since he now had some valuable connections and the outlines of a map or two to build on.
#Alien invasion tf2 series
By encouraging them to hold a series of seemingly innocent contests, such as the TF2 Maps “Mercs vs Aliens” summer mapping contest, he was able to source out some talented mappers. His first port of call was to the mapping community. He wanted there to be truly diverse content, maps, weapons and more. He wanted to see more than just another sleugh of cosmetic items though. The Ronin (the man who was to became the Overall Project Manager for this Invasion update) had missed out on Boogaloo but was determined to be involved with a project. With robots and zombies taken, there was a glaring void that Team Fortress 2 lacked from the first person shooter genre. Even before the finely ground metal flakes had floated gently to the floor, lovingly scraped from the latest in digital millinery, there were those who looked on with envious eyes. May of 2013 - Robotic Boogaloo was released, the first entirely community made Team Fortress 2 update. Now, for us all, it is too late they are among us. For more than two years they planned, they built their rockets, their suits, their weapons and their maps. Our faces lit from the false light of this game we love. Night after night we sat there glued to our screens. We’d like to share with you the project’s origin story as well as how the movie, the maps, and the items came about. Welcome to the official behind-the-update page for Invasion! It took many hours of blood, sweat, and tears to bring to fruition (the update, not this page).
0 kommentar(er)
