In Dev Log #2, we spent a lot of time talking about survival. Food could spoil, characters could become sick, rest and sleep had started running against the world clock, and Perception was beginning to limit what a character could actually see. We also had seasons on the calendar and were laying the groundwork for the environment to eventually react to them.
A lot has changed since then.
The biggest difference is that the Garden is starting to feel less like a collection of systems waiting for players and more like a place where people actually have reasons to do things. Businesses need supplies, workers have shifts and wages, merchants have limited stock and money, inns can rent actual sleeping spaces, and the public shelter can run short on food. Characters continue dealing with survival while their player is away, weather can make a journey harder, and crops are now capable of growing according to soil, season, moisture, and environmental conditions.
A lot of these systems are still early, but they are finally beginning to push against one another. That interaction between systems has been the focus of most of this development period.
One of the first major additions after Dev Log #2 was the Garden's first real group of businesses. Right now we have four permanent establishments: the Common Toolhouse, Greenbasket Provisions, The Hearth & Reed, and the Garden Common Shelter.
These aren't abstract shop interfaces. They are run by actual NPC characters living in the Garden. Harlan Wood operates the Common Toolhouse, Talia Green runs Greenbasket Provisions, Mara Fen is the innkeeper at the Hearth & Reed, and Orren Hale oversees the Garden Common Shelter.
The more important part is how those businesses work underneath the names. They have physical stock, Marks, owners, employees, and actual things they are willing to buy or sell. Commerce is beginning to operate through the same physical world as everything else rather than through a separate shop system that ignores where people and items really are.
Commerce has now moved inside the physical world. Businesses have service counters, and trading requires the customer and an appropriate worker to actually be there. If you walk into the Toolhouse, you need to approach the counter and deal with whoever is working. If nobody is available to operate the business, the shop doesn't continue functioning through an invisible interface outside the building.
It sounds like a relatively small change, but it connects a lot of systems that were previously being built independently. Buildings matter because businesses occupy them. Interior movement matters because the player physically approaches the service counter. NPC schedules matter because someone needs to be working. Opening hours matter because those workers aren't available forever. Physical stock matters because whatever is being sold has to actually exist.
One of the goals throughout Hive Legacies is to avoid situations where the world visually tells you one thing while the game logic quietly does something completely different underneath it. If a business is closed, we want there to eventually be an actual reason it is closed.
We also added Bargaining as a proper character skill. Merchants now have economic and personality profiles that can influence how they negotiate, and players can attempt to haggle over the prices of actual trades.
The idea isn't to create a button you repeatedly mash until the game finally gives you the discount you want. Negotiations are remembered for a period of time, and the result can take things such as the merchant, their stock situation, your relationship, and your Bargaining ability into account. If a negotiated price is reached, that price then applies to the real transaction.
This also gives us room to expand merchant behavior later. A merchant sitting on too much aging food shouldn't necessarily negotiate the same way as somebody holding one scarce tool that everyone wants. We aren't all the way there yet, but the foundation for that kind of behavior now exists.
Structures have also gained a much more complete ownership and access system. We already had physical doors, locks, keys, bars, and other ways of controlling an entrance, but now there is a social and legal layer sitting beside the physical one.
A character can own a building while other characters can be residents, household members, guests, tenants, employees, lodgers, or managers. Those relationships can grant different rights, including permission to enter, shelter there, operate an entrance, or manage access for other people.
Permission still doesn't replace the physical world. Someone may have permission to enter your home and find that the door is physically locked. On the other hand, someone could potentially have the physical ability to get through an entrance without having any legitimate right to be there.
Keeping those concepts separate will become increasingly important as we move deeper into property, renting, households, theft, trespassing, businesses, crime, and eventually law.
The Hearth & Reed is a good example of why we spent so much time building the earlier systems before trying to create businesses. It can now function as an actual inn rather than simply being a building with an “Inn” label attached to it.
At the moment, a stay costs 10 Marks for 24 world hours and includes a limited amount of food and water. Capacity comes from the actual usable sleeping spaces inside the building rather than from an arbitrary number attached to the business. If the available sleeping space is occupied, there isn't another room to rent.
Payment also participates in the economy. The Marks used for the stay move into the business rather than disappearing into a generic system sink. Food comes from the inn's real stock, water comes from its real stock, and the temporary access granted to a lodger ends when the stay ends. Renting a room for a night doesn't somehow turn the guest into a permanent owner or resident.
A fairly ordinary action like renting a room now brings together money, buildings, beds, access rights, food, water, NPCs, world time, and recovery. That's the kind of overlap we want to keep building.
The Garden Common Shelter provides another type of service. It can offer temporary free shelter to characters who legitimately need somewhere to stay, with finite sleeping capacity and limited food and water coming from the shelter's own supplies.
It isn't intended to become free hotel accommodation for someone who already owns a perfectly usable house nearby. Eligibility matters, not because we want to simulate bureaucracy for its own sake, but because we want institutions in the world to have real purposes and real constraints.
The shelter needs food and water to provide those services. Those resources have to come from somewhere, and that creates another point where survival starts feeding directly into the economy.
For a while, merchant dialogue included an option to ask whether somebody had any work, but it was mostly a placeholder. That option now connects to the actual condition of a business.
Businesses can generate supply work when they are genuinely running short on something they need. If Greenbasket Provisions needs a resource and the business can afford to pay for it, a supply contract can become available.
That contract isn't coming from a generic quest table. The business is actually short on stock, the owner actually needs the goods, and the Marks being offered as payment actually exist. When a player accepts the contract, the payment is reserved. When the requested physical goods are delivered, they move into the business's inventory and the reserved Marks move to the player. If the agreement is cancelled or expires, the reserved payment returns to the business instead of disappearing.
This is one of the first places where Hive Legacies can present something that looks a little like a traditional MMORPG quest while operating very differently underneath. The situation itself created the work. If the shortage is solved, the reason for that work disappears with it.
That's much more interesting to us than an NPC permanently asking every passing adventurer to bring them five roots because somebody wrote that quest into a database.
The other merchant conversation option we wanted to turn into a real system was “Know any rumors?”
NPCs can now answer that question using beliefs they actually possess and are allowed to share. If a merchant knows that their business is running short on something, that can become local information. If somebody witnessed something on the road and formed a belief about what happened, that information can eventually be passed along as well.
The important distinction is that the game doesn't turn somebody's statement into absolute world truth simply because an NPC said it. Your character knows that a particular person told them something. That belief has a source and a level of confidence, can potentially be transmitted again, and may eventually turn out to be wrong.
We're beginning to build toward a world where information moves through people instead of every person having access to one giant omniscient database. That creates a lot of room later for witnesses, trade information, reputation, lies, crime, news, misunderstandings, and deliberate misinformation.
The people working in these businesses are also becoming more than permanent decorations standing behind counters. Employees now have actual shifts tied to world time. A gatherer may work from morning through the afternoon, a cook might stay into the evening, and the Garden Common Shelter even supports an overnight worker.
NPC business production respects those schedules. If a cook is off duty, the business doesn't quietly continue using that character to produce food all night. If the person needed to operate a particular service is no longer working, that service can stop being available.
It's the beginning of businesses having actual daily rhythms rather than treating everybody in the world as permanently awake and permanently productive.
Employment now includes real payroll as well. Workers earn wages in Marks according to the terms of their employment, and the business owner is responsible for actually paying them.
Businesses reserve money for upcoming payroll before deciding how much of their remaining cash can safely be spent elsewhere. If there isn't enough money to cover the full wage, partial payment can occur and the remaining amount becomes wage debt. Under the current rules, an employee who goes through three completely unpaid paydays can leave the job, but quitting doesn't erase what they were already owed.
This gives us the beginnings of an employment relationship that can genuinely fail. A poorly managed business can overspend, struggle to afford supplies, miss payroll, lose employees, and then become even less productive because those workers are gone.
We don't have a complete economic simulation around all of that yet, but the basic feedback loops now exist.
Businesses can also maintain supply priorities based on what they actually need. A toolmaker may need materials for production, a grocer needs food stock, an inn has obligations to its guests, and the Common Shelter needs enough food and water to provide the services it promises.
Those shortages can influence what employees gather and what kind of work becomes available to players. If the shelter serves food and its stock falls, replacing that food becomes an actual need. An employee may gather more, the institution might pay a player to deliver supplies, or eventually another business could be competing for the same scarce resource.
That's the direction we want the economy to move: away from static NPC shops with endless inventories and toward people and institutions competing for physical things that actually exist in the world.
We also released the first version of Persistent Survival, and this is one of the systems we've had to approach carefully. There is a very thin line between making the world continue while a player is gone and accidentally making logging out an automated progression strategy.
After a short disconnect grace period, an absent character can continue dealing with basic survival. They can become hungry or thirsty, consume food and water they physically have access to, recover, suffer from environmental exposure, and, when appropriate, attempt to reach legitimate shelter using routes they actually know.
A character who owns a nearby home can prefer returning there. Someone who qualifies for the public shelter may use it. However, an offline character won't simply decide to spend the player's Marks renting a private inn room without permission.
Most importantly, being offline does not award skill XP, knowledge, route familiarity, Marks, production, social progress, or other player progression. If the player disconnects in the middle of productive work, that productive timer is paused across the offline period rather than turning logout into a way to automate the game.
Your character can try to stay alive while you're away. They cannot play Hive Legacies for you.
Hydration has now joined hunger as another physical survival need. Drinking requires water that actually exists and is physically reachable rather than generating a serving from an invisible survival action.
If you have water in a reachable container, you can drink it. If an inn promises water to a guest, that serving has to come from the inn's stock. If the public shelter begins running low on water, that shortage becomes real as well.
That means what looks like a fairly straightforward survival meter immediately begins touching the rest of the simulation. Water has to be collected, stored, transported, and supplied. Travelers need it, businesses can need it, and now agriculture needs it too.
In Dev Log #2, we introduced the world clock and calendar, and at the time we specifically pointed out that the game could tell you it was Spring without Spring actually changing much about the world.
That is no longer true.
Hive Legacies now has an environmental simulation covering weather, daylight, seasonal climate, temperature, wind, visibility, soil moisture, river conditions, and flood risk. Different terrain types respond differently to those conditions. Woodland doesn't retain moisture or expose travelers to wind in exactly the same way as rocky terrain, a marsh behaves differently from a meadow, and river areas react more strongly to changing water conditions.
Weather isn't just descriptive text either. Rain can make characters wet, temperature can create thermal stress, shelter can protect people from those conditions, and a functioning hearth can become important. Visibility can change, travel can become slower or more difficult, natural resources can regenerate differently depending on the season, and rising water can make river and marsh routes significantly worse.
Persistent Survival uses those environmental conditions too, so the weather still matters while a player is away.
Travel consequently doesn't have to be a fixed statement that a route always takes a certain amount of time. A route might normally be straightforward but become substantially worse today because of rain, flooding, visibility, or other conditions. We're beginning to get actual days where the world behaves differently from the day before.
Once weather, soil moisture, physical water, world time, and land preparation existed, farming became a natural next step.
The first playable farming loop is now in the game. We're starting small with a crop called Garden Roots, but even this first crop already sits on top of quite a few existing systems.
A player prepares real ground on a physical 1-meter tile. That ground needs to be appropriately cleared, and the tools used to work it can physically wear down. Planting consumes an actual Edible Root, watering consumes actual reachable water, and tending can reduce weed pressure.
The plot itself tracks things such as soil moisture, fertility, natural fertility, tilth, and weeds, while the crop tracks growth, health, and developmental stage. From there, the crop experiences the same environment everything else does. Temperature matters, moisture matters, weather matters, and the current season matters.
Garden Roots currently have a baseline of around 120 world hours to reach maturity under appropriate conditions, and their seasonal response differs substantially between favorable periods such as Spring and difficult periods such as Winter.
We're trying to avoid farming becoming a simple cycle of clicking Plant, waiting a few minutes, and receiving a stack of identical vegetables. Even this first implementation is being built as the foundation for a much larger agricultural system.
Farming also forced us to answer an interesting question about Persistent Survival: if the world keeps running while you're offline, should crops freeze because the farmer closed their browser?
We decided they shouldn't.
Plants are part of the world's biology rather than player progression. A crop can continue developing with world time while its owner is gone. Rain can still happen, soil conditions can still change, and the plant can continue moving toward maturity.
What does not happen is automatic player progression. You don't gain Farming XP while away, receive harvested food, earn Marks, or have the game magically move the crop into your inventory. If a plant becomes mature while you're gone, it simply becomes mature.
Someone still needs to physically go out there and harvest it.
That distinction between the world progressing and the player progressing is something we expect to use in a lot of future systems.
We've also continued cleaning up and expanding the character skill system. There are currently 16 skills in the live catalog, including newer additions such as Bargaining, Farming, and Wayfinding.
Wayfinding is intentionally different from route familiarity. A character knowing one particular road well because they have traveled it repeatedly is not the same thing as having a more general ability to navigate difficult terrain and environmental conditions.
Those are therefore separate systems. A character can become familiar with a particular route through repeated experience while developing broader Wayfinding ability at the same time. Wayfinding currently provides a modest ability to deal with some of the environmental overhead involved in regional travel, which becomes increasingly useful now that terrain and weather can complicate those journeys.
The next area of development is important to describe accurately. The genetics work is still actively being developed, so we're not presenting everything in this section as a completed and released gameplay system yet. Enough of the foundation exists, however, that it's worth explaining where we're headed.
Rather than eventually creating one inheritance system for crops, another completely unrelated one for animals, and then a third one for human families, we're working toward a shared living genetics foundation. Garden Roots are serving as the first testing ground for that architecture.
The current design gives plant lineages inherited potential in areas such as vigor, yield, maturation speed, drought tolerance, heat tolerance, cold tolerance, and tolerance for overly wet conditions. Those inherited tendencies aren't intended to override everything else happening in the simulation.
A crop with strong drought tolerance can still suffer under terrible conditions. A genetically promising plant that is placed in bad soil, poorly planted, and neglected by the farmer should still perform poorly. Good farming can help a crop realize more of its inherited potential, but good farming shouldn't magically transform a weak lineage into a perfect one.
The important distinction is between what an organism inherited and what actually happened to it during its life.
The same principle will eventually matter for animals and, much later, human families. Skills and knowledge are specifically separate from genetics, so a child won't be born knowing how to farm simply because one of their parents happened to become an exceptional farmer.
Another important part of the genetics work is how players actually learn about inherited characteristics.
The simulation may need hidden numeric values in order to model biological variation, but that doesn't mean players should be presented with a spreadsheet telling them that a plant has 68.4 Drought Tolerance and 73.1 Yield Potential.
A farmer should learn that one lineage tends to perform better through dry summers because they actually grew it, compared it with another lineage, observed the results, or learned from somebody who already had experience with it.
Over multiple generations, that creates the possibility for players to intentionally develop crop lines known for particular characteristics. Those lineages could eventually be shared, traded, protected, stolen, crossed with others, or even lost completely.
At that point, agriculture itself begins accumulating history, and that is where the genetics system starts becoming especially interesting for a game called Hive Legacies.
Early development required us to answer a lot of basic questions. Can a character persist? Can they physically move through the world? Can an object stay where somebody dropped it? Can resources actually run out? Can a player build a structure? Can the world track time?
Those questions still matter, but the questions we're starting to ask now are much more interesting because they involve several systems at once.
What happens when an inn runs out of food while the worker who normally supplies it is off duty? What happens if the business doesn't have enough Marks left to make payroll? What happens when a player accepts a supply contract but heavy rain floods the route they were planning to use? What if the food they eventually deliver came from their own farm after a poor growing season? What happens later when another farmer develops a crop lineage that handles those conditions better?
That's the direction we're trying to move in. The goal isn't simply to add more features beside one another. We want existing systems to create reasons for other systems to matter.
Imagine that the Hearth & Reed starts running low on food because guests have been consuming its physical stock. The business now has a genuine shortage, and because Mara still has enough available Marks to pay for more supplies, a contract becomes available to somebody willing to solve the problem.
A player accepts that contract, but heavy rain has raised the river and made the normal route slower. Now they have to decide whether the delivery is still worth making. Maybe they're already wet and exhausted and decide to rest somewhere first. Maybe the food they're carrying came from their own farm, and that particular harvest happened to perform unusually well because the lineage handled the season's wet conditions better.
Eventually they reach the inn and deliver the goods. The food enters the inn's actual inventory, and the player receives the Marks Mara reserved when the contract was accepted. The inn can continue feeding guests, but Mara still needs enough money left to make payroll. The cook arrives for their next shift and now has ingredients available to work with.
Nobody had to write a quest called “Save the Inn From the Great Root Shortage.” The systems created a problem, and the player decided whether it was worth solving.
We're still very early, but those are the kinds of situations all of this architecture is being built to produce.
The immediate direction is to keep deepening systems that interact with what already exists rather than racing to add disconnected content.
Farming still needs more crops, deeper propagation, seed saving, and eventually persistent lineages. Weather needs additional environmental consequences. Businesses need deeper production and competition, while employment needs more reasons for workers to care about their job, wages, and treatment. NPC information needs to travel farther and become more useful, dangerous, or unreliable depending on who knows what.
Agriculture can eventually open the door to animals, husbandry, meat, dairy, eggs, manure, transport, and much larger food chains. The genetics foundation gives us something that can eventually connect crop breeding, animal breeding, and the generational family systems Hive Legacies has been aiming toward from the beginning.
There is still a very long way to go, but this development period feels important because we've started reaching the point where adding one system changes the meaning of several systems that already existed.
Weather makes travel more interesting and shelter more important while also giving farming something real to react to. Farming creates another source of food, food gives businesses something they genuinely need, business shortages create work, work moves Marks, Marks pay employees, and those employees help keep businesses functioning. Those same businesses then provide tools, food, lodging, shelter, and other services to the people living in the Garden.
That loop is nowhere near finished, but it exists now, and that feels like a meaningful step forward for a game this early in development.
Hive Legacies is actively in development. Systems, balance values, economic rules, interfaces, names, time scales, and planned features can and probably will change as we test them. Systems described in the “working on now” section should not be interpreted as completed or released until we say they are.
