Recently Browsing 0 members
No registered users viewing this page.
By Karan Singh
Life is Strange: Before the Storm Ep. 2 review: Lightning in a Bottle
by Gurkaran Singh
In almost every trilogy, the second part is the best. It doesn't have to set up the story like the first one and it doesn't have to worry about ending the series on a high note. Like a middle child, it can maintain mystery as well as have a certain sense of panache. (Of course, this has nothing to do with the fact that I'm a middle child. This is why I was highly anticipating the second episode of Life is Strange: Before the Storm. It did not disappoint.
**This review contains a few spoilers from the first episode. Reader discretion is advised.**
After Rachel burns down most of the flora in Arcadia Bay and screams bloody murder, she and Chloe are reprimanded by Blackwell's Principal Wells for having skipped school the previous day. This doesn't end well for Chloe. For Rachel, however, things turn out different. Her clean record saves her from suspension but, her actions may take away her role in The Tempest - the school play that's supposed to happen the same night. This also serves as a commentary on how prejudice can easily cloud our judgments. Everyone was willing to believe Chloe was the perpetrator without much evidence.
In any case, Chloe's "fate" in the meeting escalates into a heated argument with her mother and David, her mom's boyfriend who has announced that he is moving in with them. She feels as if everyone and everything that she's cared for is somehow betraying her. This leads her to act out and leave. She goes to the only place that she feels is still her own, the junkyard. Her relationship with her mother turns more strenuous and she never goes home for the rest of the episode. They do communicate via text messages throughout the game, though. Once at the junkyard, Chloe sees her father in another one of her dream-nightmare fugue-like states and is visibly distraught. There are many references and scenes of fire throughout the game, sometimes as the main focus and at others, in the background.
She is awakened by Rachel. Each of them pretends to be the other's therapist and, in turn, they grow closer to each other. Their relationship no longer feels rushed, even though they've known each other for no more than a few days.
Soon, Rachel has to leave for the play while Chloe has an appointment with her drug dealer, Frank Bowers who gives Chloe a "collection job". The job goes awry and Chloe is faced with a dilemma that will come back to haunt her in the next episode. Then, Chloe leaves for The Tempest. Backstage, we see a lot of events unfold that provide more dimensions to the supporting characters. Nathan Prescott - the reclusive "spoiled" brat, for instance - is seen fighting his own demons. He has to deal with his domineering father, the fear of living up to his last name all while dealing with bullies. This is an incredible development for the game. To show troubled people as not just the sum of their worst qualities, but as the product of their circumstances, is the biggest strength of this game.
Further events transpire to put Chloe on stage, acting in the play (with a little nudge from Rachel). Her sloppy acting was pretty much how I would expect her to do it. It was hella entertaining, though. Near the end of their scene, we see a real off-the-cuff moment shared by our two female protagonists, which turns into an indelible freeze-frame for their relationship.
Later, they end up at the Amber residence. This is also the first time that Chloe has a one-on-one with Rachel's parents who are, unsurprisingly, not fond of her. On being cornered, Chloe agrees to have dinner with the Ambers. The game ends on a bombshell of a cliff-hanger that stands to turn everything on its head. However, I was more interested in the conversations between Chloe, a rebel, and Mr. Amber, a "model" citizen. Their philosophies, prejudices, and hypocrisy provided a great commentary on what our society deems acceptable. Needless to say, I await episode three impatiently.
Animation, Gameplay, and Music
There isn't much to say in terms of animation or gameplay as the new episodes have barely touched on the formula that the original came up with. I do wish, however, that the facial expressions were a little better. I found the voice-over to be excellent, but facial expressions of the characters often undercut the emotion being portrayed.
One huge takeaway for me, though, would be the music. It's hauntingly beautiful and resonates with you. Music was my only complaint about the first episode, and I am glad that this episode improved upon it.
The amazing feature of this particular episode is that it delves deeper into other supporting characters. Rather than the one-dimensional personalities we are often presented within the media, we get to see the other side of the coin. Drew, for example, was shown as a jock and a bully in the first episode, but here we get to see him in a different light. His concern for his unemployed father as well as the overprotective nature of his love for his brother makes him more human than simply a caricature to further the plot of the game.
In two different instances, the episode reminds us that people are more than what they put on display. Frank, when talking about Drew, tells Chloe that "people are never just a type" and Samuel, the school groundskeeper, reiterates the same point later on in the game. Similarly, Nathan has his own struggle. His money or name doesn't make him immune to bullying or from an overbearing father. This episode was particularly exceptional for exploring these issues while at the same time moving the story forward. It doesn't feel forced or even uncomfortable. It just organically falls into place.
Life is Strange: Before the Storm is shaping up to be one of my favorite titles of the year. This episode improves on its predecessor in almost every way. While the first episode set up the story nicely, the second one brings more life to it. The moments between Rachel and Chloe feel natural instead of hastened. I was much more engaged in their dynamic. The pacing of the story is taut and the music perfectly complements it. It doesn't let you breathe and that makes it all the more exhilarating. Chloe and Rachel's bond in the game is admirable and the supporting cast gets more to do, which is a welcome change. It also sets up the third episode very nicely.
The series is poised to be an outstanding gaming experience. All I hope is that the third episode maintains the depth and music of this one and improves upon the facial animation, somehow. I completed Life is Strange: Before the Storm Episode 2 in about three hours without any major lags or glitches. It's a beautiful game and I highly recommend it. You can buy the game on the device of your choice:
Xbox One: Standard Edition ($16.99) / Deluxe Edition ($24.99) PlayStation 4: Standard Edition ($16.99) / Deluxe Edition ($24.99) PC (Steam): Standard Edition ($16.99) / Deluxe Edition ($24.99) PC (SE store): Standard Edition ($16.99) / Deluxe Edition ($24.99) Don't forget to follow us @NeowinGaming on Twitter for more gaming reviews!
Life is Strange: Before the Storm was reviewed on an Asus GL552VW with a copy provided by the publisher on Steam. The title was played with an Xbox One controller attached. Here are the specifications of the device:
Display: 15.6" 16:9 IPS FHD (1920x1080) non-touch OS: Windows 10, 64-bit RAM: 16GB Processor: Intel Core i7-6700HQ, ~ 2.60 GHz GPU: NVIDIA® GeForce® GTX 960M with 4GB GDDR5 VRAM
I was just reading this new study that suggests behaving immorally in games might make you morally sensitive in real life.
It got me to thinkin' about how much I dislike acting immorally or violently in a game when I am presented with the option to either choose a "good" or "bad" path. In Fallout, I try to do the right thing by the inhabitants of the wasteland. In Mass Effect, I preferred the paragon approach, only going back through the titles to play the renegade options to see how the story or characters played out (punching that journalist in the face in ME2 made me feel like a right jerk.).
In games where I have to kill people in order to progress the story I don't feel anything because they are simply obstacles which must be overcome in order to progress. If I don't shoot the Russian bad guys, blow up the rival drug cartel's hideout, or take down the gangsters hot on my trial in the streets I die or can't complete the game.
I threw up a quick poll for fun.
By Nick H.
Ok, time for a little backstory. If you don't want to read it, skip down to the bolded bit.
I started my current job back in October. I'm a helpdesk guy for a rather large company, catering to users around the world. It was a huge step up from my previous job, which only catered to three school campuses. Part of the reason for the position being available with this company is that it has been bought by a larger company, and so they needed the extra personnel to help with the migration process. While it wasn't explicitly pointed out, I took this to mean that once the system was together it would be the larger company's IT team that would take over complete control, basically ending my job. I was ok with that, since at the time I was unemployed so any job was fine. I imagined that this migration period would only be about one year, meaning that my contract would only be one year. Again, I was fine with that.
Skip forwards to today. I'm 10 months in to the contract, and the honeymoon period is well and truly over. Almost every aspect of this job is bad. I don't feel like I work in IT anymore, I feel more like a secretary. While I understand that paperwork is pretty much part of any job, the paperwork outweighs the computer work by something like 5:1. For every computer I touch, there is paperwork to be filled out. For every access request, there is more paperwork to be filled out. It's come to the point where my boss - in no uncertain terms - has sidelined me so that now all I deal with is access requests. This means that I'm in front of my computer almost all the time, and for every access request I handle...you guessed it, more paperwork.
The migration is a mess. I know that it isn't easy to plan such a thing, but there is almost zero communication between us and the other teams. I'm currently handling two ticketing systems, ours and theirs, in an attempt to smooth out the transition. Yeah, that's working well. Even my partner in the US is saying the same thing, the system is fundamentally flawed.
This is not what I got in to IT for. I enjoy working with computers, but I also enjoy interacting with clients. At my last job I genuinely enjoyed answering the phone and saying, "you know what, I'll just head over and meet you to explain what the issue is." While it's more difficult to have that interaction here (I can't exactly just hop over to Morocco to fix a PC) I'm no longer supposed to get involved with problems in the same building that I'm in. That becomes a job for any of the rest of the team.
I woke up this morning and trudged to work as usual. All the way along I was thinking, "why am I doing this?" And this hasn't been the first time that it's entered my mind. Today has been slightly different though, in that my mind came up with the idea of "I want a new job" and now I can't shake it. Obviously I'm going to talk to my boss when he comes back (2 weeks vacation when we were told that - due to the migration - we couldn't really do such a thing at this time) and tell him that either he puts me in to a more hands-on position or I'm out of here. But if that doesn't happen, I'm going to hand in my letter of resignation.
Purpose of this thread
As I mentioned before, I realise that very few jobs come without paperwork. And it's not that I'm unhappy with doing paperwork, so long as there is enough practical work involved to justify it. How does the paperwork : work ratio work out for everyone else?
Has anyone been in a similar situation in IT, being part of a migration process? How did it work for you?
Ignoring the "if you don't like it, change it" advice, do you think it's right that I'm considering packing it in? If you were in the above situation, what would you do?
Should I look for another job in IT, or should I try my hand at something else? If all else fails, I don't think I'd mind working in a bar for a short time, just while I figure my situation out.
If you've considered packing in your job before, how did you go about job hunting, and dealing with interviews? I'm still going to be with this company during that time, so my availability will obviously be limited.
Ok, I think that's it. Aside from anything else I needed to get it off my chest, and writing it down has cleared my head slightly which is a start. Any responses are welcome.
Is there is a way to remove a word from a Choices variable because I don't want my speech recognition to recognize the word anymore.