The format for bootstrapping the starting config file is slightly different to a regular Orx application as shown here.

When an orx/Scroll game or application starts, the matching config data file is expected to reside in the same folder as the executable, and to have the same name as the executable.

To change this, add a Bootstrap prototype to your Scroll header:

class MyGame : public Scroll<MyGame>
{
private:
	virtual orxSTATUS Bootstrap() const;
        //Other function prototypes here
 
};

Note the use of const above.

In your Scroll class, simply drop in the Bootstrap function:

orxSTATUS MyGame::Bootstrap() const
{
 
	// Add "../data/config" to the list of locations that config files can be loaded from
	orxResource_AddStorage(orxCONFIG_KZ_RESOURCE_GROUP, "../data/config", orxFALSE);
 
	// Loads a specific config file 
	orxConfig_Load("my-game-config.ini");
 
	return orxSTATUS_FAILURE;
}

Scroll will automatically pick up the Bootstrap function if it has been provided.

Your Scroll application will now call its root .ini file from some other location relative to the .exe.