wongerlt

if(p.getIPAddress().contains(player.getIPAddress()) & & p.getObjectId() != player.getObjectId()) {

nonsense

firstly check with phx multisell packet it is send correct item id

hmm, i have only one easy idea: example: when u send karma to client in server side change karma variable int mobskills = 75; int karma = 8564; int karmaplusmobskills = karma<<16|mobskills; then in interface ui script: _karma = _KARMAFROMSERVER>>16; _mobskilled = _KARMAFROMSERVER-(_karma<<16); something like this 😄

public boolean useVoicedCommand(String command, PlayerInstance activeChar, String target) { if(!activeChar.isGM()) return true;

seems problem server side.

after restart augment keep on same item with same aug skill? data appears in `augmentations` table?

i have used this pack 1132 and there no bugs with augment. u doing something wrong.

maybe after server wipe you not clear augment table in database.

i mean procedures not table... if not then: change CALL sellbuff_restoreSellerData(?) to SELECT * FROM sellbuff_seller_data WHERE char_obj_id=? change CALL sellbuff_saveSellerData(?,?,?,?) to INSERT INTO sellbuff_seller_data VALUES (?,?,?,?)

sellbuff_saveSellerData and sellbuff_restoreSellerData procedures.

did you create `procedures` in your main database? and why u use it???

but you tested ur query manually in navicat??? it's not weird you just didn't see mistake. just debug every action. easy.

in ur code print query, random example: try (Connection con = ConnectionPool.getConnection(); PreparedStatement ps = con.prepareStatement(INSERT_MACRO)) { ps.setInt(1, _owner.getObjectId()); ps.setInt(2, macro.id); ps.setInt(3, macro.icon); ps.setString(4, macro.name); ps.setString(5, macro.descr); ps.setString(6, macro.acronym); ps.setString(7, sb.toString()); ps.execute(); System.out.println(ps); // print query to console. } copy it from console and then execute in navicat in ur MAIN database. idk how explain 😄 if u not see anything in console then something wrong in ur java code.

like i said test ur query via navicat in main db. maybe different mysql version? it can occur syntax errors and etc..