Will post update on the feature requests later today. Thank you all for the feedback.
g1real wrote:So what's the difference between cancel, delete and ignore anyway for duplicate tiles? What option should I do with overlapping good minimaps.
Cancel - makes no action with the duplicate tiles.
Delete - deletes the duplicated tiles both from archive and/or current session where they have been detected. (moves to the Deleted folder actually)
Ignore - add tiles to the ignore list. This options should be used to add correct tiles that can occur on the map multiple times (like water/snow/grass tiles) to the ignore list in order to avoid them to be considered as a merge anchor for some sessions that contain them.
The entire option with displaying a duplicated tile has been made for you be able to figure out if you really have a duplicated tile or you have faced multiple sessions, saved in to a single folder.
g1real wrote:2: Okay, it does it every time now, this is 3.1.7 btw, I'm going back to 3.1.5 for now.
I will check it out but there must be read-write access to the entire map archive folder.
camobeast wrote: I'm looking at the map tiles now and instead of the start tile being given the co-ordinates 0,0,0 they vary between each save
Session tiles' coordinates do not matter. All tiles are initially compared with entire map archive by tile size so if the client saves the same location tiles in a different file size (size in bytes), automerge will not be able to detect likeness between such sessions. You can check it easily by logging in and out twice, and compare the last two sessions after such procedure.