eezeebee

Miyazaki plz

Homemade crust, pepperoni, red peppers.

The crust was just flour, water and a little salt. About 1.5cm thick. Once the dough ball was consistent I coated it with more flour to prevent sticking and then pressed it down into shape.

Pepperoni was sliced off a tube. It looks kind of greasy, but it wasn't too much, and I really like that it curled up a bit. I put the oven on high broil near the end to get it to crisp up a bit.

Super underrated band. Excellent vocalist. This isn't my only obsession song of theirs, just the most recent. They are "safe" as per some quotes of the band leader I have come across.

https://dodsferdofficial.bandcamp.com/music

Hello. I'm at a point in my learning where I see potential to make a big mess and want some advice before that happens. Particularly, how to organize game systems like inventory, damage calculation, level variables (eg. locked doors -> remain unlocked even after the level scene is reloaded).

For Inventory (consumable items, weapons etc), what I've done so far that seems to work is create a global script called PlayerInventory, within it is a list of every item as a boolean variable to indicate if the player has it or not. So now when the player travels through different level scenes, their inventory is persistent and any upgrades remain. Seems to work so far.

But how would you go about doing this for a locked door in a level scene? One way is to tie it to a key, in the player inventory - if "key" == true, "locked" = false. Ok, fine. What about a wooden crate that has been destroyed by the player? How would you keep track of the crate's destroyed state without it being tied to a "key item" in the PlayerInventory global script? Is the solution to create more global scripts, like "EnvironmentChanges"? What script should be responsible for remembering this and where should it live?

With regards to a damage calculation system, I think the high level question is similar- how to organize this? The path I'm going down looks like, "DamageManager" global script which handles the calculations and updates, meanwhile the player and enemy scenes have an "HP" node added, with the "hp" value variable set by the parent (the player or that specific enemy).

I'm looking for high-level ideas about how to make these things work together and to keep it as easy to maintain and organized as possible. More details and specifics are welcome, too. Thanks

Context: I noticed I have some clothes from 10 years ago that are still good to wear, and some newer things I have barely worn yet. I wondered if I reached a point where all the clothes I own would be enough to last for the rest of my life. There is a dresser and a closet worth of things.

For the sake of this question, let's say you can't buy, borrow, steal, receive as a gift, find, or make anything new to wear. All you get is what you have now. Is it enough?

I have an extra key that came with the AGDQ Humble bundle. I love this game and would be happy to share with someone who will enjoy it.

If your Lemmy account is at least 1 month old, comment and tell me what about the game makes you want to play it.

I just think Kazakhstan is neat

Canada has implemented a new tax savings from December to February for some things like taxable groceries, crafts, and gaming physical media. I wanted to get a new Xbox controller and found the best price at Walmart for $55 a week ago. The tax holiday starts today and I now see that the $55 has increased to $62 and change, which is about how much tax I should be saving. Great to see this thinly veiled attempt to help Canadians ( /s - win votes) is just going to be extra profit in the corporations' pockets.