2. Perform Connectivity Check with Test Client
Introduction
The Diarkis Server Template includes a test client designed to test commands. This test client is written in Go.
With this client, you can issue basic built-in commands to verify communication.
Building the Test Client
The binary for the test client can be built using the Diarkis server template.
The test client is built when you previously executed make build-local in the previous tutorial, so you can use that.
Launching the Diarkis Test Client
Execute the following make task:
$ make go-cli host=127.0.0.1:7000 uid=test1
:
[UID: test1][SID(UDP): b674cd4a79594581b90186818c1ef911]
> Connected UDPhost: Endpoint of the Diarkis server
uid: ID of the connecting user
clientKey: Client key (it is disabled by default and not needed this time)
ms (MARS Stats) Tool
This is a tool for retrieving current information from Diarkis.
It provides valuable data for analysis like current CCU, packet numbers, and Room numbers.
Creating and Joining a Room
Start two instances of the test client and try creating and joining a room.
Create a room using the room create command on one client, and then join that room using the room join command on the other client.
Create a Room with uid: test1
Join a Room with uid: test2
Verify CCU and Room Numbers with ms
Launching two instances of the test client and joining a room confirms that the CCU and Room numbers have increased.
Sending Messages to All Room Members
Use the room broadcast command to send any message.
You can also use the shorthand room + for the same purpose.
Broadcasting from uid: test1
Receiving the Message with uid: test2
Sending Messages to Specific Room Members
Use the room message command to send a message to a specific member.
Sending from uid: test1 to test2
Receiving the Message with uid: test2
Leaving a Room
Issue the room leave command to exit a room.
Checking Test Client Commands
Use the help command to see a list of available commands.
By adding a module name as an argument, such as help room, you can narrow down the commands to specific modules.
Last updated
Was this helpful?

