create a bash with something like :
MaratisPlayer.app/Contents/MacOS/MaratisPLayer "" 1024 768 1

Do you have a Mac/bash/shell version for this process? It'd be great to know.

Thanks.

1) Publish your game

2) In that published folder create a new text file that has the same name as your game's exe file.For example, if your game's exe is called Mario.exe create a text file called Mario.

Open the text file and type:

Mario.exe "" 1024 768 1 

This will make your game display at 1024 x 768. You can make it whatever you want.

Now save this text file as a .bat file.
(Change the file type from .txt to ''any file'', and type Mario.bat.)

That's it.
When you run the game, don't run it using the Mario.exe file, run it using the Mario.bat file

If you publish your game (for example a game called "MyGame") then you have the whole package in the publish-subdirectory of your project. In it there will be an EXE called "MyGame.exe". However when you start it it will always run in windowed mode. To force it to run in fullscreen-mode you have to create a Batch/Bash-Script with the line:

MyGame "" [width] [height] 1

so for 1024x768 it would be:

MyGame "" 1028 768 1

Alternatively you can create a Shortcut/Link to the EXE with this line in it.

About fullscreen, you can find a post talking about it there : http://forum.maratis3d.com/viewtopic.php?id=277
It's with a command line argument :

First of all I have to compliment the Maratis-Team. You've done an excellent job so far and I'm very excited about the new beta especially the new publish pipeline. Now it's possible to share your little games without letting the others view deeply into your assets and scripts which is a big deal for that kinda tool, I think. However I'm wondering how to run the published games in fullscreen. I have searched the forum for this problem, but found nothing. Is this possible with the beta or will this feature be included in the future? However as a kind request, maybe it would be a good idea to implement such a display-mode change as a function in the scripting pipeline so one could realize an ingame-menu for that.

At last I want to give you a list of points which I liked the most about maratis and which I think are the key-strengths of the tool:

- Extremely self-explaining interface (could create a simple game almost instantly without looking into the documentation)

- LUA-Scripting (as imho lua has one of the best scripting-syntaxes so far)

- The interface between the Engine and the LUA-Scripting is straight forward (one function that handles everything instead of call-back-functions for every possible event)

- Blender-Content-Pipeline (Blender-Export-Script)

So lastly, thanks for maratis