Tilelayers above 0 unreadable on gmap
 

Tile layers above 0 cannot be read or edited server-side on a gmap. I've seen a few other people run into this problem and there were no solutions for it, so I can only assume it is a bug. Here are 2 other threads where people had similar problems:

http://forums.graalonline.com/forums...hp?t=134262805
http://forums.graalonline.com/forums...ad.php?t=76235

I am able to read and edit on tilelayer[0], but once I go to tilelayer[1] or above it just returns the tile index as 0 no matter what. Tile layers work fine on non-gmap levels, so it seems to only be a problem on gmaps, and only serverside.

Are you sure that your x/y are correct?

You said it works fine on non-gmap levels. It worked fine only clientside? or serverside as well for non-gmap levels?

Remember that GMAP's have x/y values greater then 64/64.

The x/y values are correct, the script works perfectly fine as long as I don't change the tilelayers[0] to tilelayers[1]. The problem only occurs serverside at tilelayers of 1 or above on a gmap. All tilelayers can be edited in non-gmap levels in both serverside and clientside scripts. All tilelayers can be edited clientside on gmaps, but only tilelayers[0] can be edited serverside on a gmap. Stefan mentioned that he would look into the problem in the Windows v6 beta test thread http://forums.graalonline.com/forums...257598&page=88 so I am hoping he has not forgotten!

Was just curious because you say the bug is gmap only..

Have you tried something like player.level.tilelayers[] ? So that your not using the gmap?

Yeah, I tried everything I could think of short of using loadlines and savelines to just edit the level files directly, but no luck. The other threads I linked in the first post had similar problems, and no solution was ever posted. The script works perfectly fine for tilelayers[0] but not tilelayers[1], so I don't think there is any solution besides a bug fix.