Ok so I read mta scripting wiki
Explain this a bit more for me:
Second example - A gamemode
/counterstrike
/meta.xml
/counterstrike.lua
/buymenu.lua
The counterstrike.lua contains similiar to the following features:
Let players choose their team and spawn them
Provide them with weapons, targets and instructions (maybe read from a Map, see below)
Define the game's rules, e.g. when does the round end, what happens when a player dies
.. and maybe some more
The buymenu.lua is a clientside script and creates a menu to buy weapons
This example can be called a gamemode, since it not only intereferes with the gameplay, but actually defines the rules of it. The type attribute indicates that this example works with the Map manager, yet another resource that was written by the QA Team to manage gamemodes and map loading. It is highly recommended that you base your gamemodes on the techniques it provides.
This also means that the gamemode probably won't run without a map. Gamemodes should always be as generic as possible. An example for a map is stated in the next example.
So I create a Counterstrike.lua (as example , mine is named different) for this script
/counterstrike
/meta.xml
/counterstrike.lua
/buymenu.lua
then where do I place this one?
And what to place in buymenu.lua ( I mean what commands)