help me! haven eror

[Zuugo]

I live in Kazakhstan but may speak through an interpreter. please help me everywhere error on all clients . java updated, fully removed, nothing helps

[loftar]

To start off with, it would help if you actually posted the error.

[Zuugo]

To start off with, it would help if you actually posted the error.

java.lang.ExceptionInInitializerError
at haven.UI.<init>(UI.java:112)
at haven.HavenPanel.newui(HavenPanel.java:262)
at haven.HavenPanel.<init>(HavenPanel.java:76)
at haven.HavenPanel.<init>(HavenPanel.java:84)
at haven.MainFrame.<init>(MainFrame.java:183)
at haven.MainFrame.main2(MainFrame.java:381)
at haven.MainFrame.access$100(MainFrame.java:35)
at haven.MainFrame$7.run(MainFrame.java:424)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.RuntimeException: Delayed error in resource gfx/hud/curs/arw (v1), from local res source
at haven.Resource$Pool$Queued.get(Resource.java:334)
at haven.Resource$Pool$Queued.get(Resource.java:303)
at haven.Loading.waitforint(Loading.java:87)
at haven.Loading.waitfor(Loading.java:99)
at haven.Resource$Pool.loadwait(Resource.java:593)
at haven.Resource$Pool.loadwait(Resource.java:597)
at haven.RootWidget.<clinit>(RootWidget.java:32)
... 9 more
Caused by: haven.Resource$LoadException: Wrong res version (4 != 1)
at haven.Resource.load(Resource.java:1573)
at haven.Resource.access$600(Resource.java:39)
at haven.Resource$Pool.handle(Resource.java:379)
at haven.Resource$Pool.access$1100(Resource.java:280)
at haven.Resource$Pool$Loader.run(Resource.java:515)
... 1 more

[Zuugo]

To start off with, it would help if you actually posted the error.

http://prntscr.com/99cgq8

[loftar]

In your home directory, there should be a directory called ".haven" (please note the dot at the beginning of the name). Does it help if you remove this directory?

[Zuugo]

In your home directory, there should be a directory called ".haven" (please note the dot at the beginning of the name). Does it help if you remove this directory?

YES!!! THX VERY MUCH!!!

[loftar]

Interesting. For the record, the problem was caused by something loading the wrong version of a resource, which then got cached, but I don't understand how that wrong version could have been loaded to begin with, since there's no loading of that resource that specifies a version number at all. Arguably though, it is a problem that such errors can become cached.