One Hour One Life Forums

Getting banned isn't so much brought on by doing something bad - we all make mistakes, that's why we give warnings and such - it's more brought on by repeat offences. Repeated spam messages, constantly provoking arguments, repeatedly going off topic to the detriment of the running conversation etc.

Another thing that might get someone in trouble is constantly arguing with mods and throwing massive public tantrums about their decision.

I think knowing the coordinates is an exploit as well. It can be fairly easily obfuscated too, so I might log a suggestion on github for it.

This solution is brilliant in its simplicity and embraces the best of the current system and RNG. I don't think you need to panic about Jason paving over cracks and having to refactor everything at increased cost later. This change is miniscule in terms of code change, but adds a whole lot of depth to the game. It's almost cheating, really. But worst case, if he has to come up with a better system later, it won't be any harder to refactor anything.

Edit: TMPL (today my phone learned) refactor is a word.

Sorry for losing my cool. This is exactly why I say that I don't know how Jason stays so calm. I'm not sorry for defending him, however.

I'm sorry you have to deal with this kind of shit, Jason. I have no idea how you stay so calm and patient with morons like this. I'm not the dev here, so I can say what I want about these people.

"Y'all are fucking dicks."

Yeah, I'm not getting it either. Soil found in the wild is finite. Compost now requires a shovel of dung and doesn't even involve a worm at all. The only use for a worm is to turn hardened soil back into a tilled row, allowing you to plant more crops. Those crops are either berries, and the soil is forever consumed, or wheat, which also consumes the soil, or carrots, whose naturally occuring seeds are finite and whose domestic seeds dun dun dun, consume the soil.

So yeah, I'm totally not getting it either.

Also worth noting is that Jason identified in that message that an ax breaking on first use due to RNG would be a problem, and then proceeded to NOT implement RNG. So that "meme" is patently false.

One advantage (in my opinion it's an advantage) about the RNG is that you can't predict exactly when things will break. You can plan based on averages, but there will always be variation. I say this is an advantage because there are players like myself who always math things out. I mean, look at the very early days. Remember "three to feed, one to seed"? All mathed out. You end up working out a perfect formula that you redo every time. At first this is quite satisfying, because you feel like you've "cracked it", but it gets very boring after a while. One way to combat this is to constantly change everything (which seems to work just fine for you, Jason ^_^ ) or to have some things unpredictable, like RNG. For me, it liberates me from the mental burden of "how many times have I used this? I need three axes to keep my forge going for seventeen minutes, bla bla bla". When I play my mod, I just do things.

I think it's okay to have some hidden information.

Having already implemented this solution in my mod, I can tell you it is very simple and it works. As for the main concern around things breaking on first use, when things break in my mod, if they break outright, then they are easily replaced and there are more durable tools that can perform the same task, or they don't break completely but instead become unusable until they are restored. An example of the first category: sharp stone, has a 1 in 10 chance to break completely, but all of its uses can be performed with a kinfe or chisel, so once you have those, you don't need sharp stones any more, and until you do, there are plenty of them around. An example of the second category is the cast copper ax, which has a more than 50% chance to "break", but when it does, it goes blunt and can be sharpened with a whetstone or file. This is the same for all of the tools, but better quality tools blunt less frequently. When you sharpen the tool, then there is a chance for it to break completely, and there is also a chance for the sharpening tool to break as well, so things do eventually run out, but it's not so sudden. And when metal tools do break completely, you can salvage some of the metal and re-use it.

Summary of that paragraph is that RNG doesn't have to be completely brutal. There are ways to soften the blow, so don't consider the current tool life cycle and just chuck RNG in the mix.

On to the deeper issues: having any kind of randomness in transitions is a HUGE paradigm shift. I did it because it was simple and I can do what I want when I'm not the guy with the thousands of players to keep happy. Personally I think it works, but it is a very different play style. I'm not sure it is the best approach for the base game. Before implementing it, you should actually assess the impact of just using the current system. Is it really so bad to have an extra thousand transitions in memory? How does it affect performance? Is the cost just a little extra RAM? If so, isn't that acceptable?

Maybe you could spin up a branch implementing the second transition generation cycle with some high-use objects and transitions and deploy it to a new server and get some playtesting going on to see what the figures are. I think that would help make an informed decions before doing anything rash.

A github issue has been raised.