Skip to content
Beccalia

Beccalia: Origins

Beccalia: Origins (hereinafter the “Game”) was originally planned as the story of Becca and Rosalia growing up, but it was only released as a demo.

This section is for players who are exploring or playing the Game.

  • Keyboard / Gamepad:

    • Arrow keys / D-Pad: Move character
    • Z / Enter / A: Confirm / Interact
    • X / Esc / B: Cancel / Menu
    • C / Space / Y: Open menu (if applicable)
    • Shift / L / R: Dash (if enabled)
  • Touch UI (Mobile / Tablet):

    • Tap to move or interact
    • On-screen buttons for menu and actions
  • Ensure your device meets RPG Maker MZ requirements.
  • If the game crashes, try restarting the app or clearing temporary files.
  • Ask us on discord if persistent issues occur.

This section is for those interested in running, modifying, or extending the Game.

  • Engine: RPG Maker MZ
  • Plugins Used: none
  • Assets: All original
  1. Open RPG Maker MZ.
  2. Load the project folder beccalia-origins.
  3. Use the “Playtest” button to run the Game locally.
  4. To export, use the “Deployment” feature for target platforms.
  • data/ — database files (maps, events, actors, items, skills, etc.)
  • img/ — graphics (characters, tilesets, animations, pictures, etc.)
  • audio/ — music and sound effects
  • js/ — plugins and core scripts
  • www/ — exported HTML5 build (if deployed for web)

This section expands on legal or licensing information specific to the Game.

This Game is created using RPG Maker MZ. The game code and original content are the property of SpellWare. RPG Maker MZ runtime assets are licensed under the terms provided by KADOKAWA Corporation. All original graphics, music, and story content belong to SpellWare and are protected by copyright.

  • Any third-party assets, music, or plugins included are credited in game.

This section is for contributors or collaborators on the Game.

  • Fork or copy the project folder.

  • Submit patches or mods via Git.

  • Include a changelog and clear notes on modifications.

  • Plugins in js/plugins/ should follow standard JS conventions.
  • Comment custom scripts clearly for readability.
  • Maintain original resolutions where possible (48x48 tiles, etc.).
  • Use consistent naming for files in img/ and audio/.
  • For collaboration or questions, ask us on discord.