Welcome to the rpg.actor Game Jam!

Every character on rpg.actor lives on the open social web. Stats, sprites, game system data — all stored on the player's own server through AT Protocol. Any game can read them. Some can write to them. Nobody owns the data except the player.

Through rpg.actor, players log into different games using their existing Bluesky accounts (or any AT Protocol personal data server) and carry a persistent character across multiple experiences. Your stats and sprite travel between adventures, you level up across different worlds, and your persona lives on across the internet.

Your mission: make a game, tool, or novelty that connects to the registry. Pull in a player's character sheet. Let them change their sprite. Do something weird with their alignment score. If it touches the actor.rpg.stats or actor.rpg.sprite lexicons, it counts!

Full details, rules, and resources at rpg.actor/jam

---

Prizes

First Place An original and complete Japanese boxed copy of RPG Maker 2000 (RPGツクール2000) with manuals for Win95, Win98, and Win2000. Printed by ASCII / Enterbrain. Plus an Ultimate Creator account on rpg.actor with a 100 character limit and your own custom .world domain to take your creation to the next level. Second and Third Place Master Creator accounts on rpg.actor with 50 characters to help you create and share. Fourth and Fifth Place Builder Creator accounts on rpg.actor with 10 characters to expand your world.

---

Some Jam Ideas

Login as Characters Use the RPGACTOR_Login plugin to load a player's character and use their existing stats and sprite to play!	Compendium NPCs Pull random characters straight from the rpg.actor compendium and populate your game world with them.
Wardrobe Changes Build a custom character designer or clothing shop and update existing sprite records with new and stylish outfits!	Something Unexpected Make a tarot reader out of existing stat data. Make a slot machine where losing turns your sprite into a goblin. Go wild!

---

Rules

1. Integration — Read or write at least one rpg.actor lexicon.
2. Any Engine — RPG Maker MZ, Godot, Unity, or even a web app.
3. Solo or Team — No size limit, bring all your crew!
4. New Work — The rpg.actor integration must be built during the jam.
5. Be Kind — No hateful or harmful content. No bullying or exploitation.
6. Open Source — Only open source entries are eligible for Verified trust status.
7. AI Disclosure — Development of AI assisted code must be disclosed in project description.
8. Human Artwork — No generative AI may be used for artwork, audio, or writing.

---

Judging

Entries are scored across four categories scored by our panel of judges.

Data Usage (.stats)	How well does the entry read, write, or leverage the actor.rpg.stats records?
Art Usage (.sprite)	How well does the entry use or modify player actor.rpg.sprite records?
Novelty / Creativity	Does the entry surprise us? Original ideas and unexpected uses will score high.
Quality / Polish	Playability, presentation, and overall craft. Completeness goes a long way.

---

Safety

Jam entries authenticate with AT Protocol using player credentials, which enables a ton of powerful features for developers.

We take the safety of these controls seriously.

Every featured entry by rpg.actor will display a trust score after the jam:

• Verified — Source code reviewed, network behavior inspected, vetted by admins.
• Reviewed — Source available and passed verifiers with no signs of tampering.
• Unvetted — No source available or not yet reviewed. Play with test accounts only.

For Players

• Create a Playtest Account — A fresh Bluesky account with a throwaway email is a risk-free way to sample games.
• Check OAuth URLs — Check the source URL for any OAuth logins to make sure you're accessing your own PDS.
• Review Permissions — Assure that games are only requesting to read/write relevant permissions during login.

For Developers

• Publish Your Source — Only open source entries are eligible for Verified safety check status.
• Only Connect Where Needed — Your game should only make network requests to the user's PDS for relevant records.
• Don't Store Credentials — Authenticate, use the session, and discard. Never store or transmit tokens anywhere.

---

Resources

Developer Guide	rpg.actor/dev-guide
Systems Reference	rpg.actor/systems
Lexicon JSON files	rpg.actor/lexicons/
Public API	rpg.actor/api/
AT Protocol docs	atproto.com/docs
Licenses & Disclosure	rpg.actor/licenses

RPG Maker MZ Plugins

The rpg.actor plugin suite for integrating in RPG Maker MZ games AT Protocol logins, character stat sync, live sprite loading, and social post integration. A sample project has been provided for exemplary usage.

Download Plugins	rpg.actor/plugins
Installation Guide	rpg.actor/dev-guide
Jam Page	rpg.actor/jam