Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

HelioSpectral

14
Posts
168
Followers
3
Following
A member registered Nov 11, 2022 · View creator page →

Creator of

Recent community posts

Yeah! I've uploaded a new version of SCARS with some rewording and layout alterations - such as letting the Fate Steel [now Arms] Heart and Bones titles sit asymmetrically, so they're more clearly attached to their tables than to each other. Let me know if the text is more comprehensible and if there's anything else I should look at!

I'll see what I can do! The intent is that "fate, steel, heart, bone" are the four categories, each of which has a single corresponding table. It's actually pretty funny that the current version never says that outright. 

Eeeuuuuuaaagh you're right. You're so right. Now that I look the core book literally says "Heat is a special type of harm that doesn’t count as damage and ignores ARMOR". Thank you so much for bringing this up. No idea when I'll have a good time to re-export everything for a version 3.1, and I'll probably wait a bit to see if there are any other corrections I should make. But expect a corrected 3.1 eventually..!

Oh! Huh. To clarify, is this a 'how does page 2 connect to page 1' kind of problem? Since now that you mention it I could definitely make that more explicit. I'm probably putting out a version 1.1 soon so I'll try to improve that! Thanks for bringing it up. 

That's incredible! I probably read this message months ago and was too self-conscious/preoccupied to respond then. But I'm reading your comment again now and it still means a lot to me! Thank you for using my little rules explainer. 

I have, and that's exactly what I did as of just now! For running NPCs in combat, anyway. Are there other aspects of GMing you think it would be useful to cover?

Yes, you absolutely could, and now can! I apologize for the extended wait to get pdf versions.

Thank you! It absolutely started as a gag, the simplest pun possible on the jam theme, and the more seriously I took it the better it felt.

I'm in the part where I've got 90% of the work done, and the remaining 10% is the other 90% of the work! There's a few final bits that have me stumped for wording and formatting, so progress has been super slow. I'm also grappling with trying to elegantly implement more accurate attack rules (it's based on weapons, not mounts), which I don't consider solved yet. But I'm glad you're looking forward to it! 

Huh, you're right! As I look back over the core book and comp/con, it seems every reaction individually specifies how often they can be performed per round. Meaning that not only is "no repeats/round" not accurate, but also the more accurate "default no repeats/round" isn't necessary.

I'll add it to my list of stuff to change! Probably I'll include that as a minor update to version 2 at the same time that I publish version 3. Thanks for bringing it to my attention. 

Ha ha, it's hard to call it "wrong" when it's literally what the core book says! I'd view it as, the option is there to play the game one way or the other. I'm really glad you're finding the sheet useful! Feel free to send me any other impressions or feedback - it all helps inform the design! 

You are correct! However, there's some errata noting that this is a misprint in the core rule book! https://lancer-faq.netlify.app/#bf060b

On the sheet, I included an asterisk next to that check, which is followed up in a side-note stating how 'Free Action' is a misprint. Considering how much other stuff is packed in there, I don't blame you for missing it! I'm glad you brought it up, since if it was an error I would want to fix it right away (and if this is something several people run in to, I'll want to update the sheet layout to make it clearer). 

I've ended up in a weird place for this one. LARS v2 has a clearer model of tech actions, but the Full Tech wording still isn't quite RAW accurate. The challenge is, if I make it say "use 2 quick-techs", that vaguely implies 2 quick-techs can't be used on their own even though they can. And, as far as I can tell, there's rarely an advantage to declaring two different quick-techs as a Full Tech. So the wording is still unresolved and still on my mind- once I find a good solution I'll upload it as version 2.0.2. I remain thankful to you for pointing it out! 

That's a good point! I'll adjust the wording to make the quick/full tech relation clearer in version 1.1. Thanks for bringing it up.