Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Tufty318

3
Posts
A member registered 23 days ago

Recent community posts

MY LIEGE THANK YOU

Please. Great Master o' Wisdom, Wizbeard. Save us from our stagnancy

Bug Report (for Wizbeard)

  • Title: Level 20 crash / temporary layout mismatch
  • Version: superJumpDude-win-v0.6.1 (Windows packaged build)
  • Environment: Windows 10 (10.0.26200)
  • Severity: High (crash) + Medium (wrong layout after workaround)

1) Original Critical Bug

  • Issue: Opening Level 20 crashes the game.
  • Steps to Reproduce:
    1. Launch superJumpDude.exe
    2. Load save slot save1
    3. Enter Stage20
  • Expected: Level 20 loads normally at the front door/start.
  • Actual: Game crashes to desktop.
  • Crash Trace (runtime):
    • IndexError: list index out of range
    • Call path:
      • superJumpDude.py line 497
      • world.py lines 444 / 506 / 773
      • levels\level.py line 955 (build)
    • Packager/runtime line:
      • [PYI-16564:ERROR] Failed to execute script 'superJumpDude' due to unhandled exception!
  • Observed at: 2026-05-01 ~9:14 AM (UTC-4)

2) Temporary Mitigation Applied

  • Local workaround: Replaced stage20.lvl with stage19.lvl content.
  • Result: Crash is avoided; Level 20 launches.
  • New problem: Level 20 now shows Stage19 layout and player is not centered at the front door on entry.

3) Likely Root Cause

  • Original stage20.lvl data appears invalid/corrupted or incompatible with loader assumptions, causing out-of-range indexing during level build.

4) Requested Fix

  • Regenerate/restore a valid stage20.lvl with:
    • Correct tile/entity array lengths and references
    • Correct Level 20 front-door spawn/entry metadata
  • Add loader safety checks:
    • Bounds validation in level build
    • Graceful error logging (level + bad index) instead of hard crash

5) Artifacts

  • Backup of original Level 20 file kept as:
    • .../_internal/levels/levelfiles/stage20.original.20260501-091459.lvl
  • Crash-free relaunch after workaround confirmed at:
    • 2026-05-01 ~9:16–9:17 AM (UTC-4), exit_code: 0