On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
Tags

Hi,

If any of the above are premium, running their own code while the game is running and your code calls for functions from code you did not write (from a plugin) or it excecutes by itself then it would not be allowed.

If the tools are used to create assets which are then used in the game and all the work is done by your own code or functions being called on are from free plugins it is allowed.

If your game can do something while it's running that is not the result of code you wrote yourself or code that came from a free source it's likely disqualifiable.

Hey there! Thank you for the response, I wanted to ask for a bit of clarification. I'll use FMOD as an example.

FMOD allows me as the composer and sound designer to create an immersive audio experience using this external tool. It does not require payment, unless your game hits a certain income threshold (which does not apply to our jam plans!). There are code calls within the FMOD Api that allow us to use this functionality in our game and access the presentation of the assets I've created. Is this allowed? Or, am I as a composer/sound designer expected to be able to build all audio functionality with code and no middleware tools?

A second question I have is - technically a game engine (such as Unity) is running code at runtime that the game dev does not write. I would like to ask if that disqualifies Unity from being utilized? I saw that engines were mentioned as okay - but I'm curious where the line is as far as what counts as "code running at runtime" :)

The second question is not being cheeky - just an attempt to get a better sense of the boundaries, so we can appropriately participate in the jam, and plan our process and resources most effectively. 

Lastly - your response "If any of the above are premium, running their own code while the game is running and your code calls for functions from code you did not write (from a plugin) or it excecutes by itself then it would not be allowed." - does this ultimately mean that if a plugin is free, it is good to go? Or, is it that any one of the following disqualifies the asset: 1. premium, 2. running their on code, 3. executes by itself

If any of this doesn't make sense, just let me know! Just trying to get our tech stack sorted, ya know :D

Thank you!

Jamie