Move an Existing Project to Summer Engine

​

Move to Summer Engine

Summer Engine is the product you install and use. Its current upstream technical base is Godot Engine 4.6.1, and Summer follows upstream continuously. That lineage preserves familiar project formats and editing concepts, but it is not the Summer Engine product version and does not change the identity of your Summer game. Check the generated compatibility reference before migrating. It distinguishes measured facts from project-compatibility claims that have not yet been measured.

​

Profile Migration

If you are coming from Godot Engine, the node, scene, resource, and GDScript concepts are familiar. Summer Engine adds its own AI workflow and product surfaces, so verify plugins, editor customizations, and export behavior instead of assuming every detail is identical.

​

What’s the Same

The portable foundation includes:

• Node and scene concepts — familiar nodes, properties, and relationships
• GDScript — the default creator language in Summer Engine
• Text scene and resource formats — .tscn, .tres, and .gd
• Project configuration — project.godot
• Asset import metadata — verify on first open because importers can change upstream

​

Zero Lock-in

Summer games use upstream-compatible project formats: Summer does not require a proprietary replacement for these files. Keep the project in version control and review the first Summer Engine import diff before accepting it.

​

Team Workflows

Mixed-editor teams can share source formats, but should pin compatible versions and review generated import metadata:

• a collaborator may open the project in the compatible upstream editor,
• a creator opens the same repository in Summer Engine,
• both commit project files to the same repository,
• the team resolves real file changes through its normal review process.

​

Worst Case

Your GDScript, text scenes, resources, and assets remain in documented formats. Opening them in another compatible editor may require an import pass and will not provide Summer-only AI or platform surfaces.

​

What’s Different

Summer Engine adds its own AI-native workflow to the familiar technical foundation:

​

AI Chat Panel

• Location: Docked on the right side of the editor
• Purpose: Natural language interface to modify your project
• Integration: Directly connected to the editor’s APIs

​

Enhanced Workflow

Instead of manually clicking through menus:

1. Describe what you want - “Add a player character with movement”
2. Review the plan - Summer Engine shows you what it will change
3. Apply or modify - Accept changes or ask for adjustments
4. Undo if needed - All AI changes use the standard undo system

​

Project Compatibility

To try an existing Godot Engine project in Summer Engine:

​

Common Questions

​

Getting Started

Ready to try Summer Engine with your existing project?

---

Need help or have questions? Reach out to our founders at founders@summerengine.com or join our community on Discord for fast responses.