Lemnis Gate Uses Time Travel To Change Your Thinking About First-Person Shooters

For some competitive first-person shooter players, there’s a hill you can never seem to surmount. You might excel at planning and have an excellent sense of the game; you know how your opponents think and where they’ll be, and you know how to outsmart them. You carefully plan your ambush, lying in wait with a superior plan–but when you get your opponent in your sights, they overpower you with superior aim and twitch shooting skills. You might have superior planning, but in many FPS scenarios, fast reactions can and often do win the day.

In Lemnis Gate, though, your tactics are often much more important than your twitch skills. The competitive FPS combines the planning and execution of real-time strategy games with the on-the-ground play of a character-based shooter, creating a sort of turn-based FPS that values out-of-the-box planning and preparation.

Winning is all about timing in Lemnis Gate, which we quickly learned in our recent hour-long hands-on session with the game. The idea is that Lemnis Gate’s matches take place as a series of time loops, each spanning 25 seconds. When you take your turn, you dispatch a character onto the map to complete an objective–say, to grab an item and return it to a teleporter on your side of the map. You have 25 seconds to do that, and your turn ends. Your opponent then takes their turn, dropping a character into the same 25 seconds you just played; they see your character run out and do whatever it is you did on your turn, but they have the opportunity to grab the resource first or shoot your character, stopping them from accomplishing their goal. The 25-second time loop changes thanks to their actions, and then it’s your turn again. You might kill their character so that your character survives and grabs the objective, for example, changing the loop again.

Continue Reading at GameSpot

This post has been read 11 times!

0 0 votes
Article Rating
Like
Like Love Haha Wow Sad Angry
guest
Not Optional
Optional
0 Comments
Inline Feedbacks
View all comments