Updated · OASIS Team
OASIS Team develops its own games. Alongside them, we make development tools and software with practical uses of their own. Income from those published products helps finance continued work on our games.
Tools grow out of making
Building a game creates recurring needs. UCSystem focuses on object customization through models, materials and parameters. BCSystem explores modular building and connected structures. Work on these systems and work on our games inform one another.
UCSystem is available on FAB. BCSystem remains in development, with a separate release and integration with UCSystem planned.
Software beyond game development
UBS takes our software work into appointment booking. Customers and staff work through Telegram; a self-hosted Windows package keeps the bot running. Its editions serve specialists and teams with different scales of work.
A useful product needs to stand on its own. We want people to choose a tool or an edition of UBS because it fits their work. Supporting the studio’s original game development is part of what that income makes possible.
Products need a purpose of their own
A useful product begins with the work it helps someone do. For a development tool, that may concern creating and presenting interactive systems. For business software, it may concern organizing appointments and the people who handle them. Those needs deserve a clear scope and a practical description.
At OASIS Team, product income also supports the longer work of making original games. These roles belong together: the product needs to be useful to its buyer, and its income gives the studio another way to sustain development.
Game development takes more than an idea
Our games bring worlds, mechanics and interactive systems together. Those parts need to be developed, tried and revised as an experience. A project page can explain the direction, while public demonstrations and journal entries can make particular parts of the work easier to understand as they become ready to share.
This is why the studio’s public catalog distinguishes products that are offered to customers from projects still in development. They can support one another without sharing the same availability or release schedule.
A catalog that can keep growing
The current games, tools and software are part of an ongoing body of work. New needs can lead to new systems, and new projects can join the catalog when we have a useful public introduction to share. The website will grow with that work.
Future articles will collect product information, explain project directions and share confirmed materials from development. Following the journal or the studio communities is a way to stay connected without assuming that every update announces a release.
Support begins with a useful choice
If one of our published products fits your needs, review its official offer, requirements and terms. Following a game, sharing its public page or passing on a useful tool also helps the work reach people who may be interested.
The Support page brings together current public routes. Product purchases are purchases of that product; future game access, game keys and release dates are announced separately when confirmed.
The cover is an editorial studio illustration, not a game screenshot or a photograph of our workspace.
Share this page
