"Weird version number on gfx/tiles/grass/grass"

The worst monsters in the Hearthlands warp the fabric of space and time..
User avatar
nejj
Posts: 49
Joined: Tue Aug 25, 2009 6:08 am

"Weird version number on gfx/tiles/grass/grass"

Post by nejj »

When I try to run H&H I get the following error and the window automatically closes itself:

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)
User avatar
nejj
Posts: 49
Joined: Tue Aug 25, 2009 6:08 am

Re: "Weird version number on gfx/tiles/grass/grass"

Post by nejj »

It's working now, but I thought I'd leave this post up just in case it helps.

I don't know if this is why its working, but I checked the "always trust content from this host" box and it worked after that.

(edit: sorry for the double post)
Last edited by nejj on Fri Aug 28, 2009 3:04 am, edited 1 time in total.
User avatar
theTrav
Posts: 3464
Joined: Fri May 29, 2009 11:25 pm

Re: "Weird version number on gfx/tiles/grass/grass"

Post by theTrav »

It means you've got an older version of the grass tile cached from what's on the server (or something like that)

delete your temporary internet files, restart your computer, touch your toes, spin around then do 4 star jumps and it should be fine.

you don't need to keep touching your toes while you spin btw, just once is enough
User avatar
nejj
Posts: 49
Joined: Tue Aug 25, 2009 6:08 am

Re: "Weird version number on gfx/tiles/grass/grass"

Post by nejj »

Ah, okay.

Thank you for the fast response!
User avatar
loftar
Posts: 9096
Joined: Fri Apr 03, 2009 7:05 am
Location: Your character database

Re: "Weird version number on gfx/tiles/grass/grass"

Post by loftar »

Actually, it's because I messed up the other day while changing the resource file format and had to replace some resources (the grass being among them) with older versions, so your client had cached a newer version than the server requested. That kind of error should only occur once, though, because after it has occurred, the client discards its "used resources" list and doesn't try to preload resources from the JNLP cache.
"Object-oriented design is the roman numerals of computing." -- Rob Pike

Return to “Bugs”