Cant log in. Haven error

[Jamilian]

Just when I start the Client I get an error.

I cleared the Java-Cache and it didn't change anything.

Here again the error-report:

java.lang.ArrayIndexOutOfBoundsException: 6
at haven.Utils.uint16d(Utils.java:173)
at haven.Resource$Tileset.<init>(Resource.java:636)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at haven.Resource.load(Resource.java:993)
at haven.Resource.access$300(Resource.java:39)
at haven.Resource$Loader.handle(Resource.java:389)
at haven.Resource$Loader.run(Resource.java:368)
at java.lang.Thread.run(Unknown Source)

[Rift]

yea, the newest client has that error. im sure loftar is working hard to fix it as we speak.

[Zaffirus]

I hope it resolves soon

good job anyway

[Jamilian]

jep I see, now the error occurs after clicking the login button

[Jamilian]

Now its only a "Could not connect to server anymore" Client does not crash.

EDIT: works again whats new? ^^ okay, i know, we will see

[Zaffirus]

patience pls xD

[loftar]

I messed up a bit while doing some internal updates. Everyone might get exactly one more error, but after that, it should be resolved. Please tell me if it isn't.

(That last error is caused by some old data still living in the JNLP persistence cache, and should be cleared once it is detected)

[PhaedrothSP]

I just got this error

java.lang.RuntimeException: Weird version number on gfx/tiles/grass/grass (5 > 3), loaded from null
at haven.Resource.load(Resource.java:129)
at haven.Resource.load(Resource.java:159)
at haven.MCache.loadset(MCache.java:140)
at haven.MCache.tilemap(MCache.java:407)
at haven.Session$RWorker.handlerel(Session.java:366)
at haven.Session$RWorker.getrel(Session.java:375)
at haven.Session$RWorker.run(Session.java:443)

Edit: nevermind, it went away.

[AnonWat]

I messed up a bit while doing some internal updates. Everyone might get exactly one more error, but after that, it should be resolved. Please tell me if it isn't.

(That last error is caused by some old data still living in the JNLP persistence cache, and should be cleared once it is detected)

Nice going.
Aye but don't worry man. Everyone makes mistakes.
Thought I would mention this but, after the newest update I downloaded, it seems I've been having this issue as well.