AL5 changed where containers are stored

Containers are now stored in there own table with the below schema

CREATE TABLE `containers` (
  `id` int(6) NOT NULL AUTO_INCREMENT,
  `pid` varchar(17) NOT NULL,
  `classname` varchar(32) NOT NULL,
  `pos` varchar(64) DEFAULT NULL,
  `inventory` text NOT NULL,
  `gear` text NOT NULL,
  `dir` varchar(128) DEFAULT NULL,
  `active` tinyint(1) NOT NULL DEFAULT '0',
  `owned` tinyint(1) DEFAULT '0',
  `insert_time` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
  PRIMARY KEY (`id`,`pid`)
) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4;

And a sample row

INSERT INTO `containers` (`id`, `pid`, `classname`, `pos`, `inventory`, `gear`, `dir`, `active`, `owned`, `insert_time`)
VALUES (1,'76560000000000000','B_supplyCrate_F','[20767.8,6730.18,0.402126]','\"[[[`peach`,4]],4]\"','\"[[[],[]],[[`Chemlight_yellow`],[2]],[[],[]],[[],[]]]\"','[[-0.663391,-0.748273,0],[0,0,1]]',0,1,'2016-11-14 04:16:43')

Cyberbyte-Software / CyberWorks

AL5 changed where containers are stored #87