...

[mvgulik]

...

[loftar]

Code: Select all

Caused by: haven.Resource$ResourceClassNotFoundException: Could not find class haven.Rendered in resource lib/motley(v7)

That's weird. It seems like it's using resources from the old client. I can't think of any obvious reason why it would do that. I've made some changes to the client to allow it to report the more exact conditions of the resource used, so if you could please try and trigger the error again, that would probably be helpful.

[mvgulik]

...

[loftar]

As in, it should detect and update those ?

No, the new resources come from a completely different source, so it shouldn't ever even see the resources for the old client.

[Forik]

Code: Select all

java.lang.NoClassDefFoundError: haven/Rendered
   at java.lang.Class.getDeclaredConstructors0(Native Method)
   at java.lang.Class.privateGetDeclaredConstructors(Class.java:2671)
   at java.lang.Class.getConstructor0(Class.java:3075)
   at java.lang.Class.getConstructor(Class.java:1825)
   at haven.Utils.construct(Utils.java:1404)
   at haven.Sprite$FactMaker.make(Sprite.java:66)
   at haven.Sprite$FactMaker.make(Sprite.java:63)
   at haven.Resource$CodeEntry.lambda$get$0(Resource.java:1312)
   at java.security.AccessController.doPrivileged(Native Method)
   at haven.Resource$CodeEntry.get(Resource.java:1310)
   at haven.Resource.getcode(Resource.java:1149)
   at haven.Sprite.create(Sprite.java:127)
   at haven.ResDrawable.<init>(ResDrawable.java:42)
   at haven.OCache.cres(OCache.java:233)
   at haven.OCache.lambda$cres$4(OCache.java:245)
   at haven.OCache$GobInfo.apply(OCache.java:720)
   at haven.Loader.lambda$defer$0(Loader.java:235)
   at haven.Loader$Future.run(Loader.java:71)
   at haven.Loader$Future.access$400(Loader.java:42)
   at haven.Loader.loop(Loader.java:197)
   at java.lang.Thread.run(Thread.java:748)
Caused by: haven.Resource$ResourceClassNotFoundException: Could not find class haven.Rendered in resource gfx/terobjs/vflag(v63)
   at haven.Resource$CodeEntry$1$1.findClass(Resource.java:1239)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
   at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
   ... 21 more

I got one of these today too, and it works just fine on an outdated amber client.

[loftar]

I got one of these today too, and it works just fine on an outdated amber client.

Under what circumstances did this happen to you? Was it the default client just as downloaded from the website? Part of the reason why I'm wondering is that I don't seem to have received an error report from your client.

[Forik]

I got one of these today too, and it works just fine on an outdated amber client.

Under what circumstances did this happen to you? Was it the default client just as downloaded from the website? Part of the reason why I'm wondering is that I don't seem to have received an error report from your client.

Yeah, a freshly downloaded website client, think my java didn't report for some reason the first time, just did it again, and it looks like the report was successful. Happens as I walk out of my front gate, the game itself doesn't actually crash (I can see my character move and all), but I can't control it anymore, and a java error prompt shows up with the error (if that helps).

[loftar]

Yeah, a freshly downloaded website client, think my java didn't report for some reason the first time, just did it again, and it looks like the report was successful. Happens as I walk out of my front gate, the game itself doesn't actually crash (I can see my character move and all), but I can't control it anymore, and a java error prompt shows up with the error (if that helps).

I can see from your error report that you have a bad version of the resource cached. The real question is how it made it into your cache to begin with. If only for the sake of science, could you try clearing your cache to see whether that fixes the problem? (If you do, remember to export your map first.)

[Forik]

I can see from your error report that you have a bad version of the resource cached. The real question is how it made it into your cache to begin with. If only for the sake of science, could you try clearing your cache to see whether that fixes the problem? (If you do, remember to export your map first.)

Yep, that fixed the issue, maybe it's gotta do with the fact that I'd mostly been playing with amber up to when the clients broke a few weeks ago.

[loftar]

Yep, that fixed the issue, maybe it's gotta do with the fact that I'd mostly been playing with amber up to when the clients broke a few weeks ago.

How annoying, tbh. I was hoping that it would crash again and reveal the reason why it got that resource into the cache to begin with. I don't think any custom client should be using the same cache ID.