Video summary

Why is everything in Runescape ˢᵒ ˢᵐᵃˡˡ ?

Main summary

Key takeaways

Educational

Main ideas / concepts

  • Old School RuneScape (OSRS) cities and regions feel “too small” and distances are too short compared to what their lore implies.
  • This mismatch isn’t just an aesthetic choice; it’s explained by “scale theory,” a framework for understanding how game worlds compress reality and lore into playable form.
  • The game world shown to players is intentionally incomplete:
    • Not necessarily missing things in a “content removed” sense,
    • but missing a lot of geographic/lived-in “world” scale (density, breadth, spacing).
  • Similar “scale problems” exist in other games (e.g., Pokémon, Skyrim), suggesting the issue is common in fantasy world design rather than unique to RuneScape.
  • Attempts to measure OSRS/Gielinor using tiles, character height, or engine behavior don’t reconcile cleanly with narrative travel times and geographic descriptions.
  • Time is also scaled (actions take consistent in-game seconds that don’t feel physically proportional), and NPCs appear to run on different types of looping behavior.
  • Even if a more “realistic” scale sounds appealing, it would hurt gameplay:
    • Larger maps mean more server load and complexity.
    • Emptier space would reduce meaningful encounters and create “waiting” rather than “progress.”
    • OSRS is built for accumulation (resources, encounters, progress), and realism would flatten that rhythm.

“Scale theory” model (explained as X and Y gaps)

The video proposes a layered model for how game worlds relate to lore and what players see:

  • Game universe (rules-based theoretical world)

    • Everything that could exist within the game’s internal rules.

  • Gap X: “not yet written / undesigned” portion

    • Described as stories that are not written and regions that aren’t designed.
    • Examples given:
      • Pokémon Generation 10
      • RuneScape’s Eastern Lands
      • Elder Scrolls 6

  • Game lore (documented/confirmed by creators)

    • Lore is treated as “confirmed” canon rather than purely theoretical.

  • Gap Y: scale theory compression

    • How lore gets reduced (“simmered”) into what players actually see.

  • Player-visible world (what you experience while playing)

    • The presented world through the lens of your character’s viewpoint.

Key analogy

  • The player character is compared to having tunnel vision—focused on goals, ignoring most “fluff” and thus experiencing compressed scale.

Evidence/examples of OSRS scale being compressed

1) Major cities described as huge, but visually tiny

  • Varrock

    • Framed as “the greatest human city in all the world” (from a RuneScape novel, Betrayal at Falador).
    • In-game, it looks like it has far fewer buildings/housing than the lore implies.

  • Ardougne and Falador

    • Also discussed as being portrayed as major population centers in the novels vs. their smaller in-game layouts.

  • Explanation offered

    • These places have far more NPC roles (guards, officials, workers, shopkeepers, etc.) than visible housing could support.

2) Locations implied by mini-games/side content don’t exist on the permanent map

  • Temple Trekking mini-game

    • The mini-game routes pass through areas that don’t appear as mapped regions in the normal world map.

  • Misthalin Manor

    • Described in story as being on an island near Lumbridge Swamp.
    • But no island exists there on the map, and even with sailing expansions, the manor isn’t shown.

3) Optional travel systems can produce “deliberately unremarkable” crash sites

  • Balloon transport
    • If a route isn’t unlocked, balloons crash at two designated crash sites.
  • These crash sites are portrayed as:
    • small, barren clearings
    • lacking landmarks
    • not clearly anchored to the map’s larger geography

Video suggests these areas are designed to feel like you’re “lost in the woods,” reinforcing that the world is broader/messier than the discrete tiles imply.

Why measuring OSRS/Gielinor precisely fails (methodological attempts + mismatch)

Past approaches mentioned

  • Character height vs. door frames
    • Using the player model as a reference.
  • Tiles as fixed real-world distance
    • Treating tiles like meters and scaling outward to generate a map size.
  • Reverse-engineering from the Java engine
    • Treating the game as a technical artifact whose scale could be decoded.

One estimate mentioned:

  • Mod MatK (via a livestream) suggests ~4 ft per tile.

Why these approaches don’t work

  • Narrative travel time and distance descriptions in books conflict with in-game travel times.

    • Example: in Betrayal at Falador, travel from Falador to Ice Mountain foothills is described as 3 days.
    • Another quote: Eastern Bank hunting restriction implies Varrock is 2 days travel away.
    • Example distance claim: characters stop after 20 miles and can’t see Falador (despite it being “right there” in-game).
    • Later narration: Edgeville is a full day’s journey east after a monastery fight.

  • The same “warping” is also said to apply to density/descriptions:

    • “Dens” described as ramshackle warrens and streets that look identical in the dark don’t match one-to-one with the playable layout.

Core takeaway

  • The world is not built to be metrically measured from tiles to lore as if it were a real-world map.

Time scaling and NPC “looping” behavior

Physical time scaling (actions take consistent in-game time)

Examples:

  • Stringing a shortbow: 1.2 seconds
  • Building a ladder with shelves: ~3 seconds

Argument:

  • These durations don’t match how long such tasks would take in real physics, implying time is scaled too (game logic overrides realism).

Types/levels of “time loops” for NPCs (in increasing weirdness)

  1. Static, non-interactive scenery

    • Does not move or animate (treated as “paused” Gielinor).

  2. Short time-loop NPCs

    • Example: bankers
    • They appear to animate in place, stuck in short loops.

  3. Wanderers (free movement within a radius)

    • NPCs can roam within about five tiles
    • Viewed as “chaotic time loops”: they eventually return to starting positions via paths they choose.

  4. Controlled loop work NPC

    • A worker carrying archaeological finds to a museum repeatedly runs the same route.
    • Video provides a route-timing example:
      • 3 minutes per loop
      • If looping nonstop since May 29, 2007, then 3,261,599 laps completed (as calculated in the video).

  5. Long-running large conflict loop

    • A battle between gnomes and Kazzard warriors
    • Described as ongoing since 2002
    • A claim is made:
      • 148 million gnomes have died in that place since 2002

“Why” the world is scaled and why it feels better to play

Technical/design reasons

  • Making a bigger, more realistic world is expensive and harder

    • OSRS started as a Java applet browser game with tight memory/processing constraints.
    • With limited resources, every extra tile/object mattered.

  • Smaller team / earlier development constraints

    • Early RuneScape was made by a small team; realism adds design/testing/deployment cost.

  • Server and multiplayer considerations

    • Larger maps mean more data, entities, pathfinding calculations, and state updates.
    • More empty space requires more infrastructure still to track updates (the example given uses the “tree falls” server-state thought experiment).

  • Empty space also creates population demands

    • A larger world needs more people/entities to feel “alive.”
    • More players increase load, complexity, and instability—so dense worlds are easier to run.

Player-experience reasons

  • A 1:1 scale would be exhausting and create “friction.”
  • OSRS relies on accumulation pacing:
    • accumulating resources, encounters, and progress
    • frequent discovery moments keep the loop engaging
  • More realistic scale would likely:
    • space out encounters/resources
    • reduce uniqueness
    • flatten the experience
    • feel like waiting rather than progressing

Instructions / methodology (explicit or implied steps)

No explicit how-to gameplay methodology is given. However, the video outlines an explanatory “method” for understanding world compression via the scale model:

  • Define layers of world reality

    • Identify the game universe (rules-based theoretical world).
    • Introduce Gap X (not-yet-written stories/undesigned regions).
    • Identify game lore (creator-confirmed documented canon).
    • Introduce Gap Y (lore compression into what’s shown—scale theory).
    • Identify the player-visible world (what appears on the map and is experienced through the character).

  • Test the model against concrete examples

    • Compare lore population/travel claims vs. in-game geometry and travel duration.
    • Compare mini-game implied locations vs. permanent map presence.
    • Look for NPC/area behaviors that suggest the world is broader/messier than the tile map.

Speakers / sources featured (as identifiable in the subtitles)

  • Narrator / video creator
    • Speaker using “I” and explaining the framework; name not clearly stated in the subtitles.
  • Jimmy
    • Mentioned repeatedly as “Jimmy” and as a creator who discussed related findings.
  • Mod MatK
    • Mentioned as having suggested ~4 ft per tile in a livestream.
  • Noclip Austin
    • Referenced as having discussed Skyrim tree density being about a fifth of real life.
  • Alien Food
    • Referenced as having footage of a balloon crash site.
  • The creators / Jagex
    • Referenced as the developers; not a speaking source but cited.

Original video