Lurker > Energy Surge

? Block annoys me. Sage was better.


---

The only reason lightning never strikes in the same place twice, is that the same place isn't there the second time.

GinsuVictim posted...

Energy Surge posted...

but then the industry crashed in '83 and video games weren't popular again until the resurgence a few years later.

We never slowed down on gaming during that period. They were putting out more than we could consume. From the late 70's forward, gaming never lost steam with its audience.

I'm not saying you didn't play lots of games back then. I'm just saying that gaming wasn't popular at that time. And an industry crash is pretty good evidence of the lack of popularity. But all of this arguing over when games became popular is a moot point.

To reiterate my post, I have to interpret what 'popular' means to correctly answer the poll. I don't regularly play games that are older than me but I do play older games. If I equate classic games to games older than me and popular games as games younger than me, exactly as the poll equates them, I can use the last response to accurately answer it.


---

The only reason lightning never strikes in the same place twice, is that the same place isn't there the second time.

I say if you're in your mid-30s (or older) you were born before games got popular. There was the initial video game popularity rise in the late 70s, but then the industry crashed in '83 and video games weren't popular again until the resurgence a few years later.

The problem is the poll ambiguously equates 'classic games' to 'games older than you.' This is an acceptable definition as modern games will eventually become classic games at some point. But it makes speaking about categories of responses more difficult. When one person says they were born before games got popular what they're referring to as popular or classic games may be different than what you consider popular or classic games. A twenty year old might very well refer to a game from '98 as a classic game. While a thirty year old would see the same game as much more modern than a game he grew up playing that was made in '88. But both games are the same age as the person considering them 'classic'.

The poll is also worded poorly as is normally the case. Therefore you need to creatively reason why you choose an answer that isn't entirely true but as close as possible to your actual response.

Do you regularly play games that are older than you?

No, I don't regularly play games older than me.

Yes, I love playing classic games on old systems

Well what do you mean by classic games? Are classic games games that are older than me as in what the question asked or games on older systems as in this response? I do love playing classic games, not necessarily on the old hardware. So maybe I should pick this response despite it being completely opposite of my true answer.

Sometimes, I'll play retro games now and then

Probably appropriate for me, I'll revisit old games every once in a while. So the frequency here is pretty accurate. But again are we talking my interpretation of retro or do we mean games that are strictly older than me?

Rarely, I've only played a couple of the classics

This might work too, I tend to play only a couple of old favorites when I play classic games. However these few classics are younger than me. And it isn't a rare occurrence for me to play these few titles.

No, I only play newer games on new systems

This negative response matches my response to the question, but the specific reason does not match my reason for not playing games older than me. I don't only play newer games. I will play older games, they're just not often older than me.

No, I was born before video games were popular

Wait a second, the question was about "games older than you" not "games older than the popular period of gaming". This is the only negative response that I don't play games older than me that most closely matches my reasons. I'll just have to assume they are allowing me to interpret when games got popular as I choose.

The classic old favorites I'll return to play are around 25 years old, which is younger than me. The poll is just missing, "No, I was born before all the old games I play." And the last response is the closest approximation.


---

The only reason lightning never strikes in the same place twice, is that the same place isn't there the second time.

A lot of one's I enjoy have already been mentioned in this topic. Portal, To The Moon, Kingdom Hearts, Mirror's Edge. Here's some of my other favorites that have gone unmentioned:

"Beyond the Bounds" - Zone of the Enders 2
I'm not as big a fan of Kiss Me Sunlight from the first game. But I do love the chanting music that plays on the menu in both games.

"Late Goodbye" - Max Payne 2
"Children of the Elder God" - Alan Wake
"Poet and the Muse" - Alan Wake
Basically anything Poets of the Fall is awesome.

All five songs from Transistor:
"We all Become"
"The Spine"
"In Circles"
"Signals"
"Paper Boats"
Plus the bonus song "She Shines" that was released after the game was out. I'm pretty sure they made it before the game but just didn't find a place to include it in the game. Either way it was made for the game.


---

The only reason lightning never strikes in the same place twice, is that the same place isn't there the second time.

SkynyrdRocker posted...

From what I understand, everyone killed prior to people evaporating will not come back. I saw that in a link. Meaning Loki, Gamora, and Vision

Why does everyone always forget Heimdall? He died like thirty seconds before Loki!

Also Gamora's not going to stay dead. She's too big of a character to be absent from GotG3.

They're going to say something like, she was killed by Thanos to acquire the Soul Stone and her soul is still there in the Infinity Stone. How did Thanos get the Soul Stone? He tosses Gamora off the cliff, big light show begins and he wakes up lying in a shallow lake of water below the mountain range. And he just has the Soul Stone in the gauntlet. What's the first thing Thanos sees after snapping? Before he even teleports away to recover from the injury Thor inflicted, he's in a empty place covered with shallow water. The younger child Gamora is there asking Thanos, "Did you do it?" and "What did it cost?" They may have to sacrifice someone else to get Gamora back from the Soul Stone, but she's definitely going to be back.


---

The only reason lightning never strikes in the same place twice, is that the same place isn't there the second time.

ReggieTheReckless posted...

im guessing this remembers you so it doesn't change when you go more than once?

because I got spared 10 times in row

It is written in javascript so you can view the source to see how it works. It uses a cookie. Looks like it expires in a year, May 3, 2019. So if you clear your cookies or open in a new private window it'll roll a new result for you.

I was slain about five or six times in a row repeatedly opening it in new private windows and then was spared twice in a row.

Looks like there was a button to clear the cookie that the developer used for testing and then commented out as it still is visible in the source code.

The Popo posted...

Should have made it a poll. Would be curious how close to 50% it turns out.

It uses the Math.random() method to generate a pseudo-random number from 0 inclusive up to but not including 1. Then the script checks to see if the value is less than 0.5, if true it prints you were slain, otherwise it prints you were spared. It will probably be close to 50%, but Math.random isn't the best source of random data, so I'm sure there will be some bias.


---

The only reason lightning never strikes in the same place twice, is that the same place isn't there the second time.

There was an error posting your message:
Your message text was blank - you need to enter text for your message


---

The only reason lightning never strikes in the same place twice, is that the same place isn't there the second time.

zebatov posted...

@Energy_Surge

I did the ones with the trees by the windmill. The last tree is the one I had to just try all the options on because I was getting frustrated not seeing anything on the branches. (Blacked out for Link, but I'm sure he'll get it right away.) If you do get that last tree on your own, let me know why the solution is what it is. Energy, if you know, maybe post it up for me and black it out. Thanks!

I'll explain the trees. As you learned from the earlier panels the tree diagram on the panel matches the layout of the tree in front of the panel. And the solution matches the apple location. On the panel before the last panel, you noticed that the branches of the tree in front of the panel didn't quite match up to the diagram. You had to look at that tree from the other side to get it to match the diagram.

Last tree panel however the tree doesn't match the panel at all, even if you look at it from a different direction. And there is no apple on the tree to show the solution! Well if you compare the diagram and the tree, there is exactly one fewer branches on the tree than the panel. And it appears like where there would be a branch it has broken off. The apple was on that branch and removed from the tree. For another hint, I think you can see the broken branch lying on a table on the other side of the gate the panel opens. And when you open the gate the apple is sliced and lying near the branch.

I also got stuck in the marshy area with the panels opposite each other. There are "l" and "---" shapes, and you need to surround them, but I can't because you can't overlap your line.

Yes, you need to surround them. But that one symbol in the middle is impossible to surround... If only it was next to an edge of the panel like those other two symbols...

I also couldn't get the panel with the triangle in it on the ground at the starting castle.

You'll see more of them strewn about the world. If you find another and succeed at solving, try to figure out why that is the solution and then test your hypothesis by going back to one you haven't solved. That's a lot about what this game is about. Discovering a solution and then determining why it is a solution until you understand the mechanic.


---

The only reason lightning never strikes in the same place twice, is that the same place isn't there the second time.

zebatov posted...

I'm stuck what seems relatively early on. There's a puzzle in a shack, or shed, full of plants along the coast you start at (beyond a grove) which requires you to isolate four different colours from each other by drawing lines around them. The difficulty is that you can't go back over a previously used square (where your line already exists) and the limited space you have.

Oh you're talking about the colors bunker. When you finally figure that one out, it feels so good. Unless you accidentally figure it out by luck. Though I suppose you could deduce the solution through trial and error. But there is a really easy solution you're just not realizing.

I don't want to cheat and look it up but if you get to it, let me know how you do.

I'd hate to spoil the ah-ha moment for you. What other parts of the island have you done? Early on there are a set of puzzles in an apple orchard that sort of teach you how you should be analyzing the really obtuse puzzles.

You can go anywhere you want from the start, as long as you can figure out the puzzles. They don't give any explanation as to what some of the shapes mean and you should never have to guess, although I did use the power of deduction to get by one puzzle and still didn't know why it was what it was.

Out of curiosity which one did you deduce?


---

The only reason lightning never strikes in the same place twice, is that the same place isn't there the second time.

I remember the rumor that Mew was under a truck.

But never heard of Yoshi being in the game.


---

The only reason lightning never strikes in the same place twice, is that the same place isn't there the second time.

Some decisions will affect things. But it is pretty minute differences.

A character might say something different to acknowledge how you handled their problem in the first game. The Enhanced Edition added a journal entry to explain how an optional romance ended between the games. Some decisions in Witcher 1 make you an enemy of a group, and that in turn will make dealing with that group more difficult in the second game. A couple characters can survive or die based on player decisions and their deaths will affect the next game. One doesn't actually show up, but you receive a message and package if they lived. (Oddly this character shows up in the third game even if you import saves where the character died from first game into the second game and then import that save into the third game.) The other character that can live or die by your hand can cause another character to challenge you in the second game.


---

The only reason lightning never strikes in the same place twice, is that the same place isn't there the second time.

I remember when that game originally came out. At the time I was more of console gamer. Family computer didn't have the capability to play the 3D games. I didn't play this game till years later when I purchased it on GOG.

It's actually an interesting asymmetric game, like StarCraft or Alien vs. Predator, where the different sides have vastly different mechanics. Except the game play is a third person strategy game, like Sacrifice or the Battlezone remake. You play one of the soldiers on the field but can build structures and units and research upgrades while ordering your units around you also play the action game.

There are three sides to this conflict and each has their own story campaign. These little alien soldier engineers crashed on this island and are trying to repair their spacecraft. They have jet packs and guns and seem like the technology race. There's this race of aquatic humanoids called the Sea Reapers. They use swords, bows and magic. And finally there is Kubuto which is just this giant that lives on the island. Since he's so large he plays like a monster eating units to regain health, perhaps a precursor to Evolve? He doesn't build bases like the other races but he can spawn smaller monsters to build up forces.

The base building wasn't really extensive. It was primarily a third-person action game. But you still had to control resources to win. I believe Shiny made this game, they also made Sacrifice which is also a fun third person RTS game. Oh, I just checked the developer Planet Moon was made up of former Shiny employees, which is probably why I thought it was a Shiny game.

I played a bit of the alien engineers campaign and it was entertaining, but didn't get far enough to play the other race's campaigns. I jumped into a multiplayer skirmish match as each of the other two races to try out their abilities. It is a very different and unique game. I will probably get back into it at some point. Parts of the interface felt like they hadn't aged well. I remember the map in the single player campaign didn't seem like it was working correctly. But I have no idea if you need a structure to get more map info or if a rendering issue due to the game being so old was causing it to look strange.


---

The only reason lightning never strikes in the same place twice, is that the same place isn't there the second time.

Cotton_Eye_Joe posted...

Why do games need "story mode"?
Shouldn't YouTube playthroughs suffice?

Cotton_Eye_Joe posted...

I should've said story difficulty.

When the story has branching paths, your choices can affect the story. If you watch someone else play it, their decisions affect the story not your decisions. "Story mode" difficulty lets people that aren't proficient at the combat experience the story with their decisions still controlling where the story goes. This way it remains an interactive game you play, instead of becoming a non-interactive movie you just watch.


---

The only reason lightning never strikes in the same place twice, is that the same place isn't there the second time.

This page talks about the different codes that appear on the cart's front sticker and which version they correspond to:
http://zeldaspeedruns.wikia.com/wiki/Version_Differences


---

The only reason lightning never strikes in the same place twice, is that the same place isn't there the second time.