One Hour One Life Forums

If I ever find a curse note, I immediately take it far away from town and hide it. This kind of thing should not be possible.

I think the ponds actually get up and walk around as if they're a penguin, then turn back into a pond again. Not sure if that's the root cause, but that's my best guess.

Here's potential way you could implement it so that you get 32-bits of data instead of 15: make a writable object able to hold a single object, similar to a container, but the item it's holding is not treated as an item, but just as a 32-bit ID that you can use to look up entries in your writing table. You can't remove the object that your writable object is containing, and it gets created with an auto-incremented ID when the writable object is first created.

Then any object can contain one or more writing-IDs, the IDs will move around with their object the same way containers work, and then you'll be able to have 4 billion different writing entries per server, instead of 32k.

It's a pretty ugly hack, so probably don't do it this way. I can see pitfalls with server code thinking a writing-ID is a carrot, and tracking it under food stats, so you'd have to have code that asks if it's a real ID or a writable ID based on whether it's in a special container spot. It's also not very general, and would take some work to make objects able to contain things other than regular IDs and writing IDs.

To solve this, you could use the upper bits of the object ID to specify what type of object it is (0, for regular, 1 for writing, 2... and so on), that way at least you don't have to check whether its in a special container slot, and there's no way your code would think a writing object is a carrot. Depending on how many different object ID types you'd want, you'd only lose the upper few bits, so you'd still get way more than 32k different writing-IDs (not to mention way more than 130k regular IDs too) with this method.

I thought about this, but neither of these suggestions would really work. To "free the noobs" you need a tutorial to spawn above you, which doesn't always happen, or you need one below you to not already be completed. Both of these are not guaranteed, so adding an element of randomness to the end of the speedrun is not really a good thing.

Making a cart could be a potentially good extra challenge, maybe as a separate extra% category, but it also has its problems. To make a cart you need a goose to oil a file. There's no guaranteed goose nearby the tutorial, so many runs would die just by chance from not having one spawn close-by. This could be solved by playing on localhost and always spawning with a set seed, but that opens a whole new kettle of fish.

Really, breaking the stump is the only good place to end the speedrun. Any earlier and you're not really "out" and any later is a pretty arbitrary choice that only really adds randomness and uncertainty to a completely non-random run.

I was the one who made like three knives. I thought it would be funny to make both knives and medical supplies. Hopefully the Luck's last a while. Looking at the family tree they're at generation 9 right now.

That's why I saw a bunch of wounds on the ground near my town. Fantastic.