Developer Q&A: community questions answered

Studio Techtrics has shared a developer Q&A built around answering community questions about Floatlands. The responses cover procedural islands, resource gathering, crafting, base building, hostile robot NPCs and the technical work behind the low-poly presentation. They also explain what remains focused on single-player play and what may change when multiplayer arrives.

The team develops the game in Ljubljana, Slovenia, with feedback gathered from players across several countries. Australian players in Sydney, Melbourne and Brisbane have asked about performance, accessibility, local release plans and the survival systems that determine whether an expedition feels rewarding. The answers focus on the systems currently in development, known limitations and the possibilities outlined for future updates.

How are the islands generated?

Each island is assembled procedurally within one of Floatlands’ main environments: jungle, desert, sea or snow. The objective is to make every expedition feel different while preserving a coherent balance between travel, resources and danger. Landmarks, routes and resource distribution change, encouraging players to read their surroundings rather than follow a fixed map.

Answers about scarcity, landmarks and exploration are expanded in our desert biome field notes, which show why careful planning matters in a hostile environment. The desert creates particularly sharp decisions between pushing further, gathering what is available and returning to safety before supplies run low.

That design also suits the way many Australian players game around work, meals and commutes. A short expedition can still provide a complete cycle of gathering and crafting, while a longer trip offers more room to explore. Procedural variety keeps repeat visits relevant without requiring every session to follow the same routine.

What does survival involve day to day?

Survival begins with gathering raw materials and converting them through the crafting system. Players must decide which supplies are essential for immediate protection, which can support a base and which are worth carrying during an expedition. The resource chain gives each activity a purpose beyond simple collection.

Base building provides another layer of planning. A useful shelter can become a place to store materials, prepare equipment and recover between dangerous outings. The strongest bases are practical rather than decorative, since every improvement competes with the resources required for tools, exploration or combat.

Hostile robot NPCs add pressure to those choices. Players can avoid some encounters, prepare an ambush or use the surrounding terrain to gain an advantage. Combat therefore fits into the wider survival loop: preparation affects the result, and losing resources can make the next journey more difficult.

Will multiplayer change the game?

Floatlands currently focuses on single-player gameplay, with multiplayer planned for a future update. The team has not attached a firm date to that feature because its final form still requires design and technical work. This keeps expectations realistic while leaving room to test how shared play should interact with exploration, resource scarcity and base building.

A multiplayer version must preserve the tension that makes the islands worthwhile. Simply placing several players on the same procedurally generated terrain would not guarantee meaningful cooperation or competition, so the studio is considering how players interact, communicate and divide their objectives.

Until those decisions are settled, the robot NPCs continue to provide the main source of opposition. Future updates will explain which multiplayer ideas are being tested, what the community can try and how the feature may differ from the current single-player experience.

What is behind the low-poly look?

The low-poly style gives Floatlands a distinctive identity while helping important objects remain readable in dense environments. Simplified forms can communicate distance, terrain changes and potential threats more clearly than highly detailed assets, which is valuable when players need to scan a jungle path, snowfield or desert horizon quickly.

Procedural generation adds a separate technical challenge because each combination of terrain, resources and structures must behave consistently. The team balances visual variety with rules that remain understandable, ensuring that unusual island layouts feel surprising without making the underlying systems arbitrary.

The latest development update explains more about the studio’s technical approach and current priorities. It also provides the clearest picture of how systems are being refined before Floatlands moves beyond its development phase.

Australian PC players are accustomed to discovering independent games through Steam wishlists, digital sales and community promotions, while boxed PC stock is less prominent than console inventory at major retailers. Clear regional pricing, demo access and release information will therefore be important when an Australian launch is confirmed.

What happens next for the community?

The public roadmap and development logs are the main sources for information about upcoming changes. The team uses them to show which systems are being worked on, which ideas remain under consideration and how community feedback has influenced the game. Planned features such as multiplayer should be treated as roadmap goals until an update confirms their release.

Australian distribution also involves legislation and regulatory processes. The Australian Classification Board assesses commercial game material and marketing, while Australian Consumer Law requires accurate descriptions and clear terms for digital purchases. Because robot combat is central to the game, Australian trailers and store assets may require classification before distribution.

Follow Floatlands for roadmap changes, explore the current single-player experience and share focused feedback with the community. Players who want to influence future additions can watch the development logs, discuss the systems that matter to them and participate when new features enter testing. The next stage of the islands is already taking shape in Ljubljana, and the community can help guide what arrives there next.