1st story quest the lost son, anyway to save him?

[Funz]

Is there anyway to save the lost adventuring son? if so what is the outcome?

[TheKingBoysan]

Yes and he joins the Guild, he's got good traits.

[Funz]

guess im restarting my run ._.

[Craig Prime]

So long as you can follow the trail and don't take too long to reach him, saving him is perfectly doable.

"Good Traits" does not do him justice, this son will join your guild and become the legendary hero that all your other adventurers could only dream of sharing a party with. You could find an adventurer in the tavern with a trait combination that make them the best damn mage in the kingdom and they still won't even be able to compare to this guy, because this guy is the best [insert any class] in the world by the time he's level 10.

[Ryan]

I made him a Knight, but his stat growth for every stat is outrageous. I'm still early (pre level 10) not sure what he'll end up being. Stupid powerful I love him.

[Blake]

you need to give him a healing potion when you reach him, i don't know if having a priest in the party can save him as well. he's the most flexible character you get so i'd restart the quest if you couldn't save him

[Corzair]

Confirmed that having a priest will provide an option to save him.

[Gorgeous_Joe]

Yep, Elan, Daryl, Alissa and the others are all legendary if you level them correctly.

[Carambar]

I didn't take so long to reach him... After wasting a short time trying to avoid a goblin, I rushed my way to its location. Only to find out he's dead, after a very tough fight that dissipated all my healing potions.

I had a well and alive priest in the party. Didn't get the option to save him... Disappointing.

[Haplo]

If he was dead when you found him then you spent too many turns on the map before getting to him. If you get to him in time and don't have healing item or a Priest he will die then.

[Carambar]

I don't think that throwing a time-limited quest with the outcome being missing out entirely on a story character at the very beginning of the game is wise. Both time-limited to start the quest AND time-limited within the quest itself. And a very short time at that.

I just purchased the game yesterday. Not even 3 days have passed that I'm alrdy on a timer when my adventurers are still recovering from the initial missions, meanwhile I'm being bombarded by new assignements, introductions to new npcs & tutorials . Had to recruit a bunch of newbies for this quest and the encounter blocking the passage is just so much harder than what seems to be reasonable at this stage of the game. I do have a +20% hp and dmg multiplier for enemies but still; it does not seem like an encounter that should appear at the very first week of the game.

i only managed bcs I've read somewhere that the AI only targets the closest target, instead of rushing for the weakest available target in range. (as it used to before a patch came out!)

I'm open to criticism and welcome advice if anyone cares to. But that's my two cents on the matter as a new player. It really doesn't feel good.

[FlyingTorcensoredWhale]

Originally posted by Carambar:

I don't think that throwing a time-limited quest with the outcome being missing out entirely on a story character at the very beginning of the game is wise. Both time-limited to start the quest AND time-limited within the quest itself. And a very short time at that.

I just purchased the game yesterday. Not even 3 days have passed that I'm alrdy on a timer when my adventurers are still recovering from the initial missions, meanwhile I'm being bombarded by new assignements, introductions to new npcs & tutorials . Had to recruit a bunch of newbies for this quest and the encounter blocking the passage is just so much harder than what seems to be reasonable at this stage of the game. I do have a +20% hp and dmg multiplier for enemies but still; it does not seem like an encounter that should appear at the very first week of the game.

i only managed bcs I've read somewhere that the AI only targets the closest target, instead of rushing for the weakest available target in range. (as it used to before a patch came out!)

I'm open to criticism and welcome advice if anyone cares to. But that's my two cents on the matter as a new player. It really doesn't feel good.

As someone in the same boat and experiencing the game for the first time, I didn't have any issues with this quest. Permadeath, Normal difficulty.
First thing I did: I hired EVERY available adventurer on the first week. Then EVERY available adventurer on the second week. I've been able to constantly rotate guys between quests and I had a crew of level 2s and 3s to send on this quest.
I've attempted it with 5 days still in the bag for the quest timer.

I also try to send and adventurer with at least 1 high stat of each stat whenever I am sending a party in, so on the quest itself it was easy to pass checks. And the encounter overall was relatively easy (the party was outfitted with decent equipment, had a healer and had potions, bandages, antidotes and bombs with them).

So far I feel like you don't have to pick cream of the crop at the start. Just fill in the ranks with whatever you have on hand and slowly replace terrible guys with better guys along the way. Just throw bodies at the problem. If you have enough dudes to send on a quest every single day, you're gonna be fine.

Don't shy away from healing guys that take massive damage and have to sit back and heal for 5-6+ days. Sure, it will debuff their mood for a period of time, but at least they will be usable, instead of "in good mood, doing nothing". Push comes to shove - buy them a beer.

[TheKingBoysan]

Originally posted by Carambar:

I don't think that throwing a time-limited quest with the outcome being missing out entirely on a story character at the very beginning of the game is wise. Both time-limited to start the quest AND time-limited within the quest itself. And a very short time at that.

I just purchased the game yesterday. Not even 3 days have passed that I'm alrdy on a timer when my adventurers are still recovering from the initial missions, meanwhile I'm being bombarded by new assignements, introductions to new npcs & tutorials . Had to recruit a bunch of newbies for this quest and the encounter blocking the passage is just so much harder than what seems to be reasonable at this stage of the game. I do have a +20% hp and dmg multiplier for enemies but still; it does not seem like an encounter that should appear at the very first week of the game.

i only managed bcs I've read somewhere that the AI only targets the closest target, instead of rushing for the weakest available target in range. (as it used to before a patch came out!)

I'm open to criticism and welcome advice if anyone cares to. But that's my two cents on the matter as a new player. It really doesn't feel good.

Also new to the game. Playing on normal and i think the game is too easy. Iv'e only seen a few timer missions, also i don't think saving the boy is that important, i don't even use him or any of the pre-made characters as i like the RNG.

If your adventures are injured just heal them for 200 and buy them a beer for another 200, rest a day to make them happy, and you can keep using the same characters, pretty easy way to get an 10 day injury gone in a day.

[Carambar]

Followed roughly the same mindset as you have for the most part. Only skipped the healing & I'll definitely learn to use it if I see a good opportunity for it.

I have 10 adventurers and tavern hasn't rotated its "stock" yet. 4 adventurers was the max I could send on this mission anyway, a lv2 Priest was part of it.

It's a shame cause while I managed the fight, it was only to find out that the dude was dead before the party arrived! RIP.

Even then, I firmly believe that this quest should appear later on, once the player has had time to settle in with all the introductions and tutorials. Or make the timer within the quest itself more lenient. Well, that's more of a message to the developer but it is obviously up for debate among the community.

Time for a restart then!

Edit: I wasn't specifically complaining about the difficulty of the encounter or the game in general. Rather, it is when this quest is made available.

The quest itself is presented to us at the very beginning of the game while we are being introduced to the core game mechanics and several npcs.
It is time-limited, and there's a very tight timer within the quest itself as well.
The encounter blocking the path is way harder than the first enemies we are introduced with in comparison and only manageable because the AI behavior has been nerfed. Including having to know that a Priest or Healing potion will be needed to even complete it and if you don't, get *****d. It wasn't a problem for me since I had a priest, but what about anyone else who didn't and used all their potions to survive this encounter? They would make it in time only to realize that it was all for nothing anyway.

Great way to leave a sour taste when the game has just started.

I realise the dude we unlock is totally broken, but is it then necessary to introduce him this early into the game?

[Nitroglycerine]

That's weird. At least for me, the timer wasn't tight at all.
I played through the first 15 days around 5 times, and never had him dead when I reached him.

Usually, I went right, then up, fought the goblin enemy, collected all the resources, walked further up, fought the 2nd battle, then collected the chest there, and walked to the guy and he was alive and kicking.

Did you camp? Maybe camping a day was what caused him to die?

[Carambar]

Originally posted by Nitroglycerine:

That's weird. At least for me, the timer wasn't tight at all.
I played through the first 15 days around 5 times, and never had him dead when I reached him.

Usually, I went right, then up, fought the goblin enemy, collected all the resources, walked further up, fought the 2nd battle, then collected the chest there, and walked to the guy and he was alive and kicking.

Did you camp? Maybe camping a day was what caused him to die?

Yes, I did camp! That would make sense; it's my bad for omitting this detail in my previous posts.