UniF-Logger

Usage

Before logging, you must tag yourself `unif.debug`

And the following is a logging example. ``` [0:1000] [INFO] (NAMESPACE) MESSAGE ```

- `[0:1000]` is the time of the game when logging. It means that log was created at the time of 1000 on the day 1 of the game. - `[INFO]` is the type of the logging. There are a total of 6 levels, `ALL` < `DEBUG` < `INFO` < `WARN` < `ERROR`. And type `TIPS` is displayed to normal players, it has no stoarge. - `(NAMESPACE)` is the namespace of the logging.

After logging but logging of DEBUG, all logging will record into stoarge `unif.logger:logs`, and there are also 4 stoarges: `unif.logger:debug_logs`, `unif.logger:info_logs`, `unif.logger:warn_logs`, `unif.logger:error_logs`.

When the logs is going to be too big, it will auto delete the last log in logs.

General Logger

This is a example to print a general logging. ```MCFUNCTION function #unif.logger:logger/v1/info {"msg": 'Here's some messages!', "namespace": "Test"} ```

Injected Logger

Warning: Warning: Injected Logger can inject clickable JSON fields like clickEvent.

```mcfunction function #unif.logger:injected_logger/v1/info {"msg": "{"text":"Injected Info Test"}", "namespace": "Test"} ```

```mcfunction function #unif.logger:injected_logger/v1/info {"msg":"{"text":"Injected Info Test","hoverEvent":{"action":"show_text","contents":"aa"}}","namespace":"UniF-Logger"} ```

Logs

Read logs

You can use the following functions to read logs in the past.

```MCFUNCTION function #unif.logger:logs/v1/read_all function #unif.logger:logs/v1/read_debug function #unif.logger:logs/v1/read_info function #unif.logger:logs/v1/read_warn function #unif.logger:logs/v1/read_error ```

Clear logs

You can use the following functions to clear logs.

```MCFUNCTION function #unif.logger:logs/v1/clear_all function #unif.logger:logs/v1/clear_debug function #unif.logger:logs/v1/clear_info function #unif.logger:logs/v1/clear_warn function #unif.logger:logs/v1/clear_error ```