# Expanding the dimentions of a tileset for an existing map without it breaking horribly?

**URL:** <https://discourse.mapeditor.org/t/expanding-the-dimentions-of-a-tileset-for-an-existing-map-without-it-breaking-horribly/1505>\
**Category:** Questions\
**Created:** [July 2, 2016, 8:55am UTC](https://discourse.mapeditor.org/t/expanding-the-dimentions-of-a-tileset-for-an-existing-map-without-it-breaking-horribly/1505 "2016-07-02T08:55:41Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lactamid](https://avatars.discourse-cdn.com/v4/letter/l/e480ec/32.png) [@Lactamid](https://discourse.mapeditor.org/u/Lactamid)\
**Post date:** [July 2, 2016, 8:55am UTC](https://discourse.mapeditor.org/t/expanding-the-dimentions-of-a-tileset-for-an-existing-map-without-it-breaking-horribly/1505/1 "2016-07-02T08:55:41Z")

</div>

Ran into an issue a few days ago that I’ve been unable to resolve.  
When I went about building a map I felt that I was missing pieces and wanted to create a bunch of new tiles.  
So I jumped into making a couple new ones and saved them in my tileset image.

Tiled then opened a pop up saying something about the tileset changing from 47 lines to 53 (or the like) would you like to change it? Y/N.

I clicked yes, but then the whole map went from done into chaos.

I did expect a few changes as a few of the tiles had actually been moved on the tileset image, but 95% of it should have been ok. It was not.

(Sadly I had only saved an earlier version of the tileset image before the changes and overwritten the tileset image before the expansion of tiles so I could really go back).

Is this something that happens to others or did I just screw up somewhere because it’s supposed to work?  
Happy to learn how I’m supposed to do (because I would like to expand again now hehe 😃 ).

---

<div class="post-metadata">

**Author:** ![bjorn](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.mapeditor.org/bjorn/32/1599_2.png) [@bjorn](https://discourse.mapeditor.org/u/bjorn)\
**Post date:** [July 2, 2016, 2:53pm UTC](https://discourse.mapeditor.org/t/expanding-the-dimentions-of-a-tileset-for-an-existing-map-without-it-breaking-horribly/1505/2 "2016-07-02T14:53:24Z")

</div>

Well, Tiled is of course meant to fix up your map, not make it into chaos. Although it worked for me when I implemented it, you’re not the only one running into problems. According to the following bug, it may be related to some tiles being empty:

> <https://github.com/bjorn/tiled/issues/1242>
>
> Hi,
> I just tried to resize a tileset used in one my maps and it appear that Tiled detect the column change...

I’ve marked this bug as urgent now and will test and hopefully be able to fix this soon.

---

<div class="post-metadata">

**Author:** ![bjorn](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.mapeditor.org/bjorn/32/1599_2.png) [@bjorn](https://discourse.mapeditor.org/u/bjorn)\
**Post date:** [July 20, 2016, 8:55pm UTC](https://discourse.mapeditor.org/t/expanding-the-dimentions-of-a-tileset-for-an-existing-map-without-it-breaking-horribly/1505/3 "2016-07-20T20:55:25Z")

</div>

Just a heads up that this bug was fixed in [Tiled 0.16.2](http://discourse.mapeditor.org/t/tiled-0-16-2-released/1519).

But, those using the terrain tool should be aware that there is a related issue with the terrain information getting messed up, which isn’t fixed yet. If this affects you be sure to follow this issue:

[https://github.com/bjorn/tiled/issues/1315](https://github.com/bjorn/tiled/issues/1315)

---

<div class="post-metadata">

**Author:** ![Lactamid](https://avatars.discourse-cdn.com/v4/letter/l/e480ec/32.png) [@Lactamid](https://discourse.mapeditor.org/u/Lactamid)\
**Post date:** [August 17, 2016, 4:11pm UTC](https://discourse.mapeditor.org/t/expanding-the-dimentions-of-a-tileset-for-an-existing-map-without-it-breaking-horribly/1505/4 "2016-08-17T16:11:17Z")

</div>

Noticed another little issue with the tileset image changing.  
I think if your map isn’t previously saved the current check doesn’t work.  
I’m not sure this is what caused it, but I got the same issue as in the old version today when editing the tileset image on the fly while building a map.

---

<div class="post-metadata">

**Author:** ![bjorn](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.mapeditor.org/bjorn/32/1599_2.png) [@bjorn](https://discourse.mapeditor.org/u/bjorn)\
**Post date:** [August 19, 2016, 8:22am UTC](https://discourse.mapeditor.org/t/expanding-the-dimentions-of-a-tileset-for-an-existing-map-without-it-breaking-horribly/1505/5 "2016-08-19T08:22:36Z")

</div>

> [@Lactamid](#):
>
> Noticed another little issue with the tileset image changing. I think if your map isn’t previously saved the current check doesn’t work.

Actually, it seems like it doesn’t work for newly added tilesets, regardless of whether the map is new or not. 😕 Thanks for noticing this issue, I’ll look into it.

---

<div class="post-metadata">

**Author:** ![bjorn](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.mapeditor.org/bjorn/32/1599_2.png) [@bjorn](https://discourse.mapeditor.org/u/bjorn)\
**Post date:** [September 6, 2016, 12:58pm UTC](https://discourse.mapeditor.org/t/expanding-the-dimentions-of-a-tileset-for-an-existing-map-without-it-breaking-horribly/1505/6 "2016-09-06T12:58:24Z")

</div>

Fixed that last issue with the following commit:

> <https://github.com/bjorn/tiled/commit/cde5319d52d582ce516dccfaa6c50d472d419373>