Macro store failed

[ShinichiYao]

WARNING: could not store macro:
com.mysql.jdbc.MysqlDataTruncation: Data truncation: Data too long for column 'acronym' at row 1
    at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3868)
    at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3806)
    at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2470)
    at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2617)
    at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2550)
    at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1861)
    at com.mysql.jdbc.PreparedStatement.execute(PreparedStatement.java:1192)
    at com.zaxxer.hikari.proxy.PreparedStatementProxy.execute(PreparedStatementProxy.java:44)
    at com.zaxxer.hikari.proxy.HikariPreparedStatementProxy.execute(HikariPreparedStatementProxy.java)
    at com.l2jserver.gameserver.model.MacroList.registerMacroInDb(MacroList.java:160)
    at com.l2jserver.gameserver.model.MacroList.registerMacro(MacroList.java:87)
    at com.l2jserver.gameserver.model.actor.instance.L2PcInstance.registerMacro(L2PcInstance.java:1631)
    at com.l2jserver.gameserver.network.clientpackets.RequestMakeMacro.runImpl(RequestMakeMacro.java:105)
    at com.l2jserver.gameserver.network.clientpackets.L2GameClientPacket.run(L2GameClientPacket.java:69)
    at com.l2jserver.gameserver.network.L2GameClient.run(L2GameClient.java:1135)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
    at java.lang.Thread.run(Unknown Source)

[George Spatacean]

Hello,

I'm not able to replicate this using develop branches. Macros are saved successfully in database. In database, "character_macroses.acronym" is varchar(4), which is the max length allowed by the L2 client for the acronym of a macro.

Are you still able to replicate this? If so, can you confirm "character_macroses.acronym" type is also varchar(4)? also, can you please specify which branches(or even latest commit hash) are you replicating?

Thanks, George S.

[ShinichiYao]

Yes its varchar(4) in DB, Maybe Chinese Client allows longer length of acronym.

[Zoey76]

Seems it's a problem with the client.