Showing posts with label writer. Show all posts
Showing posts with label writer. Show all posts

Thursday, December 19, 2019

Interactive Game Story Writer- Remote, Boke Technology Co., Ltd Company, Los Angeles, California

Boke Technology Ltd. is looking for talented writers and story tellers! Does this sound like you? 

You’ll be writing stories for our newest game Stories: Love and Choices. You’ll be working with our team of producers to delivery weekly quality content to our story-based app. Our ideal candidate writes stories with interesting characters and compelling narratives, is able to follow the established style and tone of our games

You’ll be using your imagination to write fantastical worlds filled with daring adventures, mysteries, romances and amazing characters, brought to life by your writing! Bring your world to life and share your stories with millions of other people! Join us if you have a passion for storytelling, writing intricate plots and sprinkling a dash of romance in the mix!

About the job:
  • Write new stories for our game Stories: love and choices
  • Create a new chapter every 1-2 weeks
  • Write compelling twists, plot lines and exclusive premium choices
  • Create intricate characters that the users will fall in love with
  • Play various interactive storytelling games, explore the target market and the demands of our target audience
 
About you:
  • 1+ years’ experience in writing for interactive storytelling games [MUST]
  • High level of proficiency in English
  • Ability to follow the established style of our games and adapt to the tone
  • A book lover, you love to read in your free time
  • A passionate gamer, especially games with developed narratives
Bonus points:
  • Previous experience in writing for story games/in the video game industry
 
If this sounds like your dream job, don’t hesitate to apply! Send us your CV and cover letter in English, as well as a sample of your writing to  storiesrecruit@boke.com


 We encourage you to download similar interactive games like Choices, Chapters and Episodes to have a feel of interactive game experience.  


Please send us a sample that will best showcase your ability to write for the game. If you have more than one relevant example, please don’t hesitate to send more!

How you match

Criteria provided by job poster

Skills

 Game Design 
    English
    Game Programming
    Storytelling
    Writing
Storytelling
  • Interactive Storytelling 
  •  Interactive Media
  • Thursday, October 27, 2016

    8 Questions That Improve Your Game's Narrative by Angel Leigh McCoy

    http://www.gamasutra.com/blogs/AngelLeighMcCoy/20161024/283602/8_Questions_That_Improve_Your_Games_Narrative.php

    8 Questions That Improve Your Game's Narrative
    by Angel Leigh McCoy on 10/24/16
     

    The following blog post, unless otherwise noted, was written by a member of Gamasutra’s community.
    The thoughts and opinions expressed are those of the writer and not Gamasutra or its parent company.

     
    Quips: Quick Tips for Game Narrative and Other Noodlings

    Creating narrative for a video game has similar challenging, frustrating, and fun elements as those you encounter when putting together a jigsaw puzzle. Both tasks require critical thinking and the ability to see the big picture as well as the details.

    Half the battle is learning how to evaluate each piece and determine where it belongs in the grand scheme of things. The following questions can help guide your narrative design toward stronger, more cohesive storytelling.

    Does it support and strengthen the brand?

    Every product has an identity that players and readers rely on. If a player is looking for a science fiction first-person shooter with mature situations, then they're going to look for a brand that has all those markings. They will then be surprised and disappointed if they start playing and learn that it's actually all about relationships and RPG-style interactions. Thus, it's important that your story support the brand.

    If you're completely unfamiliar with what brand identity is, the article "Defining Brand Identity" by Christy MacLeod has basic information on it. Read that first, then come back.
    At its core, the brand identity is a promise to players that you will deliver what you've said you will. As a narrative designer, it's your duty to support and strengthen the game's (and the company's) brand.

    Most existing companies will have well-established definitions of what their brand identity is both for the company and for the game itself. This may include a mission and/or value statement, the voice/tone of the game, and its look and feel. With games, the ESRB rating also plays a strong role in a game's identity. And, if you're starting to make your own game (hello, indie teams), one of the first things you'll want to do is determine and document your game's identity. Many of your decisions will be based on it.

    Does it make sense from a player's perspective?

    Sounds basic, right, but this is one of the most challenging aspects of game writing. You have to always put yourself in the mind (and heart) of the player. There's a phenomenon I like to call "writer omniscience syndrome" which describes the fact that a writer knows everything about the story and thus assumes everyone else does too.

    This, however, is never the case. Your readers and players do not know the whole picture, and so they may be confused by events that make perfect sense to you.

    How do you avoid this? Avoiding writer omniscience syndrome is a skill you develop over time, like a muscle, and it starts by exercising that muscle at every turn. Ask yourself, "Have I given the player all the information they need to understand what's happening here?"

    If your answer is "No," then you need to look into foreshadowing and lore delivery in prior content. Getting the set-up right is critical to a satisfying pay-off.

    Have you ever experienced writer omniscience syndrome? I'd love to hear about your experience in the comments below.

    Are the physics right?

    Every story has its own set of internal physics that determine how the world and its elements work. The two most important story physics are world dynamics and character motivations. If the tale you're telling in-game breaks the rules you set up previously, then you'd better be fully aware of it and know exactly why you're making that story choice.

    For example, in a science fiction world, interplanetary travel could be established as taking hundreds of years. If you choose to now say that your characters can teleport between planets, you must explain why they can now do this. If you can't explain it, then don't make the change.

    The same applies to character motivations. If one of your characters behaves out of character, then either fortify the behavior by building in a new motivation or modify the behavior to fit. When a character changes its motivation or methods in mid-stream, it pulls the player out of their suspension of disbelief and triggers their right-brain critic, and that is not immersive storytelling.

    TRAP: Many writers fall into the Shiny! trap. Don't be that writer. Your idea may be awesome, but examine it closely to see if it truly fits what you're trying to accomplish with your product.
    What other areas of storytelling have story physics that you should fortify?

    Can I make this story idea fit?

    Game companies are filled to brimming with passionate, creative people who are overflowing with great ideas. A large part of the narrative designer's job is taking someone's else's great idea and fit it into the narrative. Game design is collaborative at its heart.

    These ideas may come down from the director level, from the level designers, or from support teams like Art or Quality Assurance. Depending on the force of the passion behind the idea, you may find yourself working magic to weave an idea into the rest of the world and story.

    Straight up, this isn't always possible and you may have to explain why and see the excitement die from the eyes of your coworkers. (My least favorite part of the job.)

    When it is possible, then it's a puzzle that demands solving, and it will call on you to use your most creative and strategic muscles to make it not just work, but work smoothly. Your coworkers love it when their ideas become canon. It's your job to evaluate ideas and find ways for the best of them (or the one's forced on you by bigger fish) to fit into the story.

    Ever had to incorporate someone else's idea into a creative project? How did it go? Tell me about it in the comments.

    Is there a better way?

    Neurologist David Eagleman, host of the PBS show "The Brain," believes that the first idea you have may not be the best idea—and I agree with him based on my own anecdotal experience. The problem is that we're wired to grab the first thing that comes to mind, and often that originates with whatever pop culture we're enjoying at the moment, or whatever game we played most recently, or just whatever's foremost in our minds.

    The real trick—and challenge—is to stretch beyond that and really dig into your creativity for all the ideas, some of which may be better than your first one. Eagleman recommends that you not stop at the first idea, but force yourself make a list of ten ideas. I've also heard the advice to force yourself to come up with 100 ideas, but when I tried that it devolved quickly into the ridiculous. Ten seems a good number.

    Remember that you're the narrative designer and that means it's your responsibility to come up with the best ideas and then pitch them to others. If you had one idea, then others did too, and they're not trained—as you are—to look beyond the obvious for the extra cool option. You will have to walk them there yourself, by explaining and justifying why your idea is better.

    Let's talk about the lazy human brain!

    Is this plot necessary?

    In my job, I talk a lot about stages and spotlights. I view the game environment as the stage, and where you shine the spotlight defines the story you're telling. Many parts of the story will and should remain in the eaves, never making it into the spotlight. Learning to discriminate between what should get the spotlight and what shouldn't is another important narrative skill to hone.

    Any plot point you put in the spotlight should advance the story—no exceptions. There are no good digressions or detours in game narrative design because we don't have that much gas to go wandering around the countryside. The focus, and thus the spotlight, should be on the core through-line and any moments that strongly support that through-line.

    If you were the technician behind the spotlight, how would you choose where to shine it?

    Does the story moment ask questions we can't/won't answer?

    It's also important, when choosing what moments to spotlight, to consider the future. Does using this dialogue or introducing this item cause players to speculate and yearn for more? Great if you plan to pay it off! Boo, bad if you can't or won't. Players hate few things more than when the game teases them with something that they never get to experience.

    We call this "story debt." It's a debt that we creators owe players, and we should endeavor never to renege on that debt. Any game that is putting out multiple releases and advancing the story in each will undoubtedly create "story debt" by introducing plot lines that they won't pay off.

    This may happen because the people working on the game change, because tribal knowledge is lost over time, or because the team no longer has the bandwidth to pursue the storyline despite their best intentions.

    Narrative designers can learn to be vigilant and recognize these situations, evaluate the risk, and determine whether it's worth it. Is there a better way?

    Ever been saddened because an anticipated game story got dropped?

    Where is this going?

    "The past is already gone, the future is not yet here. There's only one moment for you to live, and that is the present moment." —Gautama Buddha.

    What Buddha said is true, unless you're a narrative designer and the future of your story is at stake.

    While it is true that the future cannot be set in stone until it becomes the present—and this is especially true with game design—it pays to have some idea of where the story will be going. This allows you to seed elements early on that you can pay off later to fans' delight.

    You don't need to know exactly what the destination will be, but you do need to have an idea what the next few story landmarks will be. Foreshadowing, as mentioned above, adds depth and clarity to your story. The more you know about the future of your story, the more control you have over foreshadowing.

    The best laid plans of mice and men (and women) often go awry, however, so you have to remain flexible. If a tree falls across the path you're on (or an asset doesn't get completed in time), you'll have to take a detour. It's this flexibility and practical use of all these questions that makes you a great narrative designer and allows you to create awesome experiences for your players.

    For the past 9 years, Angel McCoy has been a writer and narrative designer on the AAA MMO Guild Wars 2. In the past, she lent her creative skills to industry heavy-weights XBox.com,  Advanced Dungeons & Dragons, and White Wolf's World of Darkness

    In her spare time, she founded and serves as Creative Director for the indie game team at Games Omniverse. Her narrative toolbox is overflowing with lessons learned and shortcuts discovered, so she's sharing some of the best of them with you.

    Thursday, February 19, 2015

    Writing in Games: It’s Much More Than Narrative_Why some of the best writing has nothing to do with character or story. By Tim Biggs

    22 Jun 2014  Warning: This feature contains a minor spoiler for The Last of Us: Left Behind.

    Writing can make or break a game. It takes many forms - from dialogue to in-game literature, voiceovers or even scripted environmental events - but in almost all cases it aims to move the game along, distil complexity into something meaningful, give justifications for gameplay conceits and keep the player attached to the characters and scenarios through story.

    When it comes to pointing out ‘good writing’ in games though, we don’t always look to the examples that do these things best. More often than not we associate ‘good writing’ with well-crafted story content and entertaining text or dialogue, and while this obviously isn’t a negative thing in and of itself, it leaves room for the idea that there are games with great, skilful writing that we don’t think of as such because they aren’t literary or don’t tell a gripping story. So is there a problem with the way we evaluate the quality of writing in games?

    With the exception of pure narrative, writing in games must be function first; less to do with crafting a story and more to do with non-literary concerns like player retention and awareness.
     
    Often when we talk about writing, we refer to the bits between or on top of the gameplay, where the characters talk to one another or you read some text to gain exposition. Yet while that kind of writing is easier for us to identify and analyse (by looking for the indicators of quality we recognise from literature and other media), the more game-specific, more technical (and depending on the game, more vital) form of writing that takes place during and informs the gameplay can often be overlooked.

    With the exception of pure narrative (for example in a cutscene), writing in games must be function first, which is to say it’s less to do with crafting a story and more to do with non-literary concerns like player retention and awareness. Concerns like how does a player know the only way to exit the room is through a ladder in the roof? What does an AI character say to alert the player to incoming danger? How will the game explain to the player that a particular area is off-limits?

    Whether these concerns are addressed seamlessly depends almost entirely on the quality of the writing which, like most other art in games, is usually there to build part of the scaffolding as much as part of the pretty façade. For example having a character deliver a “no, this doesn’t go here” or a “just three more to go” or heaven forbid a “hey, listen” serves a gameplay purpose rather than a literary one, and so should be judged on whether that purpose is realised.


    Ride as fast as you like, you can't get away from Navi...

    Ride as fast as you like, you can't get away from Navi...

    Even if an offhand character remark gives you exactly the information you need at the right time to have things click into place and make you feel like a genius or a badass, such writing is unlikely to be called out as ‘good’, and I think it boils down to the fact that this kind of functional writing only really exists in video games.

    As a baseline, consider Naughty Dog's Uncharted trilogy and The Last of Us, which are generally very well regarded in terms of writing and storytelling. This can be seen most recently in The Last of Us Left Behind DLC, in which the narrative cleverly negotiates our familiarity with coming-of-age stories. 

    Although stories of this type tend to be predictable and hard to pull off owing to the sheer number of times they’ve been told, the characterisation and literary restraint in Left Behind allows an experience that feels exciting and surprising while still managing to convey something deeply universal. Had the characters been written more salaciously or more in line with traditional young love stories, the player would surely have anticipated this and the impact of Left Behind would have been undermined.


    Such a believable relationship.

    Such a believable relationship.

    Stories like these show that video games are just as capable of incredible storytelling as film and literature, but it’s plain to see that the cleverness and skill with which the game’s narrative aspects are handled are satisfying to us in all the ways we recognise from those purely narrative forms. We recognise them as hallmarks of good storytelling. So what about the cleverness and writing skills unique to video games as a form? For an example of that I’m going to jump to a game similar to The Last of Us in many ways, but also very different.
     
    The Gears of War games, not always regarded as having ‘good writing’ (“Never thought it would end like this, huh Maria!?”) make an interesting example in my argument that the way we measure writing quality in games might center the discussion mostly on the overtly artistic or narrative kind.

    Whether or not the story being told in the latest game - Judgment - was of a high quality in the traditional sense, the writing was exceptional. Take the declassified missions for example, which appeared in each chapter and offered an optional set of parameters to the player, increasing the challenge but also the reward.

    The parameters obviously had to be fun from a gameplay point of view, but their in-game justification required scenarios that made sense to that exact part of the narrative, could be left out entirely if the player so chose, and delivered a reasonable explanation for why visibility was suddenly limited or the mission had to be accomplished under a certain time constraint. In addition to this, voiceover had to be written that explained these ludicrous happenings from the perspective of one of the main characters, bringing in their own perspective and personality.

    In the end the player has an understanding of the option, the consequences and the story, and they’ve stayed immersed in the artifice of the game throughout. It’s a great (if not very subtle) example of games writing acting as the carpenter’s hammer rather than the novelist’s pen. While none of it hit you in the gut, brought a tear to your eye or made you gasp with an unexpected twist, it was good writing nonetheless.


    Turns out DudeBros can also be effective communicators!

    Turns out DudeBros can also be effective communicators too.

    Zooming in from the overarching scenario-type writing to the minute-to-minute experience kind, you can also see a vital role that’s easy to overlook. We’ve all had experiences where the entirety of what’s happening in a game fails to be communicated to us coherently, either because we haven’t grasped an important mechanic or are just not looking at it the intended way.

    Often in fast-paced action-heavy games where that doesn’t happen a lot (like Gears), it’s because your focus and understanding of the scenario is being shaped by mission directives or context-specific character speech. For all its malignment, “RAZOR HAIL” is a pretty stunningly effective thing for a character to scream at you if you need to be told “keep yourself covered from above at all times or you’ll be ripped to shreds”.

    Whether a particular game is built around mechanics or a story at its core (or both), the function of this seemingly incidental writing is to connect the player in their limited perspective to their place in the immediate scenario and the wider game world.

    A poorly written or communicated aspect of the game will break the player’s ability to experience the game as intended, even as the disruptive and unpredictable tendencies of the player will break any writer’s attempt to focus attention too absolutely or tell a story too linearly. Yet for all this, if the writing of a game is absolutely nailed the player will hardly even notice it’s there while they’re playing.

    It’s this unique relationship between players and game designers - each affecting the way the other creates and experiences - that makes the supporting writing in games so largely unlike the writing in any other media, and it’s why that writing is just as worthy and just as deserving of our analysis and attention as the more literary kind we tend to focus on. 
     IGN Logo


    Tim is a freelance writer based in Sydney. You can catch up with him on Twitter and why not join the whole IGN Australia team on Facebook?

    Wednesday, January 28, 2015

    Tips for Writers / Ubiblog Columns by Richard Dansky | Central Clancy Writer | on September 19, 2013 |

    http://blog.ubi.com/the-write-stuff-september-2013-advice-for-writers/

    Tips for WritersThe best resource you have as a writer is other writers.

    For those of us of a certain age (which is to say, those of us old enough to remember typewriters, buy music on vinyl in a non-ironic way, and have fond memories of non-CGI Transformers), the image of the lone writer holds a romantic appeal – one that’s definitely echoed in the wider audience. The idea of a solitary wordsmith – locked in a room with only a typewriter and a blank page – plays to a certain fantasy of the artist, and for some forms of writing there’s some merit to it.

    But even the most supposedly solitary forms of literary expression, be they novels or short stories or naughty limericks that include the word “Nantucket,” aren’t entirely solo efforts. There are editors involved. First readers. Copy editors. You get the idea. And that’s for forms that involve no other asset besides the words.
    And believe me, it’s a good thing to get those other folks involved.

    Most writers, in their more candid moments, will simultaneously admit to being their own worst critics and getting so wrapped up in what the writing should be that they can’t edit it properly. Having other eyes on your work is a tremendous help. Good readers and editors will mercilessly uncover the weak spots and the cheats in your narrative, will relentlessly expose places where you got stylistically lazy, and call out the places where you shortchanged the reader.

    Also, if you’re lucky, they’ll catch the typos.

    The trick is, of course, finding readers and editors who can do that for you, who can read what you’ve written and provide feedback that is not only not yours, but also actively useful.

    Which brings us, in a roundabout way, to games.

     

    Don’t Go It Alone

    For a long time, most game writers were solitary creatures, whether they wanted to be or not. The role of narrative in game design wasn’t necessarily highly regarded, and a dedicated writer was viewed as a luxury. The idea of two – or more – on a single project was mind-blowing in its extravagance.

    Good readers and editors will mercilessly uncover the weak spots and the cheats in your narrative [Digression: At the first Game Writers Conference, now the Game Narrative Summit, I walked into the conference room before Marc Laidlaw’s opening talk and my first thought as I scanned the room was My God, I’m not alone. Every other person I’ve talked to who was there that day has told me roughly the same story, often using the same words.]

    Which meant that when a writer wanted feedback on something they were doing, they weren’t getting it from writers.

    Now wait a minute, I can hear you saying. Most of the people who are going to play the game aren’t writers, so feedback from writers is kind of key there, Spartacus. And yes, that’s true – knowing that things are or aren’t working for an audience is vitally important. If a reader hates the protagonist, it doesn’t matter if they’ve memorized Strunk and White or not; that feedback is useful.

    But.

    What that feedback is not, is directed, which means it’s not necessarily phrased in a way that makes it actionable. I don’t like the main character is feedback; there’s a serious disconnect between the way you position your protagonist’s backstory and her diction in the dialog you’ve written is actionable.
    Let’s rewind a bit. Imagine you’re an artist and you’re showing someone your work. Their response, quite reasonably, is that they don’t like it and something’s wrong with the way the sky looks. Now, this is useful feedback insofar as itTips for Writers A)suggests that the project needs more work and B)calls out a rough area that could use some improvement. However, what that feedback is lacking is technical criticism, using the language of the visual arts. There’s nothing there about composition, about color, about tools – in short, it’s not couched in the professional context that would allow the artist to use it as a clearer roadmap to iteration and improvement.

    And just like art, or engineering, or any other discipline within game development, writing has its own professional and technical language. Here is where the romantic notion of creation-exclusively-through-inspiration breaks down; writing is first and foremost a craft, requiring sweat and iteration and technical skill.

    Like any other craft, it has techniques and best practices and standards, and the people best equipped to give feedback that addresses the needs of the craft are – wait for it – other writers. They do the job, they speak the language. And just as artists get valuable feedback from other artists, and engineers get better feedback on their code from other engineers, some of the most directed, useful feedback a writer can get will come from another writer.

    [This assumes, of course, that the writer in question is good at critique and isn’t a jerk. But for the sake of continued employment of all concerned, we’ll assume both.]

    I’ll confess, the first time I was put in the harness long-term with another writer (while working on Splinter Cell: Double Agent), it was a weird feeling. I’d gotten used to working alone, to the point where I wasn’t sure how to interact. I’m fairly certain Taras Stasiuk, the other writer in question, felt something similar. This was something new and different and challenging. (Which is writerese for What if they don’t like my stuff?)

     Then something weird happened. I passed Taras some of my stuff. He passed me some of his. He sent back comments on mine, which were very useful, and I sent him a few on his. I didn’t agree with all of his notes, but we discussed the places where we disagreed, which made me lay out why I’d made those choices and what they implied, and that led to some new discussions about where the characters were coming from, and before you knew it A)we had a great working dynamic and – this is the important part – B)the work was better. And I’ve relished having other writers to work with ever since.

    Writing is first and foremost a craft, requiring sweat and iteration and technical skillThis is, of course, old hat to folks who’ve worked in TV writers’ rooms or found that mythical beast, the useful writers’ group. But for too many writers out there, there isn’t or hasn’t been a professional peer they could turn to. That means learning to rely only on themselves, to set up perimeters around their work, and – after too many rounds of being told I would have done it this way, and you should totally add a few dinosaurs – learning to view feedback as not necessarily in the work’s best interest. Those are hard habits to break.

    They’re worth breaking, though, and that ultimately circles us around to the original premise, namely, that the best resource you have as a writer in games is other writers. Specifically, other writers who know and understand the sort of work you’re doing and who can give you the targeted feedback that will allow you to improve specific aspects of that work. So if you’re lucky enough to be on a team, or in a studio with multiple writers, then the best thing you can do is use them. Share your work, and let them share theirs with you.

    Because they’re the ones in the best position to give you specific feedback you can use to make your own writing better.
    the author
     
    Perhaps best known for his brief stint as the world’s leading authority on Denebian Slime Devils, Richard Dansky has been with Red Storm/Ubisoft since 1999. His first game was Shadow Watch and his most recent one is Splinter Cell Blacklist. In between he’s served on the advisory board for GDC’s Game Narrative Summit, helped found and develop the IGDA Game Writing SIG, and appeared on Gamasutra’s list of the top 20 game writers in 2009. He has also published six novels, one short fiction collection and a ton of tabletop RPG sourcebooks, which is why you should never tell him about your character. For a tantalizing taste of Dansky's inimitable insights, read his recurring column on the UbiBlog ("The Write Stuff") and follow him on Twitter: @RDansky

    Wednesday, October 2, 2013

    JOB: Video Game Writer

    https://www.elance.com/j/video-game-writer/47509588
    • Hourly Rate: Not Sure
    • Hrs/wk: Not Sure | Duration: Not Sure
    • Work View™ Payment Protection
    • U.S. freelancers must have W9
    Oakland, California, United States  

    Video game writer sought for a narrative-centric, dialog-driven video game. Game is Flash/web-based and is targeted toward literate adults.
    Candidates should be able to demonstrate skill (must provide samples) in crafting professional TV-level dramatic dialog and story lines. 

    Video game design experience is also a plus.
    The job requires the use of custom Adobe Air-based authoring tools (which will be provided) as well some free-to-download software tools. Candidates must be tech-comfortable enough to install Adobe Air runtime, other necessary software, to use a text editor, etc., and to deal with the gaming mechanics of our game.

    Candidate must also have native-speaker-level command of the English language.
     
    Job ID: 47509588