Resource handling

FEAR OF FAITH Items Guide

Use FEAR OF FAITH resources and the officially stated ten weapons with purpose, team ownership, environmental awareness, and no fabricated drop tables.

Last verified August 21, 2026

Early Access · Available909 words

Field answer

What to know first

The official store states that FEAR OF FAITH includes ten weapons, but the checked sources do not support a stable complete catalog of names, stats, drops, or upgrade values. Evaluate any current item by purpose, immediate problem, ownership, and the option it preserves. Announce consequential pickups or transfers in co-op, and keep build context with personal notes.

Work inside the verified item scope

Ten weapons is an official scope fact. It does not establish the name, damage, ammunition behavior, rarity, drop location, or upgrade path of every option. The current evidence also does not support a complete item database. Publishing those gaps as facts would be worse than offering a smaller planning framework. Read current in-game descriptions and feedback for specifics visible in the live build.

  • Date personal notes by build or version because Early Access can change balance and availability.
  • Distinguish visible in-game text from inferred behavior.
  • Use an old guide, clip, or demo report as a question, never as a replacement for current evidence.
  • Expand a published item claim only when an official source supports useful detail.

Handle the examples the official material actually gives

The current official store describes utility items and consumables, and it names alcohol and COPIUM in the mission loop. It also says physical items can be grabbed, thrown, or used from the hands. Triggered grenades can be thrown away, and teammates can catch thrown items. Those handling details make position and communication part of item use without supplying an invented inventory list or effect value.

Fuel canisters belong only to historical demo context in this guide. Developer notes from that earlier build make them a permitted historical example, not proof of current placement, behavior, or availability. Check the present in-game description before planning around one. Keeping that boundary visible prevents an old demo item mention from becoming a claimed Early Access rule.

Classify the resource by purpose

Ask whether the resource helps gather information, preserve movement, control space, support another action, interact with the environment, or recover from disruption. These categories are editorial and do not pretend to be official item types. They create a common language for comparing unlike options without fabricating numerical efficiency. The same resource may serve different purposes in different bunker states.

Before using or transferring something consequential, name the current problem and what option should remain afterward. A tool used to avoid a small inconvenience may remove the only recovery answer. A resource saved too long may never contribute. Purpose keeps conservation and spending connected to the run rather than to habit.

  • Information: reduce uncertainty before movement.
  • Mobility: preserve or create a usable lane.
  • Control: make a dangerous space manageable.
  • Environment: support a physical interaction or machinery plan.
  • Recovery: restore a coherent state after a mistake.

Give important resources an owner and backup

In co-op, decide who carries, uses, or calls each important option and who understands the fallback. Ownership prevents several players from assuming somebody else will act. It should remain flexible: the player with the right position or information may become the practical owner. Announce transfers so the shared plan stays accurate.

Solo players already own everything, which creates a different problem: attention. Organize decisions by purpose and keep the emergency option mentally distinct from routine tools. When entering an uncertain area, know which response can be used without searching through an improvised plan. This is preparation advice, not an exact inventory requirement.

Compare items with environmental options

Physical interactions, bunker machinery, movement, weapons, and spells all compete as possible answers. Before spending, check whether positioning or the environment can solve the problem while preserving resources. Do not force an environmental solution if it creates greater risk merely to save an item. Compare outcomes and fallbacks, not an unsupported hierarchy of tool types.

Generator and light choices deserve special coordination because they can alter what the team sees and how it moves. If an item supports that plan, state the relationship. After the interaction, reassess whether the intended resource was actually preserved or whether the group created another cost elsewhere. This review turns a pickup into part of a strategy instead of isolated loot.

Share without creating inventory friction

A useful transfer answers a coverage gap. Give the option to the player positioned to use it, responsible for the relevant purpose, or lacking a fallback. Avoid hoarding every flexible answer with one person if separation would remove all recovery. Also avoid constant redistribution that consumes attention and makes ownership unclear. Agree on transfer moments at stable landmarks.

Use short calls: item purpose, new owner, expected use, protected fallback. The call works without publishing item names or stats. If the group discovers a strong interaction, record the current build context and the exact visible conditions. Do not promote one success into a guaranteed drop route or universal loadout.

Review resource decisions after the run

Identify one resource used too early, one held too long, and one that created genuine flexibility. Ask what information was available at the decision. This focuses the review on judgment rather than hindsight. Procedural variation means the next run may offer different resources, but the decision quality can still improve.

Use the builds guide to assign coverage, the bunker guide to compare environmental answers, and the B.O.S.S. guide to protect readiness options. Recheck official sources after updates and avoid reserved weapon-detail routes until evidence can support useful individual pages. The unpublished routes intentionally remain 404 instead of becoming thin or invented catalogs.