Read-only archive of the Armageddon Games Forums Archive (2000–2026) · About this archive

DMap Titles Skipping Indenting Spaces [655]

7 replies · 1,603 views · Started 06 November 2007

In the DMap options in ZQuest, your map title may look like this:
"__Level_1_"
"__Eagle___"
_ means whitespace

In-game, the title will display above the map as this:
"Level_1___"
"Eagle_____"

Apparently, any whitespaces at the begginning of each line are skipped over. However, all other whitespaces within the title are placed normally. The text in-game should display identiacal to how it was "indented" in ZQuest.

Edit: Interesting update. I tested a 2.10 quest in 655, and the DMap titles are fine. It seems that the newer builds regester whitespaces differently in the DMap editor.

Still present in build 668.

In response to Dark Nation's bug list, the quest in my previous post shows the bug. This bug occurs in all quests made in recent builds. Quests from early builds or 2.10 do not have this bug present (apparently those builds/versions registered whitespaces differently).

Your alignment is set to left, not center. DMap titles strip out the initial spaces at the beginning of each line intentionally. I suppose I could set it to only do that if the alignment is set to center so the quest designer could do special alignments themselves. Thoughts?

Okay, I didn't realize the default template had it's DMap titles' alignment set to the left while the older quests defaulted to center, so I though it was a bug. The center alignment isn't bad though, so maybe a 'custom' alignment option instead?

Just one question. When I change the alignment of the title from left to center, the area the title displays in centers itself on it's X position and when I change to right alignment, the box is almost completley gone (only the right edge remains at the area's X position). To work with this, I need to shift the area's X position. Is this intended, or is this a bug?

Oh, and I've been on Windows for all these builds. I'll be sure to mention that in future bug posts.