SKALD: Against the Black Priory Summer 2022 Update
-
Category: News ArchiveHits: 686
Scape-IT brings us a new project update for their retro RPG SKALD: Against the Black Priory that tells us to expect a new demo in late September. It then gives us a quick progress report that mainly revolves around new props, perception checks, and editor updates.
Here are the text bits:
Hello everyone!
Time for a summer update! Hope you’re all well and enjoying your summer. Here is a GIF of a procedural fountain effect to cool you off in the summer heat[...]
—News—
THE DEMO
As you know, we’re working on an updated demo for testing and promotional purposes. We were originally planning to enter it in an event in late June. However we elected to go for a different venue and now we’re aiming for late September. HOWEVER, the community will be getting builds in late August for testing so stay posted for more info!
YOUR STEAM ACCOUNT REQUIRES ACTION
Maybe. As you know we have two Steam pages: One for the main application and one for the prologue. As we move towards the new demo and eventually launch, the prologue page will have outlived its purpose. But the thing is, a lot of you guys have subscribed to, or even wishlisted (!) the prologue!
If this is you, I’d love to see you subscribe to, and wishlist the main application instead.
SOME COOL VIDEO CONTENT
I just did a roundtable with a bunch of fellow indie RPG developers! I’m sure you can recognize some faces and names below. We had a great talk about the art and craft of making indie RPGs and I can’t wait to bring you the vid! We’re going to edit it a bit and then I’ll be sure to let you know the moment it goes live.
—Development Update—
Currently development is all about making content, evaluating the workflow and then updating the tools and engine to become faster and safer. This is the only way we can keep the code and data manageable as the project grows.
PROPS
Props are the most important piece of the puzzle right now. They represent all interactable objects in the world that are not characters or inventory items. A huge priority has been to make the game world a lot more interactive by adding lots of interesting objects for the player to interact with (hidden secrets, loot, workbenches, lore-heavy decorations etc),
Now your character is constantly using their perception skill to try and spot hidden doors etc but also containers that may contain minor loot and fun secrets. I loved how “Pathfinder: Wrath of the Righteous” had a lot of hidden loot laying around, really incentivising you to put points in the “perception” skill and explore the environs[...]
Doors and chests can now be locked and you have to decide between looking for a key or picking or forcing the lock. Be careful however, props can be trapped[...]
All of the above might sound like stuff that has always been in the game though? Yes and no. The change is that this stuff was always possible (more or less) but it needed to be scripted on a case by case basis. Now it’s all been streamlined and standardized so that creating a trapped chest is as easy as two clicks on a dropdown menu.
EDITOR UPDATES
On the same note as above, a lot has also happened on the editor side. I’m putting a lot of effort into limiting manual data entry and instead focusing on creating objects for all kinds of data that is then linked together. This makes the data a LOT more error proof and also a lot faster to work with as so much data can now be reused.
A good example of this are “loadOut” and “appearancePack” objects. It used to be that I had to manually enter each item that I wanted to add to a character or a container. This a surprising amount of work if you want to carefully place items by hand as there are thousands and thousands of items in a game like Skald (and a big reason why the old demo had so much randomized container content). Same goes for character appearances: I had to manually pick primary, secondary, hair and skin color as well as hair styles and animations for each character and the work adds up quickly.
Now I instead create loadOuts and appearancePacks which are collections of data that can be referenced by several other types of objects. I can create a “Fighter loadout” and add in, say, a leather armor, a long sword and a shield. I can then assign it to the fighter class meaning that the items will be given to all characters with that class. I can also add that loadout to a container if I want to let players find that collection of items somewhere or even set it as a reward for a quest.
The same goes for appearances! I can assign appearancePacks to characters directly but also add them to objects like factions. That way, each character from the same faction can have the same colored livery etc. The cool part is that appearance packs can also be assigned to props so that props in certain areas can dynamically change color to reflect factions and so forth.
This will go a long way towards letting me customize the look of areas without having to create separate art assets to reflect different color schemes. And again: Doing so, is as easy as selection an appearancePack from a drop-down menu.
I’ve also done a HUGE job of creating meta data for all the game data. This means the editor now knows stuff like allowed ranges for numeric data, what objects can be linked to which, it can add tooltips and even to some auto-completing. This was a pretty huge job (I had to write a separate program to automate a bunch of the coding to get it done) but once again: It will make the game data sooooo much easier to work with and debug.
—In Closing—
There is a lot more that has happened but I’m already running long so I think I’ll round it off there! I’m actually taking more or less a week off starting tomorrow so huzzah I guess. I’m also a little less active on social media in the summer since I try to limit non-essential screen time so expect me to be a bit slower in responding to messages etc.
Have a wonderful summer and try to spend some time outside!
