One Hour One Life Forums

Done!

Okay, pie bites are now showing up in the food log correctly.  I also went back and edited the incorrect logs from the past.

Thank you for these reports!

The basket going in the backpack before was a bug that has been fixed.  The problem is that it is a sub-container when that happens (a container in a container), but clothing when worn doesn't support sub-containers.

It was an oversight of mine... the basket was never supposed to be able to fit in the backpack!

I intended for you to mince everything together, sort of as a mixing step, after all the ingredients are in.  After all, when would the carrot be minced if you put it in later?  And allowing separate mincing steps makes it too complicated to implement (pies are already a combinatoric explosion as it is).

Will fix the food log for bites of pie.  I think it's currently only counting the first bite for some reason...

And yes, feathers and fletching should go into containers.  I will fix that.

Yeah, I will certainly be on the lookout for degenerate behavior of all kinds once there are loads of people playing.  I also have full birth/death logs going back throughout the entire history of the game, so I can make little graphs that show male vs female survival rate, life expectancy, infant mortality, population fraction, and so on.

Well, there IS a cost for a baby that suicides, if the baby is itself engaged in long-term thinking.  The baby took 10 food from the colony, and when they respawn, they take another 10.  Now, if they respawn in colony B, they've now given B an advantage against A (A took a 10-food hit for nothing).  But if they respawn in the same colony...  they've made themselves cost twice as much to the colony that they will eventually inherit.

And if babies are so precious, as you posit they are, and females are thus so valued, then males are valued for exactly the same reason.  Females need to do everything in their power to make sure every baby survives.  A long journey while pulling a cart while you have a baby out there means either that you leave the cart behind or leave the baby behind.  Either choice isn't great.  Whereas a male doesn't have to worry about that.

I experienced this myself, as a male, in the most recent playtest.  We REALLY needed milkweed, so I took a basket of carrots and set out.  My journey was more than one basket of carrots away (I found some along the way), and I needed to revisit passed carrot spots on the way back, since my basket was full of rope.  But after about 15 minutes, I made it home with rope, and we could finally make a snare.  And I was never stricken with a baby along the way.  In fact, at the wrong moment along the journey, a birth might have killed me.  And I would certainly have struggled to get that baby home safely.  (And of course, I would have left my basket behind, making my whole life pretty much a waste).

I guess we could run the two-tribes thought experiment.

Clearly, a tribe that lets all female babies die is doomed in the long run.

What about two tribes, one of which lets all male babies die, and the other that keeps all male babies, so their population is 50/50?  What about a third tribe that lets half of male babies die, so their population is 66/33?

The all-female tribe will likely "waste" some of their future babies on long journeys, and also waste 10 food per male baby.  Not to mention adding to their "bad mother" limit for each baby that dies, though over the long haul, they might get a larger share of incoming babies, because they have a larger share of females.

Also, what happens during a war?

A somewhat simple twist here would be to limit the lifetime fertility of each woman.  Forget the bad mother limit... maybe you only GET 5 babies total throughout your life.  Then each male you let die wastes more than just food, and also you're rolling the dice again on the next baby.

But I'd like to let the experiment run for a bit as-is to see what emerges.

Another stupid-simple twist that has been suggested is to make males a small bit faster.  BUT, I'm generally avoiding that kind of stuff.  The true physical differences between average men and women who receive the same physical training are pretty small.

Men are still way more prevalent (like 98 to 2) in dangerous jobs that require no physical strength.

Also, I think this discussion hangs on the fact that men serve no necessary reproductive function in this game, where they do serve a necessary one in real life.

But their necessary function in real life is marginal, and only as important as it is due to monogamy (where each man, no matter how unfit, gets a chance to breed---how'd we trick women into that one?)  "We need both a man and woman to have a baby."

I guess it could be argued that in a non-monogamy situation, the non-breeding males have value in that they fill the pool that helps to float the best male to the top.   If you only kept one male baby around, how would you know you kept the best one?  So you keep 'em all and let 'em fight it out later.

But for those non-breeding males, it's still marginal, and not a direct reproductive function.

Throughout human history, males also had value as cannon fodder.   Will cannon fodder have no value in this game?

So... I looked at the life logs, and I think you probably didn't reach "the edge," exactly, since you never got farther than 300 in any direction.  Maybe there was some lag and you didn't get a map chunk in time?  If that happens, you'll see some white areas with squiggly black lines.  Is that what you recall seeing?

If not... if you really moused over something very black and it said "The Edge," then please let me know, because you found a major bug.

The edge is out at coordinate 2 billion+ in any direction, and it looks very different than the map-not-fetched.

Probably the main way that any human being will ever see it is through running their own server where they can force eve location....

Thank you everyone for helping in this.... er... very successful playtest.

Successful in that it gave me a list of very important things to fix.  The baby-management issue will be fixed in short order.  Another playtest session will be coming soon.

Ah!  That's actually normal...

The test scene in the editor isn't infinite.  You start in the upper left corner of the map, pretty much.  If you fill with biome texture, you'll notice that it stops up there too and leaves black beyond that point.

When you save a test map, it only saves the parts of the map that you actually touched.  It then loads those tiles into the middle of the infinite map on the server.  So if you walk out of your test map, you will find wilderness again.

A lot of the editor is hacked together in a "whatever was quickest" fashion.  As long as I know how it works, it's fine, right?

Which makes me hesitant to release it to the public, because it's not a "finished" piece of software, really.

Water is just the current bottleneck.  It won't necessarily remain a bottleneck, and I agree that it is a bit of a strange one.

And yes, things can be set to respawn in the very distant future.... hours or days from now.

Endgame is death or moving for now.  Civs will always collapse, eventually.

But wells will be added later.  Then wells will dry up eventually too.