{
"$type": "site.standard.document",
"content": {
"$type": "blog.pckt.content",
"items": [
{
"$type": "blog.pckt.block.text",
"plaintext": "Please note that this project has now been renamed from 31 Characters in 31 Days to \"Oh The People You Shall Meet\" which is a much more me title for this. I will admit to being behind on my character creation but not in an insurmountable amount. I will say I have officially given all 31 characters first names, and several of them last names. "
},
{
"$type": "blog.pckt.block.text",
"plaintext": "I'm weighing the pros/cons of also including physical descriptions which you might think are a given when creating a character but I don't know if I want to paint a mental picture for people of every one of the characters if for no other reason than to give the user flexibility when fitting a character into their game. Because this is supposed to be system agnostic if I describe someone say as an Elf but the game in question doesn't have elves then what? See my conundrum? If only some of them have descriptions then I can sort of hit the \"major\" fantasy & sci-fi descriptions and then leave the rest up to the end user. However at the same time that also feels lazy? I'm also playing with the idea of making a list of 30 that is simply feminine, masculine, and ambiguous descriptions that the end user can simply pick from and assign to whatever character they need to use that fits their settings. Dear readers do you have thoughts one way or another? Suggestions? Or to just tell me I'm overthinking this whole thing and to just write 31 descriptions for each character and let the end user choose if they use them or not. Which is of course the obvious choice to make."
},
{
"$type": "blog.pckt.block.text",
"plaintext": "Right now the things I'm writing for each character is, their name (first and maybe last), at least one thing they're known for, what they're general goals are, interaction tactics (which also include notes about what happens if they end up in combat but again its system agnostic so its more description/narrative then actual concrete mechanical tactics), a secret they hold (either their own or about something else), and where they are most likely to be found. I'm also playing with the idea of including the standard wants/needs/obstacles that exist in basically every narrative character creation template. You know just for funzy. But I don't want to give myself MORE work. 31 characters while doable is still a lot of characters to try to make unique and interesting. "
},
{
"$type": "blog.pckt.block.text",
"plaintext": "Thanks for checking out this devlog. Please look forward to the release of \"Oh The People You Shall Meet\" at the end of the jam."
}
]
},
"coverImage": {
"$type": "blob",
"ref": {
"$link": "bafkreibisucwwjtsjou644qti5v2tz7elj36kdvgpcm363htaiyusxflr4"
},
"mimeType": "image/png",
"size": 88450
},
"description": "Please note that this project has now been renamed from 31 Characters in 31 Days to Oh The People You Shall Meet which is a much more me title for this. I will admit to being behind on my character creation but not in an insurmountable amount. I will say I have officially given all 31 characters first names, and several of them last names. I'm weighing the pros/cons of also including physical descriptions which you might think are a given when creating a character but I don't know if I want to p...",
"langs": [
"en"
],
"path": "/oh-the-people-you-shall-meet-devlog-02-ue4ag9n",
"publishedAt": "2026-05-13T12:00:00.000Z",
"site": "at://did:plc:sgty4g46w67iqwdhrzbgfz3m/site.standard.publication/3mpc57yrxyqow",
"tags": [],
"textContent": "Please note that this project has now been renamed from 31 Characters in 31 Days to \"Oh The People You Shall Meet\" which is a much more me title for this. I will admit to being behind on my character creation but not in an insurmountable amount. I will say I have officially given all 31 characters first names, and several of them last names. \nI'm weighing the pros/cons of also including physical descriptions which you might think are a given when creating a character but I don't know if I want to paint a mental picture for people of every one of the characters if for no other reason than to give the user flexibility when fitting a character into their game. Because this is supposed to be system agnostic if I describe someone say as an Elf but the game in question doesn't have elves then what? See my conundrum? If only some of them have descriptions then I can sort of hit the \"major\" fantasy & sci-fi descriptions and then leave the rest up to the end user. However at the same time that also feels lazy? I'm also playing with the idea of making a list of 30 that is simply feminine, masculine, and ambiguous descriptions that the end user can simply pick from and assign to whatever character they need to use that fits their settings. Dear readers do you have thoughts one way or another? Suggestions? Or to just tell me I'm overthinking this whole thing and to just write 31 descriptions for each character and let the end user choose if they use them or not. Which is of course the obvious choice to make.\nRight now the things I'm writing for each character is, their name (first and maybe last), at least one thing they're known for, what they're general goals are, interaction tactics (which also include notes about what happens if they end up in combat but again its system agnostic so its more description/narrative then actual concrete mechanical tactics), a secret they hold (either their own or about something else), and where they are most likely to be found. I'm also playing with the idea of including the standard wants/needs/obstacles that exist in basically every narrative character creation template. You know just for funzy. But I don't want to give myself MORE work. 31 characters while doable is still a lot of characters to try to make unique and interesting. \nThanks for checking out this devlog. Please look forward to the release of \"Oh The People You Shall Meet\" at the end of the jam.",
"title": "Oh The People You Shall Meet | Devlog 02",
"updatedAt": "2026-07-08T03:43:13.000Z"
}