Emulator_errors_stacktrace
Issue #1290
resolved
How can I resolve this error?
java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedConstructorAccessor28.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at com.eu.habbo.habbohotel.items.ItemManager.loadHabboItem(ItemManager.java:849)
at com.eu.habbo.habbohotel.users.inventory.ItemsComponent.loadItems(ItemsComponent.java:51)
at com.eu.habbo.habbohotel.users.inventory.ItemsComponent.<init>(ItemsComponent.java:34)
at com.eu.habbo.habbohotel.users.HabboInventory.<init>(HabboInventory.java:57)
at com.eu.habbo.habbohotel.users.Habbo.<init>(Habbo.java:52)
at com.eu.habbo.habbohotel.users.HabboManager.loadHabbo(HabboManager.java:132)
at com.eu.habbo.messages.incoming.handshake.SecureLoginEvent.handle(SecureLoginEvent.java:69)
at com.eu.habbo.messages.PacketManager.handlePacket(PacketManager.java:212)
at com.eu.habbo.threading.runnables.ChannelReadHandler.run(ChannelReadHandler.java:44)
at com.eu.habbo.threading.ThreadPooling$1.run(ThreadPooling.java:54)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(Unknown Source)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NumberFormatException: For input string: ""
at java.lang.NumberFormatException.forInputString(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.valueOf(Unknown Source)
at com.eu.habbo.habbohotel.items.interactions.InteractionMusicDisc.<init>(InteractionMusicDisc.java:26)
... 21 more
Comments (4)
-
reporter -
reporter HELP ME PLEASE
-
repo owner - changed status to resolved
Fixed in 1.16.0.
Caused by an disk furniture that has no valid song id set.
-
repo owner - removed version
Removing version: 1.14.0 (automated comment)
- Log in to comment
HELP