update
parent
057033d172
commit
c91c7f5ba6
@ -0,0 +1,56 @@
|
|||||||
|
<!--210218,210107-->
|
||||||
|
<h1>a look into my achievement system </h1>
|
||||||
|
april 2, 2021<br>
|
||||||
|
#achievements #knowledgebase <br>
|
||||||
|
<br>
|
||||||
|
Designing an achievement system without any octopus tangles.<br>
|
||||||
|
<br>
|
||||||
|
<center><img src="/static/img/ent/KB_octopus.png" alt="(image: an illustration of an octopus tangling up UI, Dialog, and other game systems.)" width="500" height="396.75"></center> <br>
|
||||||
|
<br>
|
||||||
|
<h2>what does blessfrey consider an achievement? </h2><br>
|
||||||
|
<br>
|
||||||
|
An achievement is generally an objective used to create a metagame. They can vary in difficulty from an obscure discovery to repetitive use of mechanics to basic participation in the main story. Achievements can even be entirely external to the base game's system like <a href="https://steamcommunity.com/stats/221910/achievements">The Stanley Parable's "Go outside" achievement<a>, requiring you to not play for five years. Since achievements can be earned through any in-game system, the achievement system is closely tied to all other game systems. <br>
|
||||||
|
<br>
|
||||||
|
Completing an achievement usually awards a trophy, gamer points, or possibly something more practical, like a new game mode or an in-game item. <br>
|
||||||
|
<br>
|
||||||
|
Blessfrey feeds <i>every</i> in-game interaction through its achievement system, and its reward delivery is flexible enough not only to give a trophy but to cause <i>anything</i> to happen in response. Giving a trophy for finding a secret room is technically similar to gaining a Fire Resistance skill after standing on a bed of coals for 2 minutes or opening a new store after $1000 is spent at the mall. The only difference is actually notifying the player that an achievement was completed. Ironically, even though I ignore achievements in most games, Blessfrey's achievement system has become the backbone of player progression and world events. <br>
|
||||||
|
<br>
|
||||||
|
<br>
|
||||||
|
<h2>how to design an achievement system </h2><br>
|
||||||
|
<br>
|
||||||
|
Octopus-tangling is a major design concern for a system that is so interconnected with every other system. I could scatter achievement code through every other system, but that would be a problem if I ever need to make a fundamental change to the achievement system. Also, it will clutter the other systems if each system has a bunch of achievements tacked onto the bottom. <br>
|
||||||
|
<br>
|
||||||
|
Instead, Blessfrey's achievement system, the Knowledge Base, looks more like a mailman between game progress and the achievement system. A mailman Each granular action or world event that contributes to earning an achievement is called a piece of <b>knowledge</b>, which is identified by a <b>key</b> id number. Knowledge is categorized into <b>topics</b>. <b>Event handlers</b> subscribe to topics, waiting for news that a specific piece of knowledge has been encountered. The <b>Knowledge Base</b> itself stores all knowledge and facilitates the learning and forgetting of pieces of knowledge. Event handlers subscribed to the "knowledge_learned" topic will pay out awards. The <b>MessageBus</b> is the mailman that receives information about encountered knowledge and passes it off to all event handlers subscribed to that topic. The event handlers allow me to freely make and delete achievements, and the MessageBus keeps everything separate. <br>
|
||||||
|
<br>
|
||||||
|
<br>
|
||||||
|
<h2>an example</h2><br>
|
||||||
|
<br>
|
||||||
|
Let's say you get an achievement for finding the Nurse's Office. The moment the player loads into the Nurse's Office, data will zip back and forth between the MessageBus and the nurse's office object, different event handlers and the Knowledge Base. <br>
|
||||||
|
<br>
|
||||||
|
<ol>
|
||||||
|
<li>(Event Handler) At ready, event handlers call the MessageBus and subscribe to topics. </li>
|
||||||
|
<li>(Nurse's Office) The player enters the Nurse's Office. The room object sends itself to the MessageBus. </li>
|
||||||
|
<li>(MessageBus) Receives room object + sends it to all event handlers subscribed to the "place_entered" topic. </li>
|
||||||
|
<li>(Event Handler) NursesOfficeEntered receives room object. If the room is the Nurse's Office, send its corresponding knowledge key to the MessageBus. It can also verify pre-requisites and gather additional data for the Knowledge Base. This way, the system supports anything I'd like to track about when or how knowledge was learned. </li>
|
||||||
|
<li>(MessageBus) Receives the knowledge key + sends it to the Knowledge Base. </li>
|
||||||
|
<li>(Knowledge Base) Finds the knowledge identified by the incoming key. "Learns" by setting that knowledge to true and filling in additional fields if extra data was sent. Sends the knowledge key to the MessageBus. </li>
|
||||||
|
<li>(MessageBus) Receives the knowledge key + sends it to all "learned" event handlers. </li>
|
||||||
|
<li>(Event Handler) KnowledgeLearned receives the knowledge key + calls code for any changes resulting from learning this knowledge. Maybe you'll get a Steam achievement, but if the Knowledge Base was being to facilitate game progression, a quest could update, the dialog system could unlock the option to ask about the Nurse's Office, or you could gain a Codex entry about the new location. The changes can be conditional, too, so the handler can track whether all necessary keys have been received before enacting the change. </li>
|
||||||
|
</ol><br>
|
||||||
|
<br>
|
||||||
|
To use the achievement system for cyclical world events, you could trigger knowledge to be "forgotten" or ultimately set back to false in the Knowledge Base. This way, the phases of an event could begin anew. <br>
|
||||||
|
<br>
|
||||||
|
<br>
|
||||||
|
<h2>summary</h2><br>
|
||||||
|
<br>
|
||||||
|
Achievements can come from any combination of in-game actions, so an achievement system should be designed separately from the rest of the game. I achieve this through a couple of separate objects. <br>
|
||||||
|
<br>
|
||||||
|
<ul>
|
||||||
|
<li>Event Handlers: The tracking, verifying, and reward payout should be contained within event handlers, which can be generated and freed as needed. They subscribe to general topics and wait for their specific event to occur. </li>
|
||||||
|
<li>The Knowledge Base tracks the status of all knowledge in the game and can be used to understand how far the player and world have progressed. </li>
|
||||||
|
<li>The MessageBus is very light and only allows event handlers to subscribe to topics and for incoming message to be transmitted through that topic. It has absolutely no unique checks or code to execute, impartially delivering mail to the address on the envelope. </li>
|
||||||
|
<li>Another set of event handlers is concerned about the outcome of encountering and learning knowledge and can prompt changes or directly impact other systems, depending on pre-requisites met. </li>
|
||||||
|
<br>
|
||||||
|
<br>
|
||||||
|
Last updated April 2, 2021 <br>
|
||||||
|
<br>
|
@ -0,0 +1,37 @@
|
|||||||
|
<!--210218,210107-->
|
||||||
|
<h1>designing a tutorial with bingo cards </h1>
|
||||||
|
april 15, 2021<br>
|
||||||
|
#gamedesign #tutorial<br>
|
||||||
|
<br>
|
||||||
|
Give your players more freedom during the tutorial by having them play bingo. <br>
|
||||||
|
<br>
|
||||||
|
<h2>what's bingo? </h2><br>
|
||||||
|
<br>
|
||||||
|
Bingo is a game where the player is given a card with a grid filled with random squares. Someone will call out squares, and the player will cover the called squares with tokens. The goal is to fill a line of squares with tokens: a diagonal, a horizontal, or a vertical. Sometimes the game is played until a full card is covered. Since each card has different squares, it's a game of chance. <br>
|
||||||
|
<br>
|
||||||
|
Bingo's a popular gambling game in America, but it can be modified into an educational game, too. My music class played spurts of classical music in lieu of calling squares, so we had to identify the instrument in order to cover squares. <br>
|
||||||
|
<br>
|
||||||
|
<br>
|
||||||
|
<h2>using bingo to design a videogame </h2><br>
|
||||||
|
<br>
|
||||||
|
I like the bingo board as a game world because there are multiple paths to winning the game. The design of the board strikes a nice balance between game designer choice and player choice. The player is free to choose their own board based on their own criteria, but the designer ensured each board is reasonably equal. There's no board with 24 B4 squares on it, for instance. <br>
|
||||||
|
<br>
|
||||||
|
This balance of freedom and control is great for something like a game tutorial. Usually, tutorials are set in extremely confined areas with strong limits on player exploration and choice. That's a good idea in theory because it will teach the player exactly what he needs to know at a pace that won't overwhelm him, but it's boring in practice. <br>
|
||||||
|
<br>
|
||||||
|
You can think of a traditional tutorial as a row of squares on a bingo card. The squares are probably something like "move forward," "talk to an NPC," "double jump," "equip gun," and "hit the bulls-eye." If that was only one line on the board and all the other lines were filled with similar objectives, the player has a little more freedom to choose their own tutorial. The designer retains control over what the player learns because he can ensure each line is reasonably equal in its ability to prepare the player for the real game. The designer loses control of the order in which tasks are completed, but it's guaranteed that the player finished a complete set of tasks. <br>
|
||||||
|
<br>
|
||||||
|
<h2>blessfrey bingo </h2><br>
|
||||||
|
<br>
|
||||||
|
<center><img src="/static/img/ent/blessfreybingo.png" alt="(image: a bingo card filled with game objectives like Visit Nurse's Office, Talk to Chloe, Win a Sparring Match, and Buy Cheese Crackers.)"></center> <br>
|
||||||
|
<br>
|
||||||
|
To play the main content in Blessfrey, the player needs to have basic knowledge of combat, dialog, different characters, and different areas on the map. There's also less vital information that the player should encounter quickly, like shopping, using phone apps, and randomized loot. So, almost every line has some basic combat, character interaction, and zone exploration. There's some more obscure tasks scattered around to hint at what kind of things are possible in the game. <br>
|
||||||
|
<br>
|
||||||
|
<h2>bingo and the players </h2><br>
|
||||||
|
<br>
|
||||||
|
If you physically present the full card to the players, they will respond differently. Completionists might want to cover the entire board before leaving the tutorial area, so it would be fun to reward them. 1 bingo is a ticket out of Tutorial Land, but there can be further rewards for additional bingos and a big prize for the full board. Speedrunners (any%) are going to figure out which path is the fastest and only take that one. Most players are probably going to explore at their own pace and complete the objectives that seem easy or cool, though. <br>
|
||||||
|
<br>
|
||||||
|
<h2>in closing </h2><br>
|
||||||
|
So long as the board and potential rewards are balanced, why not consider taking some inspiration from a bingo board when designing your tutorial? There doesn't have to be a literal board anywhere. The idea of alternate but equal paths to completing a tutorial already brings in more potential for player choice while retaining designer control. <br>
|
||||||
|
<br>
|
||||||
|
Last updated April 15, 2021 <br>
|
||||||
|
<br>
|
@ -0,0 +1,31 @@
|
|||||||
|
<!--210401,210601-->
|
||||||
|
<h1>may 2020: AI</h1>
|
||||||
|
may 1, 2021<br>
|
||||||
|
<br>
|
||||||
|
<br>
|
||||||
|
<h2>week 1, april 1 - 3 </h2><br>
|
||||||
|
# <br>
|
||||||
|
<br>
|
||||||
|
<h3>thursday, april 1 - April Fool's Day </h3>
|
||||||
|
<ul>
|
||||||
|
<li>I got gnomed by a group leader, and FlightRising's rotated dragons made me think my graphics card was broken. I'm the April Fool. </li>
|
||||||
|
<li>To be fair, my graphics card did spark yesterday. It was scary. ;-; </li>
|
||||||
|
</ul>
|
||||||
|
<br>
|
||||||
|
<h3>friday, april 2 </h3>
|
||||||
|
<ul>
|
||||||
|
<li>maintained blessfrey.me. I like my website and it's starting to get a nice amount of content on it. I should do a graphics update sometime and make the diary and diary snippets pretty. I should at least choose my own color scheme instead of still using the first few colors <a href="https://coolors.co/">Coolors</a> gave me. </li>
|
||||||
|
</ul>
|
||||||
|
<br>
|
||||||
|
<h3>wednesday, april 13 </h3>
|
||||||
|
<ul>
|
||||||
|
<li>I've been writing and drawing a lot lately. </li>
|
||||||
|
<li>I feel more comfortable defining the mayor's character, which is great because she's a major antagonist. She's supposed to be somewhat close in age and maturity to the teen protagonists, despite being in control of a city. I like the idea of a manchild leader with a powerful artifact. Since I'm not necessarily comfortable with writing conflicts between her and the main characters as life-or-death maximum evil encounters, I've been coming up with other stakes for the cast. It should be more like my-valuables-at-risk maximum petty encounters. </li>
|
||||||
|
<li>I even have an idea what her name should be. Since the player's default name is Helia (a sun name), I want the mayor to have a moon name. Celeste and Selene feel overused in fantasy, so I was considering Chandra (is that too Hindi? It has a strong local association with the Chandra space mission + it sounds like the boomer name Shondra), Charon, Lunette, Dione, Liviana, and Mona... </li>
|
||||||
|
</ul>
|
||||||
|
<br>
|
||||||
|
<h3>thursday, april 14 </h3>
|
||||||
|
<ul>
|
||||||
|
<li>I'm partially vaccinated against COVID now. It hurts... More Americans are eligible for the vaccines, so maybe you can get one now, too. </li>
|
||||||
|
</ul>
|
||||||
|
<br>
|
Binary file not shown.
After Width: | Height: | Size: 617 KiB |
Binary file not shown.
After Width: | Height: | Size: 417 KiB |
Binary file not shown.
After Width: | Height: | Size: 203 KiB |
Binary file not shown.
After Width: | Height: | Size: 456 KiB |
@ -0,0 +1,115 @@
|
|||||||
|
<?xml version="1.0" encoding="utf-8"?>
|
||||||
|
<rss version="2.0">
|
||||||
|
<channel>
|
||||||
|
<title>blessfrey.me</title>
|
||||||
|
<link>https://www.blessfrey.me/</link>
|
||||||
|
<description>chimchooree's dev space</description>
|
||||||
|
<language>en-us</language>
|
||||||
|
<webMaster>chimchooree@mail.com (chimchooree)</webMaster>
|
||||||
|
<item>
|
||||||
|
<title>designing a tutorial with bingo cards </title>
|
||||||
|
<link>https://www.blessfrey.me/diary/entries/210415</link>
|
||||||
|
<description>Give your players more freedom during the tutorial by having them play bingo. what's bingo? Bingo ... </description>
|
||||||
|
<pubDate>Thu, 15 Apr 2021 05:00:05 GMT</pubDate>
|
||||||
|
<guid>https://www.blessfrey.me/diary/entries/210415</guid>
|
||||||
|
</item>
|
||||||
|
<item>
|
||||||
|
<title>a look into my achievement system </title>
|
||||||
|
<link>https://www.blessfrey.me/diary/entries/210402</link>
|
||||||
|
<description>Designing an achievement system without any octopus tangles. what does blessfrey consider an ... </description>
|
||||||
|
<pubDate>Fri, 02 Apr 2021 05:00:05 GMT</pubDate>
|
||||||
|
<guid>https://www.blessfrey.me/diary/entries/210402</guid>
|
||||||
|
</item>
|
||||||
|
<item>
|
||||||
|
<title>march 2020: AI</title>
|
||||||
|
<link>https://www.blessfrey.me/diary/entries/210401</link>
|
||||||
|
<description>week 1, february 28 - march 6 #ai #webdev monday, march 1 I went on a walk for 3 hours. ... </description>
|
||||||
|
<pubDate>Thu, 01 Apr 2021 05:00:05 GMT</pubDate>
|
||||||
|
<guid>https://www.blessfrey.me/diary/entries/210401</guid>
|
||||||
|
</item>
|
||||||
|
<item>
|
||||||
|
<title>generating an RSS feed with python bottle</title>
|
||||||
|
<link>https://www.blessfrey.me/diary/entries/210318</link>
|
||||||
|
<description>After a few months of quietly running my blog as practice, I want to start sharing my articles with ... </description>
|
||||||
|
<pubDate>Thu, 18 Mar 2021 05:00:05 GMT</pubDate>
|
||||||
|
<guid>https://www.blessfrey.me/diary/entries/210318</guid>
|
||||||
|
</item>
|
||||||
|
<item>
|
||||||
|
<title>python writes my skills for me</title>
|
||||||
|
<link>https://www.blessfrey.me/diary/entries/210304</link>
|
||||||
|
<description>Similar to Magic: The Gathering cards, the functionality of my skills is composed of keywords. For ... </description>
|
||||||
|
<pubDate>Thu, 04 Mar 2021 05:00:05 GMT</pubDate>
|
||||||
|
<guid>https://www.blessfrey.me/diary/entries/210304</guid>
|
||||||
|
</item>
|
||||||
|
<item>
|
||||||
|
<title>february 2020: AI</title>
|
||||||
|
<link>https://www.blessfrey.me/diary/entries/210301</link>
|
||||||
|
<description>I just feel like rambling about games. week 1, february 1-6 #design #localization #writing tuesday, ... </description>
|
||||||
|
<pubDate>Mon, 01 Mar 2021 05:00:05 GMT</pubDate>
|
||||||
|
<guid>https://www.blessfrey.me/diary/entries/210301</guid>
|
||||||
|
</item>
|
||||||
|
<item>
|
||||||
|
<title>refactoring characters: black box </title>
|
||||||
|
<link>https://www.blessfrey.me/diary/entries/210218</link>
|
||||||
|
<description>The character script was one of blessfrey's first scripts. Since it's never seen a serious ... </description>
|
||||||
|
<pubDate>Thu, 18 Feb 2021 05:00:05 GMT</pubDate>
|
||||||
|
<guid>https://www.blessfrey.me/diary/entries/210218</guid>
|
||||||
|
</item>
|
||||||
|
<item>
|
||||||
|
<title>new year's resolution - making the most of 2021 </title>
|
||||||
|
<link>https://www.blessfrey.me/diary/entries/210204</link>
|
||||||
|
<description>Everyone had difficulties during 2020. A small part of that was losing my energy for programming ... </description>
|
||||||
|
<pubDate>Thu, 04 Feb 2021 05:00:05 GMT</pubDate>
|
||||||
|
<guid>https://www.blessfrey.me/diary/entries/210204</guid>
|
||||||
|
</item>
|
||||||
|
<item>
|
||||||
|
<title>january 2020: new year</title>
|
||||||
|
<link>https://www.blessfrey.me/diary/entries/210201</link>
|
||||||
|
<description>week 1, january 1-2 friday, january 1 - New Year's2020 is over. Things probably won't be ... </description>
|
||||||
|
<pubDate>Mon, 01 Feb 2021 05:00:05 GMT</pubDate>
|
||||||
|
<guid>https://www.blessfrey.me/diary/entries/210201</guid>
|
||||||
|
</item>
|
||||||
|
<item>
|
||||||
|
<title>web development resources</title>
|
||||||
|
<link>https://www.blessfrey.me/diary/entries/210121</link>
|
||||||
|
<description>I'll collect frequently used resources for web design here. CSS Grid Generator - build a ... </description>
|
||||||
|
<pubDate>Thu, 21 Jan 2021 05:00:05 GMT</pubDate>
|
||||||
|
<guid>https://www.blessfrey.me/diary/entries/210121</guid>
|
||||||
|
</item>
|
||||||
|
<item>
|
||||||
|
<title>inventory as a system diagram </title>
|
||||||
|
<link>https://www.blessfrey.me/diary/entries/210107</link>
|
||||||
|
<description>System diagrams illustrate how components interact within a system. It saves so much headache to ... </description>
|
||||||
|
<pubDate>Thu, 07 Jan 2021 05:00:05 GMT</pubDate>
|
||||||
|
<guid>https://www.blessfrey.me/diary/entries/210107</guid>
|
||||||
|
</item>
|
||||||
|
<item>
|
||||||
|
<title>december 2020: holiday season☆</title>
|
||||||
|
<link>https://www.blessfrey.me/diary/entries/210101</link>
|
||||||
|
<description>I didn't keep a diary very well this month;; This is mostly pieced together from my git history. I ... </description>
|
||||||
|
<pubDate>Fri, 01 Jan 2021 05:00:05 GMT</pubDate>
|
||||||
|
<guid>https://www.blessfrey.me/diary/entries/210101</guid>
|
||||||
|
</item>
|
||||||
|
<item>
|
||||||
|
<title>blessfrey graphic updates + mockups </title>
|
||||||
|
<link>https://www.blessfrey.me/diary/entries/201224</link>
|
||||||
|
<description>I iterate over the graphics periodically, so I can practice without worrying about polish. Here's ... </description>
|
||||||
|
<pubDate>Thu, 24 Dec 2020 05:00:05 GMT</pubDate>
|
||||||
|
<guid>https://www.blessfrey.me/diary/entries/201224</guid>
|
||||||
|
</item>
|
||||||
|
<item>
|
||||||
|
<title>common tropes from media </title>
|
||||||
|
<link>https://www.blessfrey.me/diary/entries/201210</link>
|
||||||
|
<description>I like collecting common tropes from games I play. Maybe it can it root out cliches? Or inspire ... </description>
|
||||||
|
<pubDate>Thu, 10 Dec 2020 05:00:05 GMT</pubDate>
|
||||||
|
<guid>https://www.blessfrey.me/diary/entries/201210</guid>
|
||||||
|
</item>
|
||||||
|
<item>
|
||||||
|
<title>november 2020: dear diary </title>
|
||||||
|
<link>https://www.blessfrey.me/diary/entries/201201</link>
|
||||||
|
<description>on topic Between the 8th and 15th, I wrote a Python script for generating Godot skill scenes from ... </description>
|
||||||
|
<pubDate>Tue, 01 Dec 2020 05:00:05 GMT</pubDate>
|
||||||
|
<guid>https://www.blessfrey.me/diary/entries/201201</guid>
|
||||||
|
</item>
|
||||||
|
</channel>
|
||||||
|
</rss>
|
@ -1,100 +0,0 @@
|
|||||||
<?xml version="1.0" encoding="utf-8"?>
|
|
||||||
<rss version="2.0">
|
|
||||||
<channel>
|
|
||||||
<title>blessfrey.me</title>
|
|
||||||
<description>chimchooree's dev space</description>
|
|
||||||
<link>https://www.blessfrey.me/</link>
|
|
||||||
<language>en-us</language>
|
|
||||||
<webMaster>chimchooree@mail.com</webMaster>
|
|
||||||
<item>
|
|
||||||
<title>python writes my skills for me</title>
|
|
||||||
<link>https://www.blessfrey.me/diary/entries//diary/entries/210304</link>
|
|
||||||
<description>Similar to Magic: The Gathering cards, the functionality of my skills is composed of keywords. For ... </description>
|
|
||||||
<pubDate>Mon, 22 Feb 2021 19:01 EST</pubDate>
|
|
||||||
</item>
|
|
||||||
<item>
|
|
||||||
<title>february 2020: AI</title>
|
|
||||||
<link>https://www.blessfrey.me/diary/entries//diary/entries/210301</link>
|
|
||||||
<description>I just feel like rambling about games. week 1, february 1-6 #design #localization #writing tuesday, ... </description>
|
|
||||||
<pubDate>Mon, 22 Feb 2021 19:01 EST</pubDate>
|
|
||||||
</item>
|
|
||||||
<item>
|
|
||||||
<title>refactoring characters: black box </title>
|
|
||||||
<link>https://www.blessfrey.me/diary/entries//diary/entries/210218</link>
|
|
||||||
<description>The character script was one of blessfrey's first scripts. Since it's never seen a serious ... </description>
|
|
||||||
<pubDate>Mon, 22 Feb 2021 19:01 EST</pubDate>
|
|
||||||
</item>
|
|
||||||
<item>
|
|
||||||
<title>new year's resolution - making the most of 2021 </title>
|
|
||||||
<link>https://www.blessfrey.me/diary/entries//diary/entries/210204</link>
|
|
||||||
<description>Everyone had difficulties during 2020. A small part of that was losing my energy for programming ... </description>
|
|
||||||
<pubDate>Mon, 22 Feb 2021 19:01 EST</pubDate>
|
|
||||||
</item>
|
|
||||||
<item>
|
|
||||||
<title>january 2020: new year</title>
|
|
||||||
<link>https://www.blessfrey.me/diary/entries//diary/entries/210201</link>
|
|
||||||
<description>week 1, january 1-2 friday, january 1 - New Year's2020 is over. Things probably won't be ... </description>
|
|
||||||
<pubDate>Mon, 22 Feb 2021 19:01 EST</pubDate>
|
|
||||||
</item>
|
|
||||||
<item>
|
|
||||||
<title>web development resources</title>
|
|
||||||
<link>https://www.blessfrey.me/diary/entries//diary/entries/210121</link>
|
|
||||||
<description>I'll collect frequently used resources for web design here. CSS Grid Generator - build a ... </description>
|
|
||||||
<pubDate>Mon, 22 Feb 2021 19:01 EST</pubDate>
|
|
||||||
</item>
|
|
||||||
<item>
|
|
||||||
<title>inventory as a system diagram </title>
|
|
||||||
<link>https://www.blessfrey.me/diary/entries//diary/entries/210107</link>
|
|
||||||
<description>System diagrams illustrate how components interact within a system. It saves so much headache to ... </description>
|
|
||||||
<pubDate>Mon, 22 Feb 2021 19:01 EST</pubDate>
|
|
||||||
</item>
|
|
||||||
<item>
|
|
||||||
<title>december 2020: holiday season☆</title>
|
|
||||||
<link>https://www.blessfrey.me/diary/entries//diary/entries/210101</link>
|
|
||||||
<description>I didn't keep a diary very well this month;; This is mostly pieced together from my git history. I ... </description>
|
|
||||||
<pubDate>Mon, 22 Feb 2021 19:01 EST</pubDate>
|
|
||||||
</item>
|
|
||||||
<item>
|
|
||||||
<title>blessfrey graphic updates + mockups </title>
|
|
||||||
<link>https://www.blessfrey.me/diary/entries//diary/entries/201224</link>
|
|
||||||
<description>I iterate over the graphics periodically, so I can practice without worrying about polish. Here's ... </description>
|
|
||||||
<pubDate>Mon, 22 Feb 2021 19:01 EST</pubDate>
|
|
||||||
</item>
|
|
||||||
<item>
|
|
||||||
<title>common tropes from media </title>
|
|
||||||
<link>https://www.blessfrey.me/diary/entries//diary/entries/201210</link>
|
|
||||||
<description>I like collecting common tropes from games I play. Maybe it can it root out cliches? Or inspire ... </description>
|
|
||||||
<pubDate>Mon, 22 Feb 2021 19:01 EST</pubDate>
|
|
||||||
</item>
|
|
||||||
<item>
|
|
||||||
<title>november 2020: dear diary </title>
|
|
||||||
<link>https://www.blessfrey.me/diary/entries//diary/entries/201201</link>
|
|
||||||
<description>on topic Between the 8th and 15th, I wrote a Python script for generating Godot skill scenes from ... </description>
|
|
||||||
<pubDate>Mon, 22 Feb 2021 19:01 EST</pubDate>
|
|
||||||
</item>
|
|
||||||
<item>
|
|
||||||
<title>pretendOS - a game inspired by windows XP </title>
|
|
||||||
<link>https://www.blessfrey.me/diary/entries//diary/entries/201126</link>
|
|
||||||
<description>Getting started with blessfrey's AI was overwhelming, so I took a break and worked on a new game. I ... </description>
|
|
||||||
<pubDate>Mon, 22 Feb 2021 19:01 EST</pubDate>
|
|
||||||
</item>
|
|
||||||
<item>
|
|
||||||
<title>tidying up my skill phases </title>
|
|
||||||
<link>https://www.blessfrey.me/diary/entries//diary/entries/201112</link>
|
|
||||||
<description>In Godot Engine, you can call methods from a parent class by prefixing it with a period (.). So to ... </description>
|
|
||||||
<pubDate>Mon, 22 Feb 2021 19:01 EST</pubDate>
|
|
||||||
</item>
|
|
||||||
<item>
|
|
||||||
<title>october 2020: a blog that works</title>
|
|
||||||
<link>https://www.blessfrey.me/diary/entries//diary/entries/201101</link>
|
|
||||||
<description>week 1 #bottle #python #regularexpression #website thursday, october 1 blessfrey.me's diary ... </description>
|
|
||||||
<pubDate>Mon, 22 Feb 2021 19:01 EST</pubDate>
|
|
||||||
</item>
|
|
||||||
<item>
|
|
||||||
<title>blessfrey in japanese </title>
|
|
||||||
<link>https://www.blessfrey.me/diary/entries//diary/entries/201029</link>
|
|
||||||
<description>Instead of hard-coding text, keep it in a spreadsheet instead. It's easier to organize, edit, and ... </description>
|
|
||||||
<pubDate>Mon, 22 Feb 2021 19:01 EST</pubDate>
|
|
||||||
</item>
|
|
||||||
</channel>
|
|
||||||
</rss>
|
|
Loading…
Reference in New Issue