This is a short version of the game acceptance guidelines. Use these guidelines as a loose guideline when crafting a game concept. Please refer to the Terms and Conditions for the full guidelines.
Sulake reserves the rights to accept and remove any content at any time. The main rule though is to allow all content, as long as the guidelines are followed and the game is of acceptable quality & stability.The preference is to have fun multiplayer games, although single player games are also accepted. Game modes can be just about anything from fast paced realtime (racing) to slow turn based (chess) games.
Habbo is targeted to teen audience and thus game content should be suitable for that age demographic. Most users are between the age of 13 and 15 years. Gender ratio is roughly 55/45 of boys/girls.
Each Habbo site is in the local language. Localized user interface in games for each Habbo Hotel language is preferred but is not mandatory. Be aware though that the majority of players are not fluent in english and may feel frustrated if the game is not localized. It may also cause negative customer feedback.
Our registered users are interested in these Google categories:
Our website has the greatest affinity (page ranked) with these Google categories:
The following content is explicitly not allowed in games:
Habbo has a strict moderation policy. All player output is filtered and moderated within the Habbo Hotel context. Due to this requirement, chatting in games is unfortunately not allowed. Also user uploaded images are not allowed and any sharing of user details is prohibited.
Habbo Gaming API has notification functionality to reach players friends. Notifications can be sent to a player's online or offline friends. Notifications do not contain additional information, it only shows to a friend that a certain game has new content waiting for him or her. Try to have the new content visible to the player upon entering the game. Notifications are persistent and are fully reset from Habbo (not just between one friendship) when the player opens the game. Avoid spamming with notifications and send them only based on user interaction.
Allowed: Player A makes his move in turn based game against player B. Game sends notification to B. If B is currently playing the same game, the notification is only shown within the game. If B exits before seeing the notification, the game can do the API call and B gets notification on Habbo.
Not allowed: Player A plays the game but does nothing related to player B. Game notifies B.
Notification marks shown on game icons
Invites are sent to player's online friends that are not currently in game. Invites should be sent from player interaction and player needs to choose invitees. Invites are not persistent.
You can monetize your game by providing in-game purchases for players. These purchases can for example be game powerups or you can provide your own premium currency that is purchased using Habbo credits.
All in-game purchases that players can make using their Habbo credits must clearly indicate that player is using his credits.
You can cross promote another game within Habbo. Advertisements or cross promotions external to Habbo are not allowed.
Linking to external sites is not allowed, other than support page for game. Game help should be contained within the game, not on an external site.
Game should have a way to exit back to Habbo client at any time, even after a possible game crash. Our suggestion is to have an exit button always visible or a maximum of one step to game's main menu that contains an exit.
Continue to Developing Games.