WOSWOS Wolfite's Obby System

Getting Started with WOS

This guide assumes WOS is already installed correctly. If it isn’t, follow the Installation Guide first.

Playtesting in Studio

Press Play as usual. Saves and purchases need extra Studio settings:

  1. Open Game Settings > Security.
  2. Enable Enable Studio Access to API Services so DataStores work in Studio.
  3. Optionally enable Allow HTTP Requests (useful for update-related behaviour).

Notes:

  • Progress may not persist the way you expect in some run modes prefer the full 'Play' run mode / a published experience when debugging saves.
  • Badges and developer products also need a published experience and correct IDs in Configurations.

Configuring WOS

Almost everything interesting is driven by one ModuleScript:

ReplicatedStorage > WOS > Configurations

Double-click it in the Explorer to edit. For a short locator guide, see How to configure WOS.

How to edit safely

  • The module should return its table with the existing keys intact. Prefer changing values over deleting keys.
  • Many options have inline comments, so read those carefully before changing behaviour.
  • For a specific feature (badges, skips, chat messages, animations), use that feature’s docs page rather than guessing.

Examples of things you’ll configure here: badge IDs, skip product IDs, coil game pass IDs, checkpoint animation style, system message text, and (with Premium) watermark / extra settings toggles.

Removing the watermark

WOS is free software. A short splash watermark and system credit help people discover it. Removing credit from the source without WOS Premium is not allowed.

  • Premium options to hide branding: Remove Watermarks
  • Free tier can only adjust limited loading-screen behaviour as documented on that page

Build your stages

WOS expects numbered checkpoints that players touch to advance. Typical workflow:

  1. Duplicate a working checkpoint as a template.
  2. Set a unique stage number for each one.
  3. Keep checkpoints anchored and non-overlapping.
  4. Leave enough travel time between stages (about 1.5+ seconds) so highlight / award logic stays reliable.

Then layer on features as you need them: stage selector, badges, monetization, system messages, and so on.

Common issues

Many questions are already answered on the FAQ, especially StreamingEnabled, watermarks, and progress not saving.

Inspiration

Backgrounds on these docs pages are real games running WOS. For more examples and community pages, see the Obby Wiki entry for WOS.



Community Support