Using SimulateClient for Development and Testing

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/FarlandsModdingTeam/TerbinProyect/llms.txt

Use this file to discover all available pages before exploring further.

​

How It Works

1. It creates a TerbinCommunicator in client mode (false) and connects to the running service.
2. It registers its own [TerbinExecutable] handlers so it can receive and print any response packets the service sends back.
3. In a loop it reads a command string from stdin in the format ClassName -MethodName.
4. It uses Commands.GetClass() and Commands.GetMethod() — two source-generated Regex helpers — to extract the class name and one or more -MethodName tokens from the input.
5. It resolves the class with Type.GetType("SimulateClient.<ClassName>") and the method with BindingFlags.Static | BindingFlags.Public.
6. It invokes the method, passing the shared TerbinCommunicator communicator instance.
7. If the resolved method returns a Task, it awaits it before prompting again.

classType = Type.GetType($"SimulateClient.{@class}");
// ...
methodType = classType?.GetMethod(meth, BindingFlags.Static | BindingFlags.Public);

var result = methodType.Invoke(null, new object[] { communicator });
if (result is Task task)
    await task;

​

Starting SimulateClient

dotnet run --project TerbinService

dotnet run --project SimulateClient

[Client] ¡Conectado!
-------( Start )---------
[Client] "Clase -Accion"
Command -> (  )

SimulateClient esta desactivado.
Ponga en false el if para activarlo.

​

Command Format

ClassName -MethodName

• ClassName — the name of one of the static command classes in the SimulateClient namespace (e.g. Inst, Plug, Game).
• -MethodName — the name of the public static method to call, prefixed with a hyphen.
• You can chain multiple methods in one line: Inst -Create -GetAll.
• Two numeric shorthands are built in: -1 resolves to Yolo and -2 resolves to LittleByLittle.

exit   ex   sa   salir   q

​

Available Command Classes

​

Example Session

-------( Start )---------
[Client] "Clase -Accion"
Command -> ( Inst -Create )

-------( Instance )---------
[Client] "Nombre de la Instancia"
[Client] name -> ( MyTestInstance )

[Client] Result (Action: ... | Status: Succes | Memory: 0)
CodeServices:Create
[Client] ==> FIN
[Client] Pulse cualquier tecla para continuar ...

-------( Start )---------
Command -> ( Inst -GetAll )

**( ReferenceInstanceDTO )**
  Name: MyTestInstance
  ...
----------
[Client] ==> FIN

-------( Start )---------
Command -> ( Plug -Add )

-------( Plugin )---------
[Client] "1. Nombre de la Instancia | 2. GUID del plugin"
[Client] 1. name -> ( MyTestInstance )
[Client] 2. GUID -> ( com.example.myplugin )
[Client] Result (Action: ... | Status: Succes | Memory: 0)
Instalado Correctamente

-------( Start )---------
Command -> ( exit )

​

Registering Custom Command Classes

1. Create a static class in the SimulateClient namespace.
2. Add public static async Task methods that accept a single TerbinCommunicator communicator parameter.
3. Build the project — your class and its methods are immediately available at the REPL.

namespace SimulateClient;

internal static class MyCommands
{
    public static async Task Ping(TerbinCommunicator communicator)
    {
        // send a packet, await the response, print result
        var r = await communicator.Communicate(
            new(CodeServices.Read, CodeServicesSection.Instances), []);
        Console.WriteLine($"Status: {r.Head.Status}");
    }
}

​

Helper Utilities