Soulframe Glossary: Preludes, Pacts, Virtues & Nightfold

Key Soulframe terms

Official terms versus community shorthand

Official terms explain how the developers frame the game; community shorthand compresses experience. Both can be useful, but mixing them creates false authority. This glossary separates official wording from player-made labels so a beginner can tell what is confirmed and what is opinion.

Pacts are not traditional classes

A Pact describes a bond and the abilities connected to it. That makes it closer to a direction of growth than a fixed class with a permanent skill tree. During Preludes, use Pacts to frame a question, such as what spacing or timing you want to practice, rather than to claim a solved meta.

How Virtues guide decisions

Courage, Grace, and Spirit give you a compact way to explain playstyle priorities. Courage suggests direct engagement, Grace suggests positioning and timing, and Spirit suggests magick or ability-led choices. They are descriptive signals, not strict factions or locked paths.

Why Nightfold matters

Nightfold creates a deliberate place to review and swap earned loadouts outside combat. Practically, that means a build experiment has three parts: the intention, the encounter test, and the later swap decision. Using Nightfold impulsively removes the information you need to improve.

How to read a Soulframe discussion without getting lost

When a post uses a term you do not recognize, first ask whether it is official language, a community abbreviation, or a nickname for a temporary strategy. Then check whether the claim depends on a specific patch. This habit keeps new information organized and prevents slang from becoming an assumed game rule.

A simple vocabulary log

Keep four columns: term, where you saw it, current meaning, and confidence. Official language has high confidence, repeated community language has medium confidence, and a single unverified claim stays low confidence. The log becomes a personal onboarding guide as more Preludes systems appear.

How to verify a term you have not seen before

Start with the context in which the term appeared. Copy the exact wording, the page or discussion title, the date, and one surrounding sentence; a term lifted out of context can change meaning completely. Next, search that exact phrase against the official website, official FAQ, official update page, and Steam copy. If you find an official match, record the term as official language and link the source. If the match appears only in player discussions, record it as community language, note how many independent discussions use it, and mark its patch context. If only one post uses it, keep confidence low until you see it again or observe it in the client. For bilingual notes, keep the official English term beside the Chinese explanation so a later update can be compared without translating the name twice. If two sources conflict, keep both meanings and their dates rather than choosing the more dramatic interpretation. This process does not make terminology permanent, because Preludes can rename systems, but it does prevent a nickname from being promoted into an official rule without evidence.

• Record the exact phrase instead of a shortened translation.
• Separate official source, repeated community use, and one-off speculation.
• Attach the patch or update period to the meaning.
• Reclassify the entry when an official page later uses different wording.
• Keep contradictory meanings separate instead of merging them.
• Preserve the official English form in a bilingual note.
• Date every confidence change so older notes remain interpretable.
• Keep the original source wording beside your shorter summary.
• Mark translated explanations as explanations, not official wording.
• Remove an entry only after the source and client both stop using it.

FAQ