Unable to Sync my Character - Bugs - General - Forums - EQ - Magelo

Login / Sign up

Forums > General > Bugs > Unable to Sync my Character

Messages in topic: Unable to Sync my Character

1

MysteryOfTime

Registered User

Nbr post: 1
Register: 3/29/18

Posted: 8/31/19, 7:27 PM

Hello, I am unable to since my Character...here is the log file. [18:23:49] [WARNING] Could not find: magelo-i18n [] [18:23:49] [INFO] Using magelo-i18n[en] [18:23:49] [INFO] Using magelo-i18n[en_US] [18:23:49] [INFO] Magelo Sync 4.6.1, Copyright (C) 2019 Magelo Limited [18:23:49] [INFO] Windows 10 10.0 amd64 [18:23:49] [INFO] Java version 1.8.0_191 [18:23:49] [INFO] America/Chicago, en_US, windows-1252 [18:23:49] [INFO] [18:23:49] [INFO] Services initialisation ... [18:23:50] [INFO] Automatic user authentification... [18:23:50] [INFO] Game Slots : 2 free of 3 [18:23:51] [INFO] User : MysteryOfTime (PREMIUM) [18:23:51] [INFO] Starting services... [18:23:51] [INFO] Starting service : Content Synchronizer [18:23:51] [INFO] Starting service : Deadlock Hunter [18:23:52] [INFO] Starting service : Game session seeker [18:23:53] [INFO] New game session detected : eqgame.exe[24804] [18:23:53] [INFO] Creating Everquest game monitor [18:23:53] [INFO] Starting game monitor : EverQuest 2.8.4 [18:23:54] [INFO] [Char] Step -2 [18:23:55] [SEVERE] null java.nio.BufferUnderflowException at java.nio.Buffer.nextGetIndex(Unknown Source) at java.nio.HeapByteBuffer.get(Unknown Source) at magelo.fC.g(fC.java:55) at magelo.eX.a(eX.java:4) at magelo.eX.a(eX.java:18) at magelo.QjF.Qa(QjF.java:27) at magelo.QjF.Qa(QjF.java:41) at magelo.QjF.Qa(QjF.java:34) at magelo.QjF.a(QjF.java:44) at magelo.eZ.b(eZ.java:14) at magelo.QjC.Qa(QjC.java:46) at magelo.QjC.Qa(QjC.java:27) at magelo.QjC.Qa(QjC.java:38) at magelo.Qes.Qa(Qes.java:780) at magelo.Qes.i(Qes.java:257) at magelo.g5.a(g5.java:10) at magelo.g5.run(g5.java:21) at java.lang.Thread.run(Unknown Source)

Jelan

Admin

Nbr post: 11385
Register: 5/4/01

Posted: 9/20/19, 12:33 AM

Hi, I just patched Magelo Sync, can you check if you still have the issue and post an updated log if so ? Thanks in advance !