Submitting a Game

Submission rules

Before packaging your game for submission, check out this rules before proceeding to Preparing the submission package.

TAB Austria will consider to accept your game for integration to the F4F platform if it at least meets the following rules. Note that this is no guarantee that your game will be accepted. If we think the game does not contribute to our ambitious targets, it might happen that we reject your application disregarding the rules. To avoid this just make sure to talk to us before and during your game development to make sure that you're working into the right direction. Then there'll be less issues upon submission of your game.

On the other hand, you can be 100% sure that you'll NOT be accepted to our platform if you do not follow the requirements listed below. So please help us save your and our time by not submitting games to us if you know that you violate one of those terms. If you are unclear about a certain requirement or you need some exception, contact us at sdk@tab.at and he'll be happy to help you.

TAB Austria is reserving its right to change the terms and conditions below at any time as being required by the marketplace, our customers, our players or by law. We also reserve our right to at any time withdraw your game from our offering even if it has been accepted to our platform beforehand, if we're required to do so by law or by important reason.

General rules

• Games need to be free of critical bugs and need to behave like advertised to an end user. We will not accept games, that are buggy or are otherwise not playable in normal means by the end user.
• The design of the games needs to be in perfect quality, both on graphics, text and programming side. We will not accept games that are of sluggish design or where we see that no love has been put into its design.
• Games that perform slowly or laggy on our table will be rejected. Please especially consider the section on Handling Videos if you're using video playback within Unity.
• Games should be designed to an average duration of 5 minutes. Games must not exceed playing time of 10 minutes to keep total over-time-income of the F4F table on a good level. If games have a non-time termination condition, there should be a hard-coded time termination condition at 10 minutes. If you implement a hard-coded time termination condition make sure the user understands at the beginning of the game that the maximum time duration of the game will be 10 minutes. Please note that it is perfectly fine to offer an Continue option to the user after the game time has passed, as the user will always have to buy new credits to continue playing.
• Games need to provide a proper splash screen while loading game content.
• The splash screen must have the format of 1920 x 1080 pixels, and is required to switch the game to full screen mode immediately after launching.
• Games do not need to provide highscores to the F4F platform. If a game does, however, the provided highscores need to be meaningful regarding comparison perspective.
• Each game must allow the user to exit early.
• The game must, if an early exit is being triggered, ask the user to confirm the exit decision before actually quitting the game.
• Games must handle touch input properly. Please consider that touch inputs are limited to 40 touches at the same time. Games do not have to support single touch tables but if they do not support single touch tables they'll not be distributed to those devices, resulting in potentially decreased game starts (see Performance and Features).
• Games that abuse our system, or perform other unwanted or criminal behavior on our platform, will be rejected.
• Companies or games that promote platforms which compete to the F4F platform, will not be accepted to our program and can even be excluded from our program even if the game has been accepted to our platform beforehand.
• Content which will cause monetization of our platform through a party which is not TAB Austria, is not allowed.
• Games developed for the Fun4Four need to be designed for a resolution of 1920 x 1080 pixels.

Content restrictions

• It is forbidden by law in some countries to provide games within public space that contain realistic illustrations of killing of humans or animals. Due to that reason games portraying realistic images of people or animals being killed or maimed, shot, stabbed, tortured or injured will be rejected.
• We will not accept games that contain pornographic material.
• Games that depict violence or abuse of children will be rejected.
• "Enemies" within the context of a game cannot solely target a specific race, culture, a real government or corporation, or any other real entity.
• Games containing references or commentary about a religious, cultural or ethnic group that are defamatory, offensive, mean-spirited or likely to expose the targeted group to harm or violence will not be accepted.
• Games may not use protected third party material such as trademarks, copyrights, patents or violate 3rd party terms of use. Authorization to use such material must be provided upon request.
• It is not allowed to display advertisements, paid or unpaid, within your game.
• It is not allowed to provide games that enable real-money gaming on our platform.

Translations

• Games need to at least provide translation to English and German. You do not need to provide additional languages, but please note that your game will not be published to devices which use a language unsupported by your game.
• If you submit translations, which are not complete or even partially outdated, your submission will be rejected.

Game help

• The game help needs to crisply and shortly describe the game to the user. It needs to tell the user in the easiest possible way what the game is about.
• The game help must not consist of more than 3 pages. If you need to use more please consult us, but better think if your game is either too complicated or if you can simplify your description.
• A help text of a page within the game help must not cause a line break (in english language) within the F4F menu.
• If possible, the game help must be animated, without too many static content.
• Game help animations should always in the easiest way describe the game to the user. Use zoom-ins, highlights etc. if it provides an advantage to the help content.
• In general we recommend that you talk to us before designing your game help. We might have good input to you from our experience in the field.
• Game help videos need to illustrate touches by using the files as specified in Visualization of Touches.

Submission format

• Games submitted must exactly match the submission format listed below. Mis-formatted submissions will be rejected.

---

Preparing the submission package

Preparing the submission package is really easy. Note that you'll have to submit ALL your game source files to us for review. The reason for this is that we need to absolutely make sure not to introduce security leaks to our devices, so we need to review the source code of your game. We'll however never share that content with third parties, nor will we use your code within our projects.

Please create the submission directory use following structure (regarding game IDs, see Requesting your game IDs):

• [GameID]
  • media
    • Resources.resx (mandatory, English)
    • Resources.ger.resx (mandatory, German)
    • Resources.[...].resx (other translation files)
    • menu
      • Help_v2_[GameID].avi
      • Help_v2_[GameID]1.avi
      • Help_v2_[GameID]2.avi
      • Icon_v2_[GameID].png
      • Icon_v2_[GameID]_small.png
      • Sound_[GameID].ogg
      • PlayerScreen_[GameID].png
  • UnityProject (for contents of this folder see Contents in the folder UnityProject)
  • [GameID].unitypackage (your Unity root package)
  • Screenshot.png (1920 x 1080 screenshot of typical in-game situation, used for game loading background)
  • Duly signed TAB Austria SDK Agreement
    • Download English version here
    • Download German version here
    • Print and sign
    • Scan and attach to the submission package
    • You will not have to re-attach the document on every re-submission, just upon the first submission of a product
  • ApplicantInfo.txt (fill the file you find for download here)

ZIP the [GameID] directory, and name the ZIP file [GameID].zip. Get an MD5 hash of the file using WinMD5.
Put the ZIP file to some location where we can access it (e.g. GDrive) and send the link + the MD5 hash to sdk@tab.at.

We know, that submission process is far from being perfect, but it will be improved over time.

Thats it - thanks for submitting :-). We'll then get in contact with you!

Contents in the folder UnityProject

The folder UnityProject only needs to contain the following:

• UnityProject
  • Assets (including everything in this folder)
  • ProjectSettings (including everything in this folder)

All other folders and files are created by Unity and its Import process, you do not need to submit those files.