@directivegames/genesys.sdk 3.3.5 → 3.3.7

package/dist/src/core/common.js

@@ -98,6 +98,9 @@ export async function readdirAsync(dirPath) {
     return await fs.promises.readdir(dirPath);
 }
 export function getProjectFolderAndFile(projectPath, logger) {
+    if (!fs.existsSync(projectPath)) {
+        return { folder: '', file: '' };
+    }
     const isDirectory = fs.lstatSync(projectPath).isDirectory();
     const folder = isDirectory ? projectPath : path.dirname(projectPath);
     if (!fs.existsSync(folder)) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@directivegames/genesys.sdk",
-  "version": "3.3.5",
+  "version": "3.3.7",
   "description": "Genesys SDK - A development toolkit for game development",
   "author": "Directive Games",
   "main": "index.js",

package/src/templates/AGENTS.md

@@ -56,6 +56,16 @@
 - **Do not** create documentation or test/example code unless specifically asked to.
 - Be **very brief** on the summary when the implementation is completed.
 
+## Engine Source Reference
+- The engine source code is available in the **`.engine`** folder at the project root.
+- Use the engine source as the **primary reference** when implementing game code to understand:
+  - Class hierarchies and inheritance patterns
+  - Available methods, properties, and their signatures
+  - Engine conventions and coding patterns
+  - How built-in features are implemented
+- When extending engine classes or implementing similar functionality, **study the existing engine code** to ensure consistency and proper integration.
+- The `.engine` folder mirrors the structure of the engine package — search here first when you need to understand how a particular system works.
+
 ## UI
 - Any HTML UI you create **MUST NOT** be added to the document root directly. Add them to the game UI container, which can be accessed through `world.gameContainer`.