Larian Studios Forums Divinity: Original Sin 2 Divinity - Original Sin 2 - Help/Tips/Tricks Tarquin not on boat when trying to depart

Same issue here. I'm on my 1st play through so I really don't want to leave him behind (not sure what all I'll miss later in the game).

He's located in the graveyard and says the following :

"Let me think. A sprinkling of skulldust. A vial of dog's drool. Dried illweed. A few more odds and ends and I can get back to the ship."

The only option is to "end" the conversation.

Encountered the same issue.
Have done pretty much anything on Driftwood area aside from butchering the whole area. Tarquin never arrives on the boat. Did the All in the family quest line too.
What happened different from my last playthrough, is that he started fighting with one of Ryker servants. Not that i have any idea if it could start this bug.

Same.
I hope it will be fixed so you could send him back to ship after you already gave him 2 parts of the sword.

Larian devs, please fix this! I've hit the same issue: All in the Family completed, Tarquin remains at the graveyard saying he just needs a few extra ingredients, only option End, but proceeding to Nameless Isle leaves him behind.

+1

Hope this makes it into the next big patch.

Tarquin bugged for me as well stucvk saying "let me think. A sprinkle of skulldust. A vial of do's drool. Dried Illweed. A few more odds and ends, and I can get back to the shit. and I am ready to get off this rock for christ sakes

Same here ... he already has the two parts !
even was looking for that "ingredients" for him ... but as expected , not in the game ...
even I have some side quests open !

+1

IF you didn't want to wait that LARIAN is willing to solve that bug,

I tried to teleport him away from his standing position ... but he attacks at once
AT LEAST ,
you could kill him to get your parts back

still want him back on the ship ...

Didn't they literally try to fix this in the most recent patch? I don't get why it's still broken :/

If they fixed it they didn't do a good job, since I have this problem in a playthrough after the last patch. Guess I'll just leave him behind...

Same issue for me . He got the two parts, the quests is not anymore in the log book and when I try to depart from the island, got the mesasge thta someone is still missing on the boat. He is also hanging around the cemetary, commenting on some ingredients and the dialog options are to end the conversation. I don't want to go to the next lsland without this character and I need this sword :p

This may not be fixed for awhile. Reading the Larian News in an interview with Swen Vincke on October 9, he said the team is on holiday after completing patch 3. No telling when they'll be back. It'd be nice if there's at least a skeleton crew who can fix this problem. I've cleared absolutely everything I can find and at a dead stop because I can't leave for the Nameless Isle without Tarquin, still broken.

I'm having this same issue, "All in the Family" is completed, but he just stays at the gates of the graveyard muttering about this and that ("let me think. A sprinkle of skulldust. A vial of do's drool. Dried Illweed...").

I thought LARIAN is reading all and still NO REACTION ...
a joke, at least some comment why the last patch, which should have solved it, hasn't done it
and WHEN we could really get a workaround or solution ...

at LEAST give us the console command to move that npc on the ship !

Read Larian news. They're on holiday

Try this:

Teleport to Lady
Use the BOAT to go to the main land.
Then use the same BOAT to boat the lady.
Tarquin should be right there with you when you back on lady.

This work after you finish All in the Famalady.

i could not get this to work for me

I had tried it and still did not work :(
I went on without tarquin and its blade
Too bad as I am quite a completionist and do my best to get the quests done and if I miss a quest I don't mind , it will be done on the next run but if I don't get the completion of a quest because of a bug, I feel fustrated, as something not being right :'(
I hope on my next run, a small patch fixing this would have been applied.