Commands Aren’t Being Displayed

Issue

It seems that there is a common error people encounter where their custom commands will randomly not be displayed in the Cmdr terminal. The chances vary, but during my own testing it felt like if this was an issue you were to encounter, then you would encounter it about 90% of the time. Meaning your custom commands would only be displayed about 10% of the time.

Now you’re probably wondering…what causes this issue to happen? Unfortunately, I’m not 100% sure. What I believe causes this is module scripts we require in our custom commands or types stalling during the startup process of Cmdr. Stalling can occur from loops, using the WaitForChildMethod, or other ways as well.

Solution

After years of trying to solve this issue, one of our team members known as InsightGames005 found a solution.

The solution is very simple and only requires you to add a single line to your primary Cmdr script on the server side, which is used for setting up Cmdr on the server side. Towards the top of the script, you will paste the following code:

task.wait(5)

What this will do is delay Cmdr from being setup on the server side for the first 5 seconds. This should be more than enough time for any module scripts to finish whatever work was stalling them. If you’re still encountering the issue then you may want to increase the time.