Layers of Complexity

Like an Onion...

There are many different layers that make an rpg.actor character. Stats, metadata, and account info compose the overall details of who we are, and while the visual representation (our sprites) may look solid, they're composed of even more layers all stacked atop one another. Yet, they work together to form a final structure that's easy for games to interpret and bring you to life.

But... what are these layers? Why do they exist, and how do they all work?

What can we do with them once we understand how a character is put together?

Great questions, my hypothetical friend! Let's take a dive through these layers together and see if we can make sense of how they functions, and maybe learn some of the magic behind how games work!

The Humble .sprite

One of the core concepts for rpg.actor is that the .sprite record is our base asset and should remain as simple as possible for maximum player freedom. They will always remain the final delivery mechanism for a character's appearance, and will always be a single sheet (3 x 4) that provides basic walking and idle poses.

This certainty is maintained so that developers can confidently build their games with assured compatibility, and players can easily create their own representations however they please. No matter what, any game should be able to call for a .sprite and get everything it needs to show you on screen. Simple, easy, and completely reliable.

The Noble .generator

Our free Sprite Generator is provided to make this customization for certain types of characters even easier, but it's not meant to be definitive. There are tradeoffs between its ease, uniformity, complexity, and functionality that make it very different from the humble .sprite on its lonesome. 

This is why we've taken steps to distinct a .generator record as its own entity, which houses a deconstructed version of any character built with the generator. Think of it like a blueprint for how to put you back together from scratch. Everything that you are, the details of each visible part, and how they combine is all stored within this one record.

All the layers (shirts, pants, glasses, etc) that make up the .sprite are broken into their individual parts and neatly sorted so that games can modify or substitute individual components (e.g. change your hat) and recompose the character as needed. This gives developers some additional tools when working with rpg.actors who carry this data, including a deeper read of traits for interactions, and more freedom to affect the visual appearance of your characters.

Because the .generator record is a stack of layers, it's not really viable as a final character sprite on its own, and so games should always refer to the basic .sprite as the visible entity. However, it can be used to produce a complete .sprite by "gluing" all those layers together and writing to your PDS.

Colorways and Submasks

"Interesting," you prod, "but can you make it more complicated?"

Say no more! We've got you covered.

Within the .generator there is per-layer data for colorways and submasks which are basically an extra version of the art that's harshly painted in pure blue, green, red, white, and black. These layer-layers (lol) layer atop the layers (lmao) to let players freely colourize their clothing. This is how the colour pickers are defined and controlled within the Sprite Generator itself.

!generator_3.PNG

These garish colour choices are brought to you by colorways!

On these colorway layers, blue (#0000FF) represents the "main" tone, while green (#00FF00), red (#FF0000), and white (#FFFFFF) offer additional "sub" colours for a total of four variable hues on any given piece. Typically they are laid over a grey (#808080) midtone with shade variations for light and dark sections. This creates a huge range of options with total player freedom for colour customization.

!colorways.PNG

The submask pixels will remove everything beneath them on the layers below.

Black (#000000) is used for the submask which is like a negative-layer that removes pixels from the space beneath it. This is how we prevent your hair from sticking through your hat. When the .generator recomposes the .sprite it makes sure to erase those parts covered, leaving a much more refined appearance. It can also be used to reshape the character body where the basic form would otherwise spill through, like on this example of the Slimming Shirt here:

!slimming_1.PNG

Your .item-ized Wardrobe

So we've got a flat .sprite anyone can display, a decomposed .generator that games can tinker with, and a colour system that makes those pieces expressive.

So...what are we supposed to do with all this?!

Behold, the .item record:

These are like individual inventory items, complete with their own asset layers that slot directly into the .generator stack. They include their own colorways and submasks, metadata for where they fit (hat, shirt, etc) and an icon for general display. Every complete .item will surface in the Sprite Generator as another option for you to customize your character with.

!inventory_1.PNG

This shirt and the popcorn were obtained in The Theatre as .item records

Anyone can create their own .item record and outfit themselves however they please, just like how you're able to produce a .sprite of whatever you like. The major difference here is that these assets will fit in your .generator when used, and can fluidly function in any games that make use of the more complex record compositions.

The .gift of The Magi

Every .item can also be paired with a .give record, which allows games to verify where you got the item from. These are typically provided by games or dungeon masters, but you can also make them yourself. When put together these two records show where an item came from and act as a mark of authenticity.

This means that you can create your own inventory of outfits and strut your stuff freely, then unlock new items from different games that each validate what they've granted you. Every other game you visit will know exactly where you got your stuff from and can react appropriately.

You can even begin producing .items for others as a way of sharing your creations, while keeping .give records as proof you're the one who made that super cool shirt!

!inventory_3.PNG

See how the popcorn is obtained from @rpg.actor and the shirt from @vagabond.quest?

There's no requirement to have validated items, but as the rpg.actor ecosystems grow this can be a way of building stronger compatibility between games, creating collaborative quests between experiences, and even highlighting great creators who make wonderful clothes for us all to wear.

It All Stacks Up!

Now that you know how all these many layers work together, you can begin experimenting with your own personal style. Whether you simply wish to upload a custom .sprite or build individual .item pieces to compose in your .generator there are a lot of ways you can fine-tune your character's appearance.

Over time we'll begin expanding the rpg.actor ecosystem with more tools for creators and better ways for you to share your creations with others, but for now feel free to experiment with everything available. Go make the avatar of your dreams, and games for others to experience!

If you ever get lost, the Dev Guide and our Roomy Space will be there to help.