ㅤThere are some fundamental rules for your lua event project to follow, as well as important notes for its development. Most of them were extracted from my previous experience with events, with that said keep in mind that expections can always be made in certain cases.

Rewards

• You don't need necessarily to offer a reward in your event, they are optional. However, people are more likely to enjoy it if they can get something when they complete it.
• Admins will always give the final word in regards of rewards (the text, the art, the concept, the quantity), so it's important that you always have a plan B idea in case they reject it.
• You cannot prize a player with more than one reward per goal, nor you should create slightly different goals just to be able to give more rewards. "Don't make an event for your reward, make a reward for your event."

Titles

• According to the admins, the current quantity of titles is exorbitant, i.e., they will always prefer that you only offer one, not two or three, titles per event.
  • With the exception of very complex or big events, or if one of the titles already exist (from past events).
• Mention them in English, since they will be discussed among other members of other communities. If you have a translation preference, make sure to include it in your message too! (E.g.: The title is AAA and in french it should be BBB)
• It is recommended that smaller/simpler events offer titles rather than badges or orbs


Badges and Orbs

• They can't be given as a prize for solving an enigma. Only titles can.
• The Flash Squad is, probably, going to draw the suggested badge or orb so the game's style is respected. With that in mind, make sure to share a big image and not a tiny one.


Consumables

• You may give consumables in your event, however they are limited and not all of them are available. All consumables mentioned in https://transformice.fandom.com/wiki/Inventory are available, but some of them must be given in specific ways:
  
  • Costumes and Pets are given through system.giveEventGift and a string is used instead of a numeric id. The string has to be requested to Tigrounette.
  • You can only offer 20 seashells per day.
  • You can only offer 5 gold tickets per day. If you need more tickets, it has to be given through system.giveEventGift with a string offered by Tigrounette.
• You can only offer 10 consumables per day. Don't make them the main rewards, they must be well distributed.

• By launching a lua event, you'll have a big responsibility for technical issues and maintenance. You must not leave the project.
• You must not create "shortcuts" for your event to get the prize(s) faster. Favoritism is totally prohibited. Do not make commands to give the title to someone, to give powers for specific players or to prejudice other specific players.
• You are free to credit the developers, designers, translators and everyone who helped with the project development, but keep in mind that a lua event is meant to be just fun, not to promote players. Be reasonable!
• You can update the event as needed, it will not break the ones currently being played in other rooms until the next round!

• The map time in the event is very important. Do not make a gameplay that requires a lot of time to complete. The admins suggest 2 or 3 minutes maximum. Higher than this, the project becomes unviable.
• You can make a thread in the map submissions section to get maps from players for the event, but it is recommended to use an unique map with some good art.
• The map is limited to 509 objects that can collide, i.e.: grounds, players and objects. Thus, if your map has 500 grounds, rooms with more than 9 players will crash. With that in mind, make sure not to exceed ~430 grounds.
• Prefer maps that won't rely on nails or shaman objects, as they can glitch a lot depending on the current synchronizer of the room.

• Your code must be clear and efficient, otherwise it won't pass the admins' and lua team's approval.
  
  • Note: Events support 300ms of runtime!
• Define a name for the module to make its identification easier later. For example, evt_new_year_balloons.
• While the event is live, you are free to edit the code for maintenance purposes only. Taking care is required while you edit the code: be sure to test the new code before updating the event. You should not implement new significant features to the project once it's launched for the first time.
• Make sure to list all the functionalities, commands and relevant stuff of the event to the responsible administrator. They will check it to avoid mistakes later. Do not add enigmas or any different gameplay after the release.
• The player data is a really important part of the event. Use them eficiently. First, you need to ask the member who is willing to host the event what data manager they use, if they do. You must use the same data manager to avoid compatibility errors with the formats that already are saved in their files.

• The communication with the players during the event is essential. The more languages you implement in the code, the better the event will be.
• The mandatory languages in your event are: EN (English), BR (Portuguese) and/or PT (Portuguese) (they can be the same), ES (Spanish) and FR (French).
• If possible, share the translator names to credit them: they are as important as developers and artists! Use trustable fonts, translating your event using google translate or non fluent people is highly unrecommended. If you don't know who to ask for translations, ask for help of the Event Squad!

• You can not replace mice image (target %).
• You can not change the score of players.
• You should not change the power of snowballs (second argument of tfm.exec.snow), because it sometimes have an unexpected behavior that ends up affecting other maps' gameplay.