In our first development log, we looked at how Hive Legacies evolved from a collection of basic menus into something much more physical.
Characters gained locations.
Locations became connected.
Travel began taking time.
The world was divided into local hexes.
Those hexes became physical spaces with 1-meter positioning.
Resources became shared and depletable.
Objects could be left behind for other players to find.
Land could be claimed.
Structures could be built.
And eventually, players could step inside those structures and begin using them as actual persistent spaces.
That was the first major challenge:
Since then, our focus has started shifting toward the next problem.
A persistent berry bush is interesting.
A berry bush that can be depleted, leaving someone else without food, is more interesting.
A building that persists is interesting.
A building that provides warmth, shelter, storage, privacy, recovery, and a place to perform work is more interesting.
A character standing somewhere in the world is interesting.
A character who gets tired, hungry, sick, needs sleep, cannot see everything around them, and experiences the passage of time is much closer to actually living there.
That is where a lot of recent development has been focused.
One of the biggest additions since our last update is the beginning of a true Perception system.
The game server may know everything that exists around you.
Your character does not.
That distinction is extremely important to Hive Legacies.
The 1-meter Hex Detail map now uses perception-based visibility.
Terrain beyond your character's effective sight is obscured.
People can be outside your awareness.
Objects can exist nearby without automatically being revealed.
Ground piles, claims, and physical features do not need to become magically known to you simply because the server knows where they are.
Your Perception attribute now has an actual relationship with what your character can see and understand about the immediate world.
This is much more than a traditional videogame fog-of-war system.
It is part of a much larger rule we are building around:
Not players.
Not the interface.
Not some omniscient global game state.
If your character has no reason to know something, the game should be very careful about telling you.
Physical objects on the ground have also become more detailed.
Instead of clicking an icon and immediately vacuuming an unidentified object into your inventory, characters can inspect what is actually sitting on a square.
Depending on what can reasonably be perceived, you may be able to see information such as its physical condition, quality, weight, bulk, description, container capacity, visible contents, or markings.
That last part becomes especially interesting because ownership and physical possession are not the same thing in Hive Legacies.
Something can belong to you and still be sitting somewhere else.
Someone else can find it.
Someone else can pick it up.
And eventually, someone else might lie about where it came from.
The world knows what an object actually is.
Your character may know something very different.
That gap between truth and belief is something we intend to make increasingly important.
For quite a while, the survival side of Hive Legacies could basically be summarized as:
You can eat berries.
That is changing quickly.
We now have a generalized food foundation with several new forage classes distributed according to the terrain in which they make sense.
Players can currently encounter foods such as wild greens, edible roots, tree nuts, orchard fruit, and berries.
Those foods can behave differently.
Some are more filling than others.
Some provide more useful energy.
Some are better after preparation.
And some can be processed into early cooked foods such as boiled roots, cooked greens, toasted nuts, and roasted orchard fruit.
The important part is not simply that there are more foods.
The important part is that this gives us a foundation for a much larger food ecology.
Hunting.
Animals.
Meat.
Eggs.
Dairy.
Ranching.
Farming.
Grain.
Cultivated crops.
Regional food production.
Eventually, settlements should not survive because a developer placed an infinite food vendor in the center of town.
Food should have to come from somewhere.
Adding food immediately creates another question.
What happens if you don't eat it?
Food now has freshness and spoilage.
And once again, this is being treated physically rather than as a cosmetic timer.
A particular amount of food can exist as a persistent lot with its own age and freshness.
Move it from your hands into a basket?
It keeps aging.
Move the basket into your house?
It keeps aging.
Put the food on the floor?
Still aging.
Hand it to someone else?
You haven't magically reset the clock.
The same physical food has simply changed locations.
The interface can now distinguish between food that is fresh, aging, mixed in freshness, or spoiled.
And spoiled food can actually hurt you.
Eating bad food can reduce how useful the meal is and potentially result in effects such as nausea or food poisoning.
That food poisoning can then interact with a wider character-condition system.
Suddenly:
gathering → storage → time → spoilage → eating → illness → recovery
are all connected.
That is exactly what we want.
Once food can spoil, preservation stops being a flavor feature.
It becomes useful.
We now have the beginnings of a physical Food Preservation system.
Characters can use real physical preservation equipment such as a Woven Drying Frame.
Food preservation happens over time.
The source food is actually committed to that process.
Air-drying can be used on some foods.
Smoke-drying can be used on others.
And smoke preservation can require a functioning nearby hearth.
If the fire goes out, the game does not pretend the food is still being smoked by invisible videogame magic.
The process depends on the physical conditions actually existing.
Move the food away from the rack during an active batch?
You can disrupt the process.
Start with food that is nearly rotten?
Preservation does not magically turn it into perfect premium food.
The condition of what you started with can affect what you end up with.
Food Preservation is also becoming a skill in its own right, connecting character ability, perception, intellect, focus, equipment, physical space, and time.
This is a good example of what we mean when we say we want systems to interact.
We didn't add spoilage simply to annoy players.
Spoilage creates demand for preservation.
Preservation creates demand for equipment.
Equipment creates demand for materials and craftsmanship.
Smoking food creates demand for hearths and fuel.
Longer-lasting food affects travel.
Travel affects trade.
Trade affects settlements.
A timer on a berry can eventually become an economic system.
Structures have also taken a major step forward.
In the previous development log, we showed that players could begin entering buildings and using the interior as persistent space.
That system has now become considerably deeper.
Completed buildings can have their own physical interior space with 1-meter positioning.
You can move around inside them.
Place objects.
Leave resources on the floor.
Store possessions.
Arrange furniture.
Use beds and other recovery furniture.
Use chests.
Work with doors and closures.
And we have begun adding foundations for things such as bars, latches, primitive locks, keys, hearths, workspaces, and Joinery.
One design principle here is especially important:
If a building is secure, we want that security to eventually come from the actual world.
A closed door.
A latch.
A barred entrance.
A lock.
A key.
A guard.
A person physically being there.
Owning a building should matter.
But it should not mean the simulation simply stops applying to everybody else.
Buildings can now also begin developing public identities.
A completed structure can have a public sign name and descriptive tags.
So instead of every building simply appearing as:
Completed Structure
you can begin seeing identities such as:
Private Home
Inn
General Store
Blacksmith
Tavern
Farmstead
Warehouse
Healer
Meeting Hall
Guard Post
And potentially names created by the people who built them.
But this comes with an important rule.
Calling your building an Inn does not magically make it an inn.
The tag doesn't create beds.
It doesn't create food.
It doesn't spawn workers.
It doesn't generate customers.
It doesn't pay you income.
Those are things the physical and economic systems still need to support.
The label describes what you are trying to make the building.
The simulation still decides whether you have actually built something capable of functioning that way.
Being indoors is also becoming more meaningful.
Rooms can now have physical environmental qualities involving things such as:
Comfort
Warmth
Ambience
Shelter
Privacy
Security
Those characteristics contribute to something we currently describe as Recovery Quality.
This means rest does not need to work equally everywhere.
Sleeping outside on bare ground should not necessarily be equivalent to sleeping inside a protected room on decent furniture beside a working hearth.
And importantly, simply owning the room does not give you a magical recovery bonus.
The physical environment matters.
The furniture matters.
The building matters.
The character's current condition matters.
Again, the goal is for the game to ask:
What actually exists here?
rather than:
Which upgrade did the player purchase?
This may be one of the most important systems we have added so far.
Hive Legacies now has an authoritative world clock and calendar.
Time is no longer just a collection of unrelated action timers.
The world itself now knows what time it is.
Our current starting calendar begins at:
The current development rate is:
That means the world currently runs at approximately 24× real time.
Days pass.
Months pass.
Seasons pass.
Years can pass.
At the current rate, roughly 92 real hours takes the world from the beginning of Spring to the beginning of Summer.
About 365 real hours advances the world by an in-game year.
This gives us one authoritative timeline that future systems can use.
Seasons currently exist as part of the calendar.
They do not yet alter the environment.
Winter is not currently freezing rivers.
Summer is not currently drying fields.
Spring is not automatically spawning crops.
But now we have the foundation those systems can eventually respond to.
That matters enormously for what comes next.
Once the world had a real clock, we began rebuilding character recovery around it.
Characters now have more persistent physiology, including things such as:
Sleep Pressure
and
Physical Strain
Using energy can contribute to physical strain.
Endurance can help.
Lack of rest can begin mattering.
And recovery has now been divided into distinct modes.
At the current world-time rate:
Rest represents roughly 30 world minutes.
Nap represents roughly 2 world hours.
Sleep represents roughly 6 world hours.
In real time, that currently works out to approximately 75 seconds, 5 minutes, and 15 minutes respectively.
That recovery system now operates against the same authoritative world clock whether you are outside, inside a building, or using appropriate furniture.
So when your character sleeps for six hours...
six hours are actually passing in the world.
That distinction becomes extremely important once the world contains more NPC schedules, businesses, weather, agriculture, crime, transport, nighttime activity, and other systems that care about the time of day.
The survival foundation is also becoming more general.
We now have systems capable of representing reusable timed effects and persistent conditions.
That includes concepts such as:
nausea,
food poisoning,
fever,
pain,
warmth,
chill,
intoxication,
and being well-fed.
Persistent injuries and illnesses can generate symptoms.
Those symptoms can affect other systems, including how effectively a character recovers.
We are still early here, but this is an important architectural step.
Instead of writing a special one-off rule every time we add a new illness, injury, poison, food effect, or environmental condition, we can begin building those systems on shared foundations.
That will matter later for medicine, combat injuries, disease, environmental exposure, nutrition, and potentially many other systems.
One of the principles we keep coming back to is that important NPCs should exist inside the same simulation players do.
We do not want them to be cardboard vending machines wearing human faces.
NPCs can already travel and participate in parts of the physical world.
Now their recovery can also consume real physical food.
If food is spoiled, that matters to them too.
That may sound like a tiny feature.
It isn't.
If NPCs actually need resources that exist in the world, then eventually NPC populations create demand.
Workers need food.
Travelers need food.
Settlements need food.
Armies need food.
Children need food.
Businesses need supplies.
Suddenly agriculture and trade are no longer systems that exist only because players want to raise a crafting skill.
They can begin supporting an actual population.
That is where the idea of a living economy starts becoming much more interesting.
Another major area currently being developed is information itself.
The world can know that something happened.
That does not mean everyone in the world knows it happened.
Events can be private.
Directly witnessed.
Observable.
Public to the local area.
Or significant enough to become broadly known.
Characters can observe other characters.
Observation can expose information about what someone is doing without automatically granting complete knowledge of how to reproduce it.
Watching a skilled craftsperson work might give you insight.
It does not necessarily mean:
Congratulations. You now know their recipe.
And repeated observation does not need to produce infinite knowledge.
This also connects directly to structures.
Experiment openly outside?
Someone nearby may be able to watch.
Build a private workshop and work behind closed doors?
Now physical architecture can affect the spread of knowledge.
This is exactly the kind of interaction we want.
Knowledge affects architecture.
Architecture affects information.
Information affects economics.
Economics affects relationships.
The systems stop being separate menus and start becoming a world.
The immediate future of development is increasingly about taking these foundations and making them interact more aggressively.
One major area is Persistent Survival.
We now have food, spoilage, conditions, sleep pressure, physical strain, recovery, rooms, furniture, and an authoritative world clock.
The next step is letting those systems matter continuously rather than only when the player presses a button.
Another major focus is the environment around the new calendar.
We have days, seasons, and years.
Now those things need consequences.
Eventually, seasons can influence resources, food availability, agriculture, temperature, travel conditions, preservation, and many other systems.
Food itself also has a long way to go.
The current forage and cooking systems are the beginning of a much larger path involving deeper cooking, hunting, agriculture, domesticated animals, meat, grain, dairy, eggs, cultivated crops, and regional production.
And the social simulation is beginning to expand too.
Direct barter, teaching, study, beliefs, information transfer, relationships, organizations, encounters, crime, justice, combat, and eventually bloodlines are all pieces of the larger living-world architecture we are building toward.
Not all of that arrives tomorrow.
But the foundations are being laid in an order where each new system has something meaningful to interact with.
Dev Log #1 was largely about proving that the world could remember.
If you picked the berries, somebody else could arrive and find them gone.
If you left an axe on the ground, somebody else could find it.
If you built something, it could remain there.
That was persistence.
Now we are beginning to ask what happens because those things persist.
The berries are gone.
Someone is hungry.
The food they collected yesterday is beginning to spoil.
They need to preserve it.
Preservation requires equipment.
Some methods require a working hearth.
The hearth is inside a building.
The quality of that building affects recovery.
The character has been working all day and is physically strained.
Night arrives.
They sleep.
World time continues.
Another player walks past the building while they are asleep.
Maybe that player sees the sign outside.
Maybe they don't know who lives there.
Maybe the door is locked.
Maybe it isn't.
Maybe there is food inside.
Maybe there is a secret experiment happening in the workshop.
Maybe someone has been watching.
That is the direction Hive Legacies is moving.
Not toward more isolated features.
Toward more consequences between features.
We still have an enormous amount to build.
Most of Hive Legacies remains ahead of us.
There will be systems that change completely.
There will be balancing mistakes.
There will be things that work technically and fail as gameplay.
There will be ideas we currently love that players eventually prove are terrible.
That's part of building it.
But the game is becoming noticeably different from where it was even a short time ago.
The first version let us gather berries.
Now food can come from multiple places.
It can be cooked.
It can age.
It can spoil.
It can make you sick.
It can be physically preserved.
It can sustain NPCs.
Time passes while all of that happens.
Your character gets tired.
Rooms can help them recover.
Buildings can become named places.
Perception limits what you know.
And the game is beginning to separate what actually happened from what individual people believe happened.
We started by building a world that could remember you were there.
Now we're working on a world that can react because you were there.
And this is still only Year 1.
Hive Legacies is actively in development. Systems, mechanics, balance values, time scales, interfaces, terminology, and features discussed in this post may change significantly as they are tested and expanded.
