Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Thanks for the reply! I am not positive about the Steam Workshop aspect, because I was using Google Gemini and that's what it said was the issue.  Here's the explanation it gave me before switching to trying manually doing it locally.

The "Uncaught (in promise) Error: access denied" combined with a 0% hang is a very specific error from the Facepunch.Steamworks library. Since the game is so new that it doesn't have a public Workshop yet, this error actually confirms that the game's AppID is currently restricted by Steam.

🧩 Why this is happening

Even if a developer has added the "Upload" button to their game, Steam doesn't allow users to create Workshop items until the developer has:

  1. Fully Published the Steam store page.
  2. Enabled "ISteamUGC" for file transfers in the developer backend.
  3. Configured a Cloud Quota (the default is often 0 bytes, which causes an immediate "Access Denied" or 0% hang when you try to push files).

Because you are likely using a build where these "permissions" haven't been switched on by the developer yet, your account is being "denied access" to create a new item on Steam's servers.

Once I started manually injecting the mode I made progress. I was just using the "awesomeMod" that comes with the game. The settings seemed to align with your written directions on how to make mods and of course was provided by you. Since the built-in mods feature wasn't working, I accessed the Console and used the following commands to load it in. 

var script = document.createElement('script');

script.src = 'mods/awesomeMod/scripts/script.js'; 

document.head.appendChild(script);

Settings.mods.push("awesomeMod");

updateMods();

The game incorporates the mod, but when trying to open the Library or getting to a choice with one of those cards in the game it gives the error below.

TypeError

Cannot read properties of undefined (reading 'width')

TypeError: Cannot read properties of undefined (reading 'width')

at Card.draw (file:///C:/Program%20Files%20(x86)/Steam/steamapps/common/Galactic%20Overlord/js/Card.js:162:38)

at file:///C:/Program%20Files%20(x86)/Steam/steamapps/common/Galactic%20Overlord/js/CardViewer.js:96:30

at Array.forEach ()

at CardViewer.draw (file:///C:/Program%20Files%20(x86)/Steam/steamapps/common/Galactic%20Overlord/js/CardViewer.js:96:12)

at Object.draw (file:///C:/Program%20Files%20(x86)/Steam/steamapps/common/Galactic%20Overlord/js/states/Title.js:91:37)

at update (file:///C:/Program%20Files%20(x86)/Steam/steamapps/common/Galactic%20Overlord/

Hmm, that is a very strange error indeed, especially since I'm not using the Facepunch.Steamworks library.  I've confirmed ISteamUGC is enabled and the cloud quota is set to max, so I'm not sure what's happening here.  I might need to contact Steam to get the bottom of this, but I'll keep poking around!

Also, the game should automatically inject the tags corresponding to your mod if the files are just in the mods folder in the game's directory.  It looks like the error it's throwing is caused by the path to the card image being incorrect, so maybe doing it that way instead of the (admittedly cool) console hack?

Sorry this is a pain, you should definitely be able to mod.  I'll let you know when I work this out!

Thanks, I know you're focusing on your other game for release this year from what I saw.

When you say that the files are in the mods folder, do you mean the raw files or inside the folder for the specific mod? If it's the latter, that's what I currently have. Otherwise I can pull files out so that they're all in the main mods folder of the game.

I mean the folder of your mod should be in the mods folder, like: mods/awesomeMod/(files).  Are they not showing up without the dom injection when you load in?

Correct, nothing happens unless I inject them. I have attached a screenshot of my mods folder. The aweseomeMod contents are an exact copy from the game folder one level up.

Ok then, that's definitely a bug.  I'll look into this and let you know when it's fixed!