Community coding tips and best practices (please contribute)

Workshop Discussion
1

I’ll edit this post with good suggestions and proper credit. Anything that would make debugging or coding easier for people. Maybe we could make this into some kind of community defined coding convention. ¯\(ツ)/¯

Coding tips:

Try having a rule for each player that just infinitely loops printing out a small message so you don’t have to keep checking the inspector for a variable that changes fast/needs to be checked often. -pinghajen

The following code allows you to see your coordinates on a map for purposes of placing effects, spawns, TP locations, etc.:
Create HUD Text(All Players(All Teams), Position Of(Event Player), Null, Null, Left, 0, White, White, White, Visible To And String - bagof4grapes and AnEnemyChampion on Youtube

When creating effects using the “Create Effect” or “Play Effect” actions, make sure to use “Position of ( Event Player )” as opposed to just “Event Player” when setting the position, or the effect will not be at the player’s position. - AnEnemyChamp

Good coding practices:

As long as there is no space for commentary, it is a good idea to put the description of the variables used in the script into the names of the rules on the top. Additionally, a list with the variables wich are not used yet is very helpful too. -Shanalotte

2 Likes
2

This one helped me a ton. The following code allows you to see your coordinates on a map for purposes of placing effects, spawns, TP locations, etc.:

Create HUD Text(All Players(All Teams), Position Of(Event Player), Null, Null, Left, 0, White, White, White, Visible To And String

Credit goes to AnEnemyChampion on Youtube.

1 Like
3

As long as there is no space for commentary, it is a good idea to put the description of the variables used in the script into the names of the rules on the top. Additionally, a list with the variables wich are not used yet is very helpful too.

2 Likes
4

When creating effects using the “Create Effect” or “Play Effect” actions, make sure to use “Position of ( Event Player )” as opposed to just “Event Player” when setting the position, or the effect will not be at the player’s position.

Note that “Position of ( … )” is currently bugged for sounds in certain instances in the current version of the workshop.

5

Edited the original post with these suggestions :smiley: