• 🏆 Texturing Contest #33 is OPEN! Contestants must re-texture a SD unit model found in-game (Warcraft 3 Classic), recreating the unit into a peaceful NPC version. 🔗Click here to enter!
  • It's time for the first HD Modeling Contest of 2024. Join the theme discussion for Hive's HD Modeling Contest #6! Click here to post your idea!

Tools System 1.1

This bundle is marked as useful / simple. Simplicity is bliss, low effort and/or may contain minor bugs.
It looks like kinda Warcraft III console application, well, at least i tried to make it looking like.
Basics:
Command trigger: ` (~ without Shift) or !!(for some commands)
`man - manual for [category/command]
`list - list of commands
`ban - ban command setting (e.g. `ban name - ban name setting)
`unban - opposite of ban - enables a command setting. E.g. unbanall - unban all command setting.
!!sudo [command] [value] - to execute a command ignoring bans.
!!kick [player number] - kick the player from the game.
And so on.
I've taken some commands, as you see, from UNIX command prompt.

New commands added (see them all in triggers).
All operator commands have !! command trigger.
Triggers are divided.

Keywords:
tools, utilities, system
Contents

Еще одна карта (Map)

Reviews
12th Dec 2015 IcemanBo: Too long as NeedsFix. Rejected. 23:30, 8th Mar 2014 PurgeandFire: It sounds cool, but please update the description to have the triggers. Or make a post with the triggers in tags and then link to it in the description.

Moderator

M

Moderator

12th Dec 2015
IcemanBo: Too long as NeedsFix. Rejected.

23:30, 8th Mar 2014
PurgeandFire: It sounds cool, but please update the description to have the triggers. Or make a post with the triggers in [TRIGGER][/TRIGGER] tags and then link to it in the description.
 
Don't use "Do nothing" action. It's a useless action which just does "nothing".

Avoid doing further checks if string comparrison is matching. You can do it by putting further If/Then/Else block into the 'Else' of the first block.
Even better would be to create a single trigger for each command, to prevent useless checks.

If you use integer comparrisons like following more often, store it in an integer variable, and simply compare this integer instead of new function call:
  • (Integer((Substring((Entered chat string), 8, 9)))) Kleiner gleich 12
In your color command for example, you make check for each single color like: If string == color red, If string == color blue ....
You can avoid this by creating a String[array] and a PlayerColor[array] variable, and then check with a simple loop:
Loop LoopInt from 1 to 13:
If EnetredChatString == String[LoopInt] then set Color to Color [LoopInt]

That was not really a review, just some quick feedback. Good luck with your first ressource :csmile:
 
Last edited:
Top