You accidentally kill an NPC and the game auto saves, F this game.

[Mr Fantastic]

.

[BippoErnesti]

For what it's worth, it doesn't affect your ability to 100% the game.

To resurrect Lincoln (guy trapped in Sylvan Temple), talk to Trine (the Necromancer up in Central Alwa). Lincoln will appear inside his house at Boyd's Farm. The dialogue differs depending on rescue vs. resurrection, but the end result for both is a Tear.

[Elden Pixels]

Originally posted by Mr Fantastic:

.

Wow. we just woke up and sat down in front of the computer and we're seeing this. That's not a nice thing to wake up to, seeing someone say this.

Mr Fantastic: We're not impressed over the topic of this thread, feel free to edit it.

[Pentrago]

The same thing happened to me too and I was really annoyed because at this point I did not even know the mechanics of the water raising safe switches. I am glad there is a workaround but it is bad game design in an otherwise great game.

[Elden Pixels]

It's definitely an intentional decision to have the man clearly visible before you raise the water. If you've made it that far into the level you already raised the water once. (if you went the normal route) Killing him has absolutely no effect to the outcome of the game. As above poster mentioned you can bring him back to life and finish his quest.

When we designed this we didn't think it was bad design, we thought it was funny to play with the fact that players has no concerns killing monsters, animals, bats and going on an absolute killing spree in the land of Alwa but accidentally drowning a person seems to cause an emotional distress. If you played the original game you can also see the bosses mentioning and questioning why Zoe is killing everyone.

But everyone is entitled to their own opinion, if you think that's bad it's totally up to you :)

[Pentrago]

Thanks for your reply! The combination save point / switch really did not occur to me. You found a way better solution in Ancient Ruins, where you are given the choice. And it really happened like "Oh crap, so this save point raises the water too. I think I just drowned a guy!" But like the chest in Rose Castle (It requires three hard to reach switches, it must contain something really special!") or the one kill spikes in Eydie's Keep boss fights they are just minor design issues. I loved the Wonder Boy games for Sega Genesis so I feel right at home here.

[Broso]

Originally posted by Elden Pixels:

It's definitely an intentional decision to have the man clearly visible before you raise the water. If you've made it that far into the level you already raised the water once. (if you went the normal route) Killing him has absolutely no effect to the outcome of the game. As above poster mentioned you can bring him back to life and finish his quest.

When we designed this we didn't think it was bad design, we thought it was funny to play with the fact that players has no concerns killing monsters, animals, bats and going on an absolute killing spree in the land of Alwa but accidentally drowning a person seems to cause an emotional distress. If you played the original game you can also see the bosses mentioning and questioning why Zoe is killing everyone.

But everyone is entitled to their own opinion, if you think that's bad it's totally up to you :)

You completely missed the point. It's not bad that you can end up killing him. What's bad is the game autosaving after it.

[Elden Pixels]

Originally posted by Broso:

You completely missed the point. It's not bad that you can end up killing him. What's bad is the game autosaving after it.

The altar or whatever you want to call it that raises the water also saves the game. You can't raise the water without saving, so the save works as any other save spot in the dungeon.

We're still maintaining we don't think this is bad. But we're 100% fine with anyone having different opinions. The only thing we don't like about this topic is the original poster subject line and we asked him to change it.

[Broso]

Yeah that title is a bit harsh. Despite being of a different opinion, I think it's cool you guys take the time to actually answer people's rants on here ;)

[EctoplasmChasm]

Well to be honest I was feeling the same way, I saw the guy but I kind of thought, that since the doors are closed, he would be "sealed" in, as in the water can't reach him and he can swim out afterwards.
As to why it bothers me even though I'm killing enemies left and right: enemies actively attack me: The skeletons, flowers, statues, bats, ghosts etc. actively attack me... The other people don't, so I'm defending myself.

[Javierbenacaro]

Hey, thanks for the reply and for the aclarations.
It is really useful to know that even if we messed things up, it is still possible to redeem ourselves.
By the way, it is a bit hard to activate the switch and came back to discover that the guy just died (and that you cannot undo it).
I understand the reasons, but I would have preferred that the switches would have save only if you interacted directly (like when using a drop).
Anyway, awesome games, just finished the Awakening (100%) and jumped right into the Legacy.
I'm really loving them!

[Compass]

I played this on PS5. I think I freaked and ended up downloading an older save from the cloud to reverse the decision. I agree this could have been handled better.

[whoozle]

Thanks guys, it may sound weird but I was SO disappointed with that so I quit and never played again.

Even though dev mentioned they wanted him to be clearly visible - I haven't noticed him.

It feels so wrong to have permanent unrecoverable events in metroidvania games.

Accidentally found this thread and it seems like I can continue!

[Max Cher]

Can confirm – it feels terribly wrong and discouraging drowning him. I went to discussions to check if anyone else felt the same and now I know it can be reverted, but still – it's such a bad feeling. I wish it was made more elegantly.

[AeroFunk80]

I know the devs are strongly defending their position on this decision, but I agree with a majority here. I'm not a fan of the fact we can accidentally kill the guy. While we can (apparently) resurrect him later, and this doesn't impact the ending of the game... I really dislike how we can't load several previous saves and must commit to some decisions with no going back.

It's a single-player game, so why they insist on our decisions being a final commitment is just weird to me. If player's accidentally make a mistake and want to revert back to do it another way... I don't see why they'd deny us of this.

Again... it's a single-player game. Who cares if people are reloading previous saves. I was also annoyed I killed the guy.

[Dette]

Originally posted by Elden Pixels:

When we designed this we didn't think it was bad design, we thought it was funny to play with the fact that players has no concerns killing monsters, animals, bats and going on an absolute killing spree in the land of Alwa but accidentally drowning a person seems to cause an emotional distress. If you played the original game you can also see the bosses mentioning and questioning why Zoe is killing everyone.

After finishing Alwa's awakening (which I loved) I immediately bought this game and currently 4/5 hours in. I also accidentally killed this guy, while I realised the water would rise I just didn't think that would mean I would kill someone. I felt so bad but simultaneously I laughed at myself, I found it not that bad so I think people here are overreacting. Just like you say, we kill anything in your path but a npc is a no-go?
Thanks that you made it reversible though and that it doesn't have any consequences on 100%ing the, I came here to look it up and am glad that my stupidity doesn't have long lasting consequences, lol