a multiplayer game of parenting and civilization building
You are not logged in.
WonLife 363.83
- block many instances of your character talking to itself
- location slips temporarily give close distances
- location slips show distance when hovered
- slip to owned property
- /FAM gives location slips instead of speech
- follow roads only while autorunning
- fix bug with object search in containers
(However, the release build still has the ghost sound regression.)
Chest: Rabbit Fur Shawl (cheap and extremely uncommon)
Bottom: Rabbit Fur Loincloth (cheap, but common, until village gets wool clothing. other option would be reed skirt)
Foot: Wool Booty (relatively cheap, and seems to be the least common footwear that is easy to acquire)
I see shawls semi-regularly. But it is often hard to see the difference with a backpack on.
I usually pick a rabbit loincloth when I have the option. I believe is best in class for temperature, thus many people will wear it by choice. There are few options for bottoms though. Some of the skirts are uncommon, but there is the loom tech barrier, and they will likely get turned into pants.
I see wool booties sometimes, but they are probably uncommon enough.
Also, all of these decay, so there would be an ongoing cost. On the upside, that means extras won't accumulate and be worn by others as often.
I would go a step further than just making it a clothing related thing and say it should be a mechanic just like leadership with designated role titles
Would be nice. Right now I'm hoping to maybe create a tradition. If people play this way, perhaps it appear worthy of enshrining in code.
Meanwhile: experience report: Toques don't get made much, but people do seem to like wearing them when they exist. Perhaps I should be more active about asking people if they know about this idea or just picked it up. Would help spread the idea if nothing else.
I've been thinking that males may make better teachers without babies popping in all time time. The problem is that without those babies, you don't have a good way to start the conversation. If nobody answers on a visit to the nursery, you go off to do something else, and miss quite a few people, unless you spot somebody struggling at a basic task.
What if there were a teacher's uniform? To really work we'd have to tell new players about it like we tell them about yum, but we've got start somewhere.
Right now I'm thinking Toque Blanche (chef's hat). It's not best-in-class so you don't see them often, but they are not terribly hard to make and still have a bit of insulation. Other possibility might be the Santa Hat; however it requires alum and seems to be a bit more common on it's own.
WonLife v361.82
Packaging update. Now ships with three example settings directories, and slightly more user-focused readme. Patch descriptions moved to separate file.
Changed default for shiver and sweat to off.
Changed binary defaults for camera control to have pan instead of edge push.
If you already are running WonLife, do not update. Patches have moved to Jason's base master, which has the ghost horse/truck sound fix. The patch has thus been removed, but the packaged builds are still using the last client release as base, which still has the bug; thus this build will also have the sound bug.
I checked the code. Primary homelands *should* get reset as part of the map wipe, so no family will have one on record after the apocalypse.
Just remove death from the game. And the quit button. Catch quit signals and rootkit the computer to make sure escape is impossible. One Hour is not only guaranteed, but REQUIRED.
Nope, it's been disabled, presumably forever.
All this talk and the only thing for "garlic" on the issues was a comment on something else. So here you go.
This update also fixes the permanent horse/engine noise bug, that alone makes this a five star update.
Ty Jason! (and of coruse wondible who made the fix for the noise bug)
No, it doesn't. There was no update for binary client version. It seems he still doesn't have access to the computers used to publish client builds.
The code is committed though. It is coming.
Hi wondible, I'm just wondering why the heatmaps and the ability to see built structures seems to only work on big server 2. I was looking at server 3 and was curious to why I wasn't able to see anything besides a few spots where people died.
Jason only publishes object placement data for the main server.
I posted a map update (may be cdn delay) The banding simulation always uses the new placement; band overlay has a rough estimated switchover time, which I will update to be exact tonight.
Rolling out soon:
- Found and fixed a prime suspect for the mis-scaled activity map tiles (this wasn't reproducing locally, so it is a bit of guesswork)
- The fade option now applies to activity map. Activity may also be separately toggled off.
- Lineage color have been adjusted for dark mode
- Format options have subsections which toggle with their associated layer or feature.
Each band would have their own different types of resource variations, for example tundra bands would have white rabbits, which give white fur and different meat, while desert rabbits are a grey-colour and vice versa. This would also extend to wild foods, such as berry variations like blackberries, strawberries, etc.
Right now all the specialty stuff is rare and precious. What if each band had foods that were good and easy enough to be staples in their band, but would still be somewhat unusual in other bands. Tacos and saurkraut are probably the closest, both involve moving some base materials rather than finished goods.
Birth coords could be integrated into the activity heatmap too, since those don't cause tile changes.
Before maplogs I considered doing something like this with just the life data. I'm not sure it would add a lot to this data; perhaps it could still be done to backfill pre-maplog times. I'm also not too keen to make it any slower to process.
This is very cool. Obtained from tile content chamges?
Yep, same maplog data, just another pass (or 22, for all the zoom levels)
Rolling out now (subject to caching): activity maps (heatmaps) allow spotting active parts of the map at higher zoom levels. It can also be set to stay visible closer-in (format options), to identify hotspots in towns.
Sample size can be changed in the format options; this is mainly to give you bigger pixels for finding active spots from far perspective. Notably, it's now much easier to identify the tutorial zones.
Activity maps are static snapshots, at the same intervals as static object snapshots. Recently there were multiple snapshots per day, but today's did not split; it will likely be once a day at most times.
Delete the .db files, but there may be a few others, offhand something like map_dummy_recall.txt is one of them.
Or just pick a new random x for your eve spawn location, thats basically what the tutorial solo challenge does. I wouldn't mess with y as much, you wouldn't get special biomes most places.
I mean you shouldn't be able to enter a time in the future. Here's the hypothetical situation:
Part of the problem is different only partly overlapping data sets. Lives and map data are on different schedules. Different servers can have different ranges, I think lives on server1 don't go back as far as some others.
2030 may not make sense, but I drag "now" to the right all the time to get back to the latest snapshot, which is past any data.
It should take me to the current snapshot, right?
It should, yes.
When you refresh the page on the above link the unix time stays on whatever you've set it to, but if the snapshot isn't current for that timeframe then the map stays the same and the timestamp displayed updates anyway. That's why the timestamps and map content don't match. To load the current snapshot as you described you have to open a new tab. Deleting the unix time in the same tab doesn't work.
I see a situation where deleting the url timestamp doesn't cause any state change, which I'm not sure has an obvious behavior to it. Perhaps since viewing that url would reset to current time, it should do that. I don't quite follow the rest of your description.
There should be a check to prevent entering a time code in the future. If one is entered it should snap back to the most current instead. At the very least the timecode shouldn't persist between refreshes, as none of the other settings behave this way.
Also don't follow you. Where are you entering a timecode? Why should it ignore that input and replace it? Why shouldn't it presist? - if I want to talk about something I found, it might not be there in the latest snapshot by the time someone follows the link.
What time does the snapshot update?
Raw data updates at 24 hour intervals after the last server restart. The final moment is the default time when you load the map without a timestamp. Processing is taking longer with all the extra activity, but perhaps an hour after that.
Presets should be fixed.
The rather expensive biome layer can be toggled off (even though it doesn't affect the current time)
Maybe you overflowed onto server1 and started out in lowpop mode? Band placement of eves only works when biome restrictions are in effect I think.
A little thought:
One of the old ideas was that of people sacrificing everything to help their kids survive. But if you sacrifice yourself, you won't live long enough to enjoy the benefits of your child surviving.
This has already taking a small hit - the new player bonus, while a great advance in keeping new players alive and stabilizing the game as a whole, has removed one touching moment - we used to give our clothes to our new kids because they *needed* it "OMG mom just gave me the clothes off her back!". Now a vetern player needs the insulation more than a new child.
What was the point of obscuring the seed of the map? Isn't it kind of pointless now that resources are in predictable locations?
I think the point was to avoid people scouting out iron veins and such. Nowadays just the biome layout against the well grid would be enough to pick town sites.