vadi2
commented
7 years ago That is a side effect of the auditing and other code noticing things that I felt were important enough details that needed to be brought to the attention of the user whatever their preference to not normally see map related details. Unnamed and Duplicate area names have been issues that break things (the mapper area selection widget for one thing) for some time and we now actively prevent such things - since this means changing things in an existing map I do not think these are details that we should not draw the user's attention to them.
For any particular file this will happen when it is checked and "fixed" and should not show again if the file is saved and then reused. {Attempts to do things that would result in an unnamed (blank) or duplicate area names WILL fail with appropriate error messages.} The -1 area IS required and must be added to a map (file) without it - if the option to show it is enabled (it is by default) it will appear in the area selection widget and can be displayed - which may surprise a user - hence this must also (IMHO) be reported.
I note from the included text that the map file used is recorded as "/home/vadi/Dropbox/MMC/mapping/Sidd Map 1-25-15.dat" and presumable it is being repeatedly used and not saved - so then the messages noted WILL reoccur each time the file is loaded but this does not represent normal usage in my opinion.
I will tentatively mark this bug as "invalid" but the OP may of course review and revise that action.
Launchpad Details: #LPC Stephen Lyons - 2016-10-15 21:26:55 +0000
Even though the I have the 'report map issues to screen' checkbox turned off when selecting and loading in a map, 20+ lines related to map issues are still printed to the screen:
[ INFO ] - Reading map (format version:16) file: "/home/vadi/Dropbox/MMC/mapping/Sidd Map 1-25-15.dat", please wait... [ ALERT ] - Empty and duplicate area names detected in Map file! [ INFO ] - Due to some situations not being checked in the past, Mudlet had allowed the map to have more than one area with the same or no name. These make some things confusing and are now disallowed. To resolve these cases, an area without a name here (or created in the future) will automatically be assigned the name "Unnamed Area". Duplicated area names will cause all but the first encountered one to gain a "_###" style suffix where each "###" is an increasing number; you may wish to change these, perhaps by replacing them with a "(sub-area name)" but it is entirely up to you how you do this, other then you will not be able to set one area's name to that of another that exists at the time. If there were more than one area without a name then all but the first will also gain a suffix in this manner. [ OK ] - The changes made are: (ID) "old name" ==> "new name" (0) "" ==> "Unnamed Area"
[ INFO ] - Default (reset) area name (for rooms that have not been assigned to an
area) not found, adding "Default Area" against the reserved -1 id.
I think none of this should show, it should just go into the errors.txt unless you have that checkbox enabled (and the checkbox to fully do what it claims to say!).
Launchpad Details: #LP1632941 Vadim Peretokin - 2016-10-13 04:28:18 +0000