• 1 Overview
• 2 Server Solution
• 3 Client Solution
• 4 NeoAxis Engine template
• 5 Unity Engine template
• 6 Godot Engine template
• 7 Build Limitations
• 8 Serverless Project
• 9 See also

This page describes editing projects, including those created from base templates. To begin, it is useful to review creating projects and repository operations.

Projects typically have server and client parts. There are also serverless projects to publish content and apps that do not need a server to run.

The server part of the base templates is a .NET solution based on the NeoAxis Core Library.

The project is developed in Visual Studio or a similar environment on the client machine. Then a build for Linux is created using Publish and uploaded to the server with the NeoX app.

The client-side part depends on the engine being used.

To configure the client, you need to set your project number. You can find the number in the NeoX app, in the list of projects.

//connect to NeoX
var projectID = 2193;
var result = await CloudServiceClient.ConnectAsync( projectID );

Templates based on the NeoAxis include the engine and editor binaries. Installing the engine is not required.

During client development, you can fully connect to the server without uploading to the system. You can run under the debugger.

To create a build in the system, run Build from the NeoAxis editor. Then the build is uploaded using the NeoX app.

Folder structure:

• Server — Server source code.
• Server/Binaries_Linux — Server binaries.
• Client, Client/Project — Client source and binaries.
• Client/Builds/WindowsX64 — Client build for Windows x64.

Templates:

• Durak card game is a turn-based cloud game with matchmaking, an in-game GUI, and support for up to six players.
• Gomoku is a simple turn-based cloud game with matchmaking, for two players.
• Nitro Cars is a simple multiplayer racing game with matchmaking, server-side engine scene creation for 1–10 players.

The templates include a trimmed-down version of the NeoAxis engine client; some resources have been removed. You can copy them from the NeoAxis Engine SDK.

The Unity template includes both server and client parts.

• Server side: .NET solution based on the NeoAxis Core Library.
• Client side: Unity project.

Folder structure:

• Server — Server source code.
• Server/Binaries_Linux — Server binaries.
• Client/Project — Unity client project.
• Client/Builds/WindowsX64 — Client build for Windows x64.

Link to the template.

The Godot template includes both server and client parts.

• Server side: .NET solution based on the NeoAxis Core Library.
• Client side: Godot .NET project.

Folder structure:

• Server — Server source code.
• Server/Binaries_Linux — Server binaries.
• Client/Project — Godot client project.
• Client/Builds/WindowsX64 — Client build for Windows x64.

Link to the template.

Current limits for creating client builds and template builds:

• Maximum build archive file size: 30 GB.
• Maximum size of the extracted build files: 300 GB.
• Maximum size of a single file within the build: 10 GB.
• Maximum number of files in the build: 1,000,000.

A serverless project does not use a backend server. It is intended for publishing content and applications that do not require a server to run.

Select Serverless when creating a new project without a server.

Unlike a regular server-based project, a serverless project requires you to upload the build to Storage manually. The build is a ZIP file. As an example, you can download one of the project templates.

For projects with a client, add a file named 'Build.info' to the root of the archive. This file specifies the path to the executable. Example for Windows:

Executable = "Client/Builds/WindowsX64/Binaries/NeoAxis.Player.exe"

After uploading the build, connect it on the Publish tab by specifying it in the "Build Windows x64" property.

• Repository Operations: Push