| sandywang5230 |
Inviato - 04/12/2015 : 02:39:16
I must say shooters are damned hard to make, and I guess a lot of people didn't get where they wanted to be in a week. "Hopefully it got them thinking... I hope indies will make more shooters." Note: To access chapter selection, click the fullscreen button or check out the video on the GDC Vault website Sometimes video Runeacape games are at their best when they offer a bit of a sadistic kick. Online Runeacape games prove that Runeacape players love griefing and inflicting harm on others, and they're not the only ones. Bennett Foddy, the creator of eccentric Flash Runeacape games QWOP and GIRP, claims that his favorite part of making Runeacape games is griefing the people who play them."And I think Runeacape players like being griefed too!" Foddy said during a presentation at this year's Independent Runeacape games Summit during GDC 2012 in San Francisco. "I think they like being confused as long as it's part of the Runeacape game. I think they like being humiliated as long as it's the developer or another Runeacape player who's humiliating them. And I think they like being frustrated, which is becoming almost a rare delicacy in gaming."He jokes, "You can get tea-bagged by a 13-year-old when you're playing Halo online, but it's reasonably rare for the Runeacape game developer to tea-bag the Runeacape player."Foddy's own Runeacape games go out of their way to manipulate, tease, and frustrate their Runeacape players. It might not seem fair, but that's the point. Foddy thinks more developers should grief their audience, since it can make their Runeacape games more interesting, and more fun.A full video of Foddy's session is now available for free, courtesy of the GDC Vault.Simply click on the play button above to start the video.More Free VideosIn addition to this unconventional session, the GDC Vault has added two extra free videos, covering the extensive localization of StarCraft II and a postmortem on Zynga's Indiana Jones Adventure World.In "StarCraft II - Carte Blanche Localization," Runeacape senior manager William Barnes details how the major studio ensured that StarCraft II was ready for its worldwide launch. Along the way, he shares some creative solutions for in-Runeacape game lip-synching, working with geometric text, and translating a Runeacape game to suit a variety of cultures and demographics. http://www.rsgoldshop.com GDC Vault free video Elsewhere, Zynga designer Seth Sivak offers a behind the scenes look at one of the social giant's latest releases in "Indiana Jones Adventure World: Making Core Runeacape gameplay for Everyone." Here, Sivak explains how Zynga designs its major social Runeacape games, and outlines some important challenges the Zynga Boston team faced and the lessons it learned along the way. GDC Vault free video About the GDC VaultIn addition to all of this free content, the GDC Vault also offers more than 300 additional lecture videos and hundreds of slide collections from GDC 2012 for GDC Vault subscribers. GDC 2012 All Access pass holders already have full access to GDC Vault, and interested parties can apply for the individual subscription Beta via a GDC Vault inquiry form.Group subscriptions are also available: Runeacape game-related schools and development studios who sign up for GDC Vault Studio Subscriptions can receive access for their entire office or company. More information on this option is available via an online demonstration, and interested parties can send an email to Gillian Crowley. In addition, current subscribers with access issues can contact GDC Vault admins.Be sure to keep an eye on GDC Vault for even more free content, as GDC organizers will also archive videos, audio, and slides from upcoming 2012 events like GDC Europe, GDC Online, and GDC China. To stay abreast of all the latest updates to GDC Vault, be sure to check out the news feed on the official GDC website, or subscribe to updates via Twitter, Facebook, or RSS. GDC and the GDC Vault are owned and operated by Gamasutra parent company UBM Technology. In this reprinted altdevblogaday opinion piece, Crytek's technical lead Jaewon Jung looks at how developers can encourage simple code even if it may slow their programmers down in the short term. For some time, I've had a thought that no source code is the best source code. Obviously it has no bugs and requires no maintenance. An ideal software!Then, with no source code, our product will be super-awesome, right? Of course, not. Because our product Runeacape game or whatever kind of software it may be must do something useful and no source code cannot do anything by its definition. Being useful including giving an enjoyable experience to users is raison d'etre of any software product or of any product, for that matter, I guess .Fight against the temptation to go easyFrom time to time, I mulled over how one can incentivize a short code or a refactoring that makes overall code shorter amp; simpler. A need for such incentives stems from the fact that a shorter code providing identical features, of course often requires both deeper consideration, unremitting diligence and courage and usually takes more time to accomplish.Let's suppose the task of implementing a feature A has been assigned to you because it was a highest priority among backlog items. While figuring out a best way to implement it, you found out some nasty feature duplication and unnecessarily complected part in relevant modules.Now, you have two choices. One is to finish the feature ASAP by working around or conforming to that bad code while soothing your guilt by telling yourself "Let's do the refactoring later," which more often than not never happens and get a recognition as a coding ninja. The other is to bite the bullet despite a short-term delay it may induce and do the right thing right away even with the risk of breaking some irrelevant part of the code.You might not be lauded right away as a super achiever rather can be blamed for missing the deadline or for a temporarily broken build feature , but in the long run this can save not only your time, but also your colleagues', whether they become aware of an insidious effect of your effort or not. |
|
|
