Overseer level names collide -- User can add too many maps

[rdebath]

With the removal of the + from the end it's easy for an account to be created that blocks someone else creating their additional maps. ie:

• UserID creates map UserID
• UserID2 creates create their map UserID2
• UserID cannot create map UserID2

Old style:

• UserID+ creates map UserID+
• UserID2+ creates their map UserID2+
• UserID+ creates map UserID+2

[UnknownShadow200]

/os map add should be automatically skipping over maps that don't belong to the user

[rdebath]

Okaaay, yes, that's not confusing at all. Create seems to skip other owned maps correctly; /os go <N> doesn't though.

I still think adding a string between the user and the number is a good idea, defined in the properties of course. At this point it might be a good idea to add all three of a prefix, suffix and the infix strings. That way it can be made easy to distinguish the OS levels from the generic ones.

PS: Sorry, I should have tested what it would do, it wouldn't have stopped me raising an issue tho.

[Goodlyay]

How then does it count how many OS maps a player has made? Does it also skip in that case?

[rdebath]

Oh, dear, you're right @Goodlyay it counts them wrong, this sequence works ...

• builder2 creates map builder2
• builder creates map builder
• builder creates map builder3
• builder creates map builder4
• builder2 deletes map builder2
• builder creates map builder2

Builder has 4 maps when they're supposed to have 3.

• builder deletes map builder4
• builder cannot create map builder4