Welcome to the development journal at Silly Rabbit Studios. This is where we will share the work behind Veloria: the places we are building, the ideas we are exploring, the problems we encounter, and the progress that brings those ideas closer to something people can experience. We want this blog to become a record you can follow over time, from an unfinished environment to the smaller details that make a world feel worth visiting.<\/p>\n\n\n\n
This is an introduction to our direction, rather than a release announcement. The projects are in development. Some of the places discussed here already appear in our work-in-progress screenshots; other features and regions remain plans. We will make that distinction clear as we share more.<\/p>\n\n\n\n
There are two separate game projects in this journey. Kingdom of Veloria is our original Unreal Engine project. Veloria is our separate Skyrim-based project. They share creative interests and a community, but they have different foundations, requirements, and development challenges. Progress on one does not automatically mean the same feature is available in the other.<\/p>\n\n\n\n
For the Unreal project, we are shaping an original world and working toward a multiplayer experience. That is the direction we are building toward, not a claim that a public multiplayer release is available today. The Skyrim project has its own technical work and testing needs. Future posts will identify which project they cover so readers can follow the work that interests them.<\/p>\n\n\n\n
Our current Unreal worldbuilding focus is the harbor. We want it to have a tropical, grounded atmosphere: warm coastal light, water, sandy edges, greenery, stone paths, market spaces, buildings, and the feeling of a settlement taking shape beside the sea. It should offer a different mood from the harsher regions we hope to explore later.<\/p>\n\n\n\n
A harbor can be more than a view of boats and water. Our vision includes places for people to arrive, meet, trade, explore, and eventually make part of their everyday experience in the world. We are thinking about how the shoreline, market, castle, and surrounding land relate to one another, and how a player would move between them. Those relationships matter as much as the appearance of a single building.<\/p>\n\n\n\n
The development images show a work in progress. Buildings, terrain, props, water, and routes can change as we test proportions and decide what fits. An early shape is a starting point for discussion and improvement. We would rather show that process honestly than present every screenshot as a finished location.<\/p>\n\n\n\n
Small details can make a large difference. A wall should meet the structure beneath it. Castle battlements should look supported and face in a way that makes sense. Rocks and trees need appropriate collision where players can reach them. A character moving through the environment should feel connected to the ground, rather than simply sliding across it.<\/p>\n\n\n\n
These are examples of the practical work that sits behind a screenshot. Walking a route, checking a corner, revisiting the same building from another angle, and noticing a floating piece can all lead to useful changes. A beautiful view is valuable, but so is a place that behaves consistently when someone explores it. We will distinguish visual improvements from changes that have also been checked in play.<\/p>\n\n\n\n
Water is an important part of the harbor vision. We have discussed coastal routes, nearby islands, fishing scenes, and islands that could eventually contain dungeons or other discoveries. Surface swimming and underwater diving are also part of the desired direction. These ideas need their own implementation and testing; the presence of visible water alone does not mean those activities are ready.<\/p>\n\n\n\n
We are also learning to balance the appearance of a large environment with its resource use. A water area that looks attractive can still be too expensive for the scene around it. Expanding the world should involve choosing suitable approaches, checking performance, and deciding what actually needs to be loaded or detailed. The goal is a world that feels generous to explore and remains practical to develop.<\/p>\n\n\n\n
After the harbor, the Northern Realm is a major part of our regional vision. Its identity should be immediately different: towering mountains, immense cliffs, snowy peaks, deep valleys, cold rivers, and settlements shaped by difficult terrain. Where the harbor feels warm and approachable, the north should feel imposing, remote, and ancient.<\/p>\n\n\n\n
Our ideas for that region include forests in the lower areas, mountain passes, watchtowers, ruins, caves, waterfalls, tunnels, and rail routes through the landscape. These are design intentions, not a list of completed features. We want each region to have a reason to exist beyond being a larger piece of terrain. Climate, landmarks, travel, and the kinds of places people discover should help give each area its own character.<\/p>\n\n\n\n
The harbor remains the current focus. Planning the north helps us understand the wider world, but it should not pull attention away from making the starting area coherent. A smaller area with thoughtful routes and meaningful detail is a stronger foundation than a huge expanse that has little to do or see.<\/p>\n\n\n\n
We have also been discussing how different locations could be organized: the harbor, a city, castle interiors, sea journeys, and other regions may need different approaches to how they are built and loaded. Travel connections, including trains, are part of that planning. The exact structure will depend on what the projects can support and what testing shows.<\/p>\n\n\n\n
Natural borders, hills, cliffs, and water can help frame a region, but they also need to fit the landscape. We want boundaries and routes to feel intentional. As more areas become available, some temporary limits may change. That is part of building outward from a starting area, rather than claiming the whole world is finished at once.<\/p>\n\n\n\n
We will use this blog for development write-ups, work-in-progress screenshots, map and environment discussions, character and creature ideas, and explanations of what we are testing. When a change is verified, we can describe what was checked. When something is a concept, experiment, or unresolved issue, we will say so.<\/p>\n\n\n\n
We also want this space to introduce other projects and tools as there is something suitable to share. Public GitHub links, demonstrations, and downloads can help people understand how a project works, but each needs its own context. Source code being available does not mean a feature is deployed, and a screenshot does not prove that a complete game is ready. We will share usable links when they have been checked.<\/p>\n\n\n\n
The intention is for this blog and the main website to complement one another: detailed stories and development records here, with a clear route for visitors to find project information and updates on the main site. Connecting those updates is part of the website work; automatic sharing between the sites is not something we are announcing as finished in this post.<\/p>\n\n\n\n
Our immediate direction is to keep improving the harbor, document the work with clear pictures, and test how the environment feels to move through. Characters, creatures, water interactions, and the wider regional plans each need attention at the right stage. We are not announcing a release date here. We will focus on showing concrete progress and explaining what remains.<\/p>\n\n\n\n
Thank you for joining us while these projects are still taking shape. There is a lot to build, and this journal gives us a place to show both the visible changes and the decisions behind them. We hope the updates make it easier to follow the journey and understand the world we are trying to create.<\/p>\n\n\n\n
What would you like a future post to explore in more detail: the tropical harbor, the castle, character and creature development, or the Northern Realm? We would love to hear which part of Veloria you are most curious about.<\/p>\n","protected":false},"excerpt":{"rendered":"
Welcome to the development journal at Silly Rabbit Studios. This is where we will share the work behind Veloria: the places we are building, the ideas we are exploring, the problems we encounter, and the progress that brings those ideas closer to something people can experience. We want this blog to become a record you […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"wpai_generated_summary":"","wpai_meta_description":"","footnotes":""},"categories":[1],"tags":[],"class_list":["post-12","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/crimson-sheep-95571.zap.cloud\/index.php?rest_route=\/wp\/v2\/posts\/12","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/crimson-sheep-95571.zap.cloud\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/crimson-sheep-95571.zap.cloud\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/crimson-sheep-95571.zap.cloud\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/crimson-sheep-95571.zap.cloud\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=12"}],"version-history":[{"count":1,"href":"https:\/\/crimson-sheep-95571.zap.cloud\/index.php?rest_route=\/wp\/v2\/posts\/12\/revisions"}],"predecessor-version":[{"id":13,"href":"https:\/\/crimson-sheep-95571.zap.cloud\/index.php?rest_route=\/wp\/v2\/posts\/12\/revisions\/13"}],"wp:attachment":[{"href":"https:\/\/crimson-sheep-95571.zap.cloud\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=12"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/crimson-sheep-95571.zap.cloud\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=12"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/crimson-sheep-95571.zap.cloud\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=12"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}