vinoveritas Report post Posted June 15, 2018 (edited) You can vanish underground at those 2 coords [20:40:55] You are in Desert Pines - Kamara Desert [172,40] [20:41:14] You are in Desert Pines - Kamara Desert [156,18] Can be closed, Error resided on my side. Edited June 16, 2018 by vinoveritas Share this post Link to post Share on other sites
SlothCommander Report post Posted June 15, 2018 I just downloaded and installed the latest client. I went to the two coords but I did not go underground. Share this post Link to post Share on other sites
saxum Report post Posted June 15, 2018 Could be it varies on maps. Have not installed all of Burn's and have fallen into holes many times. Was attacked by a pink in a hole and lost a rosto and not going on invasions for a while. Share this post Link to post Share on other sites
revi Report post Posted June 16, 2018 (edited) Tab maps, Burn's or others, have nothing to do with "falling in holes". Those "holes" appear when there's a difference between server .elm maps and client .elm maps; an error in a map file might also be the cause. For what it's worth, I checked both coordinate sets, and didn't find anything wrong. While you are in DP, try the "#ckdata" command; fo me it gives #ckdata d3f8f391cc82d0dfeab745a482040b7b ./maps/map3.elm Edited June 16, 2018 by revi added #ckdata output Share this post Link to post Share on other sites
vinoveritas Report post Posted June 16, 2018 (edited) i did fall in it when walking to the coords walking along the rocks. well i get a different checksum so i check where my error is. EDIT I am using eldata file from ubuntu linux distribution that blueapp made Edited June 16, 2018 by vinoveritas Share this post Link to post Share on other sites
vinoveritas Report post Posted June 16, 2018 ok found error on my side and fixed it Share this post Link to post Share on other sites
bluap Report post Posted June 16, 2018 I assume the data from the Ubuntu packages was OK vinoveritas. It all looks fine to me. Share this post Link to post Share on other sites
Burn Report post Posted June 16, 2018 (edited) FTR: "Holes" as well as start-stop or breakage of mapwalking are caused SOLELY by not having the same map in your client as the server has. That they exist is in itself the proof that your client is using 1.9.4 data for some reason on the 1.9.5 server. A hole: the server has that particular tile as walkable, but since your old map doesn't - you can walk on it because the server permits you, but your old map has no information on what height you should be at because it has it as unwalkable. "unwalkable" in map terms is actually a height positioning lower than the lowest you can be in the game, so you end up "in a hole". Stops during mapwalking are due to the exact opposite, the client has walkable tiles that the server doesn't, so you stop when you get to those tiles. The solution in both cases is to get your client working with current data. Edited June 16, 2018 by Burn Share this post Link to post Share on other sites
vinoveritas Report post Posted June 17, 2018 (edited) it was my error. I had accidently copied the burn mappack into updates/1_9_4/maps folder, and then just copied the folder to the updates/1_9_5 not realizing there where 2 elm files in the folder from bugfixes made inside the 1_9_4 relase. I deleted those 2 files and all where ok again Edited June 17, 2018 by vinoveritas Share this post Link to post Share on other sites