Skip to main content

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

GeritzDev

9
Posts
44
Followers
3
Following
A member registered Jun 07, 2020 · View creator page →

Creator of

Recent community posts

Hey thanks for reaching out. Unfortunately yes, it has no effect in COMP/CON. That kind of addition would require coding on the website's side which is far beyond the scope of the supplement. Sorry about that, you'll have to track it pen and paper style.

This supplement only contains rules for players to take over control of NPC mechs on the battlefield. Specifically it covers: Taking initial control, what you are allowed to do with it, what you can do with it after combat, etc. Keep in mind, you can always introduce NPC-like things as exotic gear for your players to use on their mechs. They do not necessarily need to be part of the licensing system to be used, certain downtime actions even allow players to create their own systems after a fashion.

Glad you like it. Best of luck!

I see Unknown Npc System listed there, my guess is that somehow the json text of that particular weapon was corrupted. Should be fairly obvious once you look at the JSON file itself.

Did you delete the old NPC and lcp data from previous installs of the LCP in owlbear before installing the new one? (it could be the case that they do not cleanly overwrite each other.)

A few things to try: 

Try updating the lcp file in Comp Con, and then deleting the old NPC, before regenerating your JSON for use in owlbear.

Try making sure that the lcp file in Comp Con and Owlbear are the same version. (Delete the one in OwlBear first, and then import the newer lcp file [warning: I can't speak to whether this will automatically delete your old NPCs or if that may break them]  )

Try deleting the old NPC in Compcon . In some cases Compcon will simply save old configurations instead of checking their systems against its lcp counterpart if the NPC already exists (hence why you can rename things). Once you recreate the NPC, export a new JSON, delete the old NPC from Owlbear and import using the newly minted JSON.

I recognize this is a lot of trouble to go to just to fix one NPC. Personally I'm of the camp of living with the silliness and running off Compcon (that is my preferred way to run).

(1 edit)

Alright, so this is what I get after importing with an NPC Json pulled from compcon. As you can see, the flak cannon is in there, as well as the other traits relevant to the NPC. This was from an NPC uploaded using the Export function on CompCon which will generate a JSON file for you to import.

I am also assuming you are using witchdice which is what this sheet is based off of

Ok, so this LCP was not tested for Owlbear, I am not sure what differences might exist between the parser for that program versus compcon. So this will be something that I'll have to look into. Thank you for bringing it to my attention!

(1 edit)

Hey, thank you for the bug report! I'll get a patch out today, so keep an eye out for it.

Taking a look at it, let me download the LCP and make sure it was patched correctly, because I'm seeing it on my local copy in comp/con correctly. What platform are you using?

You move freely, but systems that rely on you sitting still are not going to function as you are counted as moving.

Changed my life