Headless Bots and Retro UI: Developing the Game First Cosmic on Godot 4

⏱️ ~4 min read

Concept and Setting

The game «Pervy Kosmicheskiy» is a narrative idle/incremental game about the space race of the 1950s-1975, where players manage an OKB (Design Bureau) involved in developing space technologies. The game features a retro-UI that includes oscilloscopes, IN-14 lamps, punch cards, and teletype machines. This setting allows players to immerse themselves in the atmosphere of those times when every step towards the stars was filled with risk and uncertainty.

The main dilemma of the game is «Reliability vs Speed.» Players must balance the desire for quick progress with the need to ensure the reliability of their developments. This creates a unique gaming experience where every choice has significant consequences.

Multi-window Interface Architecture of OKB

The multi-window interface of OKB in «Pervy Kosmicheskiy» is designed considering real processes of construction bureaus of that time. Each window represents a subsystem that collapses and continues to feed resources into the following stages. This allows players to effectively manage their projects and track their progress.

For example, an oscilloscope window can display current test parameters, while IN-14 lamps signal the status of various systems. Punch cards are used for data storage and transfer between subsystems, adding realism and complexity.

Such architecture allows players to delve deeper into the process of developing space technologies and better understand how different system components interact with each other.

Main Problem of the Genre — Economic Balance

One of the key problems in the incremental games genre is economic balance. Manually testing 30 minutes of gameplay after every adjustment to the economic formula is simply impossible. This requires significant time and labor, making the development process very complex.

In «Pervy Kosmicheskiy,» we encountered this problem at an early stage of development. Every change in the economic formulas required lengthy testing to ensure that the balance was maintained and the game remained engaging.

Solution: Autonomous Headless CLI-Bot on GDScript

To solve the problem of economic balance, we developed an autonomous headless CLI-bot using GDScript. This bot allows for the automation of the testing process and checking metrics that are important for maintaining game balance.

The bot is launched with the command:

godot --headless --script res://scripts/run_playtest.gd -- --seconds 600 --profile balanced

This command runs the bot in headless mode, allowing it to work on a server or in the background. The parameters --seconds 600 and --profile balanced specify how long the bot should test the game and which profile to use for checking metrics.

The bot checks the following metrics:

  • Profitability: How many resources a player receives over a certain period of time.
  • Expenses: How many resources are spent on developing and improving technologies.
  • Performance Growth: How quickly the performance of various systems increases.
  • Reliability: The frequency of failures and their impact on overall progress.

These metrics allow us to quickly assess how changes in economic formulas affect game balance. If any parameters fall outside acceptable values, we can promptly make adjustments and conduct retesting.

Thanks to this bot, the development process has become significantly faster and more efficient. We were able to focus on improving the gaming experience rather than routine testing.

Repository Link

If you want to learn more about the development of «Pervy Kosmicheskiy» or try using our headless CLI-bot for your projects, visit our GitHub repository.

There you will find the game’s source code, documentation, and examples of bot usage. We would be happy to receive your feedback and suggestions for improving the project!

«Pervy Kosmicheskiy» is not just a game but an exciting journey into the history of space and technology. Join us and become part of this thrilling adventure!»

More from the Lab
← Failed BIOS Modification and Successful PC Revival: Lab NotesOptimizing WordPress on a Real Project: How We Compressed the First Screen by 82.3% →

Комментарии

Добавить комментарий

Ваш адрес email не будет опубликован. Обязательные поля помечены *