priyanshu792/idle-viewport-game

Purpose and runtime

This is a Godot idle/viewport combat game. Godot project metadata and the configured startup scene are in project.godot; gameplay is assembled from .tscn scenes and GDScript, with resource-based unit, weapon, and upgrade definitions. No server or web runtime is evident.

Entry and scene composition

The application begins through Godot’s project entry configuration, then transitions between menu, gameplay, settings, and UI scene roots. The main gameplay composition appears centered on scene/main.tscn, driven by script/main.gd; menu flow uses scene/main_menu.tscn and script/main_menu.gd. The player, enemy, spawner, and shared UI are separately instanced scenes: scene/player.tscn, scene/enemy.tscn, scene/spawner.tscn.

Global coordination

Autoload-style global managers provide cross-scene control boundaries: event dispatch in globals/game_events.gd, level/progression coordination in globals/level_manager.gd, and window/UI visibility management in globals/windows_manager.gd. Gameplay systems should communicate through these globals or scene signals rather than tightly coupling projectile, UI, and level nodes.

Combat loop

The player and enemy actors drive the core loop: spawning enemies, targeting/firing weapons, applying damage, resolving health, and producing rewards/effects. Key implementations are script/player.gd, script/enemy.gd, script/spawner.gd, with reusable combat primitives in script/damage.gd, script/damage_calculator.gd, and script/health.gd. Enemies can drop collectible currency via scene/dropped_orb.tscn and script/dropped_orb.gd.

Weapon and projectile families

Weapons are implemented as independently instanced projectile scenes, allowing unlocks and upgrades to alter distinct behaviors. Families include base projectile (projectiles/projectile1/projectile.tscn), laser (projectiles/Laser/laser_projectile.tscn), multi-hit, orbital, spread-fire, and nuclear blast variants. Their scripts encapsulate movement/hit behavior, while visual effects use Godot shaders such as assets/shaders/laser_projectile.gdshader.

Data-driven stats and progression

Baseline actor and weapon values are Godot resources: resources/Base_Player_stats.tres, resources/Base_Enemy_stats.tres, and resources/Base_Weapon_stats.tres, backed by stat/resource scripts including resources/weapons_stat.gd. Individual upgrades are serialized .tres definitions under resources/upgrades/, including unlock, damage, speed, interval, radius, and target-count changes. This separates balancing data from runtime combat code.

Upgrade-tree and UI boundary

Upgrade selection is a dedicated scene subsystem: upgrades/upgrade_tree.tscn, upgrades/upgrade_tree.gd, and upgrades/upgrade_tree_node.gd. It consumes upgrade resource definitions and presents them through gameplay UI logic in script/upgrade_ui.gd and scene/ui.tscn / script/ui.gd. Settings are similarly isolated in scene/settings.tscn and script/settings.gd.

Tooling and external integrations

A custom editor CSV importer exists in addons/csv_importer/csv_importer.gd, with source spreadsheet/CSV content under csv_s/; it likely supports authoring/import of tabular upgrade or game data. The repository also vendors the Godot Git editor plugin under addons/godot-git-plugin/. These are editor integrations, not gameplay services.