⚙️How to set it up

Before you start drying, you should pay attention to what is written here and do it.

Stop the evidence script you had before.

Clear the items created by the previous script completely from your inventory and item list.

Below are some important types and installation contents.

• Do not change the name of the script

• Put the script in the resources folder, do not use any folderisation.

• Prefer to start manually in server.cfg as follows.

• wais-compatibility script is required. Named wais-compatibility-hudv5 in Keymaster

• Take care to start the script manually after your core.

This is not the layout and appearance that should be in Server.cfg

ensure [yourcore]
ensure wais-compatibility
#ensure other-wais-scripts
ensure wais-evidence

---

You need to read the SQL Files. If you cannot access the files, the queries are below.

SQL Table codes where we will keep Evidence data.

CREATE TABLE IF NOT EXISTS `wais_evidence` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `job` varchar(15) DEFAULT NULL,
  `evidence_id` varchar(15) DEFAULT NULL,
  `details` longtext DEFAULT NULL,
  `time` timestamp NULL DEFAULT current_timestamp() ON UPDATE current_timestamp(),
  PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=15 DEFAULT CHARSET=utf8mb3 COLLATE=utf8mb3_general_ci;

---

If you are not using QS or OX inventory in ESX Framework, you should also read this table

CREATE TABLE IF NOT EXISTS `wais_analyses` (
  `id` int(11) NOT NULL AUTO_INCREMENT,
  `analyses_id` varchar(50) NOT NULL,
  `job` char(15) DEFAULT NULL,
  `data` longtext DEFAULT NULL,
  `time` timestamp NOT NULL DEFAULT current_timestamp(),
  PRIMARY KEY (`id`)
) ENGINE=InnoDB AUTO_INCREMENT=6 DEFAULT CHARSET=utf8mb3 COLLATE=utf8mb3_general_ci;