@myvillage/cli 2.6.0 → 2.6.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@myvillage/cli",
-  "version": "2.6.0",
+  "version": "2.6.1",
   "description": "MyVillageOS CLI for community developers",
   "type": "module",
   "bin": {

package/src/commands/deploy.js

@@ -257,7 +257,7 @@ async function deployThreeJsGame(projectDir, pkg, options = {}) {
     const metadata = {
       title: pkg.myvillage.name || pkg.name,
       description: pkg.description || '',
-      category: (pkg.myvillage.gameType || 'OTHER').toUpperCase(),
+      category: toGameCategory(pkg.myvillage.category || pkg.myvillage.gameType),
       gameType: 'THREE_JS',
       targetAge: pkg.myvillage.targetAge || 'all',
       orientation: pkg.myvillage.orientation || 'landscape',
@@ -521,7 +521,7 @@ async function deployUnityPlatform(projectDir, mvConfig, platform, { gameIdOverr
     const metadata = {
       title: mvConfig.name,
       description: mvConfig.description || '',
-      category: (mvConfig.category || 'OTHER').toUpperCase(),
+      category: toGameCategory(mvConfig.category),
       gameType,
       targetAge: mvConfig.targetAge || 'all',
       orientation: mvConfig.orientation || (platform === 'webgl' ? 'landscape' : 'portrait'),
@@ -775,6 +775,15 @@ function formatStatus(status) {
   }
 }
 
+// The platform's GameCategory enum. A Three.js "custom" type (the create-game
+// default) isn't one, and sending it as-is fails the deploy server-side.
+const GAME_CATEGORIES = ['ACTION', 'PUZZLE', 'ADVENTURE', 'EDUCATION', 'QUIZ', 'EXPLORATION', 'NARRATIVE', 'OTHER'];
+
+export function toGameCategory(raw) {
+  const v = String(raw || '').trim().toUpperCase();
+  return GAME_CATEGORIES.includes(v) ? v : 'OTHER';
+}
+
 function getContentType(filePath) {
   const ext = filePath.split('.').pop()?.toLowerCase();
   const types = {