![]() ![]() Having a translation-ready script also helps with another thing, script maintainability in the long run. A script which is less prone to bugs and fairly more ready to be expanded.īy having created a universal script, you will automatically minimize possible issues of players running your script and the script non-working just because you worked the script on an archer world and the world the player is running the script is non-archer world or vice-versa. If you write your script to be universal and translation-ready you will already have created a script with strong foundations. Not world-specific, not unit-based specific (for example a script that only works on archer worlds but does not work on non-archer worlds). When working on a new script, try to make that script as universal as possible. is that worth it? Do we need a script to bring us to HQ and then another script to bring us to the Barracks? ![]() If instead, you are trying to "automate" 2 clicks. is this script worth it?ĭigitalization of a process (a.k.a script) is valid when you want to "automate" some complex/hard/repetitive task (for example sending resources from village to village, filling unit fields on rally point, etc). If it gains very little, like for example a script that redirects the player to HQ no matter where you are. Whenever you start working on a script think about what the player will gain from this script. So consider these suggestions as an open and fair discussion between developers, on how to improve scripts, instead of hard rules on how to write scripts. ![]() I will try to make my case to support those suggestions on each specific point as better as I can but you are not forced nor will you be denied script approval (if your script deserves to be approved) if it does not fit any of the suggestions below. You are not enforced to follow the suggestions mentioned below. So I will start by linking the official script rules and approval procedure:Įvery rule that is mentioned on the link above needs to be followed.Īll that comes below are only recommendationsbased on personal experience as a scripts author, they do not represent Tribal Wars official policy regarding scripts and scripting. In this article, I will share my own experience writing and maintaining Tribal Wars scripts. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |