Gothic Remake: Planning an Overachiever Run

Gothic Remake: Planning an Overachiever Run
Image: TposeGaming, used with permission.

Keep skill progress together on one save.

Verified route notes

TposeGaming frames Overachiever as a single-playthrough skill challenge. Its route prioritizes Learning Points for skills, with equipment and permanent bonuses supporting character attributes.

The July article also describes a PS5 tracking mismatch. Check later patch information before assuming that historical issue still applies.

  • Track learned skills on the same save.
  • Keep a backup near completion instead of overwriting every milestone.
Gothic Remake: Planning an Overachiever Run
Reference image from the linked TposeGaming guide.

Plan one continuous skill record

Begin with a single save lineage for the achievement attempt. Keep a simple list of learned skills, the character on which they were learned and the milestone save that records them. Do not add together progress from separate experimental builds and assume that the combined list represents the state of the character you intend to finish with.

Distinguish learning a skill from meeting a weapon requirement or wearing equipment that changes an attribute. The source’s proposed strategy reserves Learning Points for skills and uses other bonuses to support attributes. That distinction is the useful planning principle; it does not establish that every attribute target can be reached without spending points.

Gothic Remake: Planning an Overachiever Run — source reference
Reference image from the linked TposeGaming guide.

Audit the next purchase before committing

Before a lesson, record the available points and the training option you intend to buy. Afterward, inspect the character’s skill information and confirm the change. A training conversation that was opened and then cancelled should not receive the same check mark as a lesson actually learned. This small record becomes valuable when several systems are being developed together.

Write down faction or progression restrictions beside the skills that still need attention. The two-handed trainer route, for example, has prerequisites described in its separate guide. Keep these restrictions visible before committing to a different goal. This page does not supply a verified exhaustive skill checklist, so it should support your in-game record rather than replace it with invented requirements.

Keep milestone saves instead of only a rolling latest save. A useful checkpoint sits before a cluster of training purchases and another after you have verified them. Name the checkpoints by what they establish, such as a completed training session, rather than by a claim that the achievement must now unlock. The platform tracker and the character sheet are different records.

Handle a tracking mismatch carefully

The source’s PS5 mismatch is a historical July report. Check the installed build and later official notes before assuming it still affects your version. If the character’s skills and the platform display disagree, record both states, when the last lesson was learned and whether the platform was connected normally; avoid declaring the run lost from a single counter reading.

Do not buy unrelated lessons simply to force a counter to change, and do not overwrite the near-completion backup while experimenting. Gather the evidence for a support request first. A completed planning sheet cannot guarantee a trophy, but it can show exactly which skills and saves were checked, making a real discrepancy easier to investigate.

Gothic 1 Remake cover art
Gothic 1 Remake cover art for context; not a route map.

Source and scope

Game-specific route notes: Gothic Remake Overachiever Achievement Guide. Additional planning and troubleshooting advice is GameThrum editorial guidance. This is not a firsthand gameplay review.

Related Gothic guides

Original source: TposeGaming

About the author

GameThrum Editorial

Practical game guides built around clearly identified sources. Each article explains its scope and source material. Send corrections through our feedback page.

↑