Skip to main content

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

A dossier guideline or key would be quite useful.

A topic by ThouArtSamSki created 21 days ago Views: 81 Replies: 1
Viewing posts 1 to 2

I find when using the dossier to make custom barks, it's quite difficult to tell what placeholders are available (is it just {mech_name} and {callsign}?) and whether or not they apply to your own mech or the mech you're targeting. I tried to make one character who used proper military doctrine and would call out "{callsign}, splash one bandit, enemy down" or something to that extent, but It would use the targets name instead. It would be really nice if I could choose between own, target, and maybe ally callsigns/mech names, allowing for a mix of the two.

This is only a minor gripe and has likely only come to my attention because I spent 4 hours in just the dossiers of my pilots out of my 12 hours in the game, but I love what is already in and hope it improves :)

P.S. Keep up the great work :3


Developer(+2)

Haha I also self-sniped myself by getting caught up writing the barks. It’s such a fun exercise.

The current interpolated values are: mech_name mech_frame pilot_name callsign

I’ll make a note to look into giving more flexibility & visibility into who you can refer to in the barks! I think the reason I defaulted it to only one possible unit was to not have to handle people trying to use like target_callsign in a bark type with no target information (like deploying). But that should be fixed with better viz, now that I think about it.

Glad you’re having fun :)