Rosey, Bedazzled, Beansprout
Direction, art, and systems all came from a very small circle that kept the project moving.
Everbloom Valley comes from a small core team handling design, engineering, art, writing, and community work, backed by early supporters and a player base that keeps the project honest.
Direction, art, and systems all came from a very small circle that kept the project moving.
World voice, character writing, art direction, iconography, and UI style were all shaped in-house.
Farming, fishing, breeding, trading, quests, networking, and live-service support all depend on the engineering layer.
Bug reports, screenshots, balance feedback, and testing from the community directly influence what ships next.
The project is intentionally personal. A small team carries creative direction, live systems, and community support, which is why crediting roles clearly matters here.
Sets the tone of the world, leads overall direction, writes core lore and NPC personality, and helps steer community-facing decisions.
Shapes visual identity across environment art, UI, props, iconography, and the overall look that makes the valley feel distinct.
Builds the gameplay backbone, networking, data systems, economy support, and the technical architecture that keeps the experience running.
Because the team is compact, roles overlap. Even so, there are clear ownership lanes that keep decisions coherent across updates.
This is the current live footprint the site is built around, so the numbers below reflect what players can actually expect today instead of broad promises.
The core crop ladder already active in the valley.
Hybrid breeding goals deepening the late-game farm loop.
Catchable species already stocked across the live fishing pool.
Friendship-ready residents anchoring the current town cast.
Collectible star transformations tied to the Fallen Star chase.
Main-story quest count and lore depth already shaping the world players step into.
Small-team games survive because the work is shared by more than the people with edit access. These groups helped test, amplify, and pressure-test Everbloom Valley before and during Early Access.
Bug reports, feature requests, balancing notes, and the day-to-day pulse of player sentiment.
Community sharing, word of mouth, and the kind of farm-showcase energy that helps a cozy game feel alive.
First-wave players who trusted an in-progress world and gave the team real feedback instead of empty praise.
The platform foundation that makes the game, save systems, and multiplayer reach possible in the first place.
Production-ready footer pages should feel like a connected set: privacy explains data, terms explain rules, credits explain authorship, and support gives players a way to respond. This page closes that loop by making the people behind the game visible.
The Team page gives the broader creator-facing view, while Terms and Privacy explain the rules and data handling behind the same public project.