Bug Bug Thread: Discussion - Page 2

Endoperez · #11 October 3rd, 2006, 03:56 PM

Quote:

Arralen said:

Quote:

Endoperez said:
[img]/threads/images/Graemlins/Bug.gif[/img] Adding descriptions to mods doesn't work properly. New lines entered in all text editors (tested on Notepad and Wordpad) don't start new paragraph; they seem to act as spaces. Also, the last #description command in the mod is used as the mod's description, even if the said command is actually a monster's description. This forces the modder to put the description of the mod to the very end of the mod.

Can't 2nd this. Use Unix-type linefeeds/newlines, that may help.

You need 2 newlines (an completly empty line) to get paragraphs in the description window. 'was this way in Dom2 as well.

If the #description does not work properly, you might have left out a " somewhere...

I didn't notice any missing quote marks in the Anansi mod I posted to the mod forum. All three descriptions started and ended properly, or at least I didn't notice anything out of order.
Regarding newlines: it just doesn't work for me. Didn't work in DomII either. It could well be problem with Notepad and Wordpad and the way they handle newlines.

Arralen · #12 October 3rd, 2006, 04:23 PM

Quote:

Endoperez said:
I didn't notice any missing quote marks in the Anansi mod I posted to the mod forum. All three descriptions started and ended properly, or at least I didn't notice anything out of order.
Regarding newlines: it just doesn't work for me. Didn't work in DomII either. It could well be problem with Notepad and Wordpad and the way they handle newlines.

#desciption: will have a look

# newlines: yeap. I'll pm you a link to an editor which does A) Unix-linefeeds and B) (incomplete) syntax-highlightning for Dominions.

Endoperez · #13 October 3rd, 2006, 04:30 PM

Quote:

Arralen said:#desciption: will have a look

# newlines: yeap. I'll pm you a link to an editor which does A) Unix-linefeeds and B) (incomplete) syntax-highlightning for Dominions.

Wow!

Any way, I still count it as a bug, because this is supposed to be multi-platform game. You know, not everyone has a fancy Linux or Mac! There are many Windows guys and gals even on the Shrapnel forums!

Neophyte · #14 October 3rd, 2006, 07:21 PM

I'd appreciate that link too, please. And is Unix style (Suse 9.x and 10.x if it matters) CR & LF, CR or LF? OpenOffice 2.x gives this as an option when you save a file as Text Encoded (.txt) and check the "Edit filter settings" box before clicking on Save. Answer appropriately when it asks if you're sure you want to save as txt and not native OpenOffice.

Thank's, and good luck - mine shipped today!

Arralen · #15 October 3rd, 2006, 08:26 PM

LINUX = "\n" *nix uses the LF character
WIN32 = "\r\n" Windows uses both -- with the CR coming before the LF
MAC = "\r" Macs use the CR character
MAC_LEGACY = "\n\r"

Ballbarian · #16 October 3rd, 2006, 08:39 PM

I too had problems in Dom2 as a windows user using notepad. Solution for me was to use Vim.

Bluebird · #17 October 4th, 2006, 04:50 AM

A windows user switching from notepad to vim? You must be kidding.

Ballbarian · #18 October 4th, 2006, 08:58 AM

I still use notepad when I can, but I love the power of Vim. Just a matter of choosing the right tool for the right job.

DominionsFan · #19 October 4th, 2006, 09:03 AM

Quote:

Ballbarian said:
I too had problems in Dom2 as a windows user using notepad. Solution for me was to use Vim.

So using Vim as a text editor should work properly to edit the mod files for Doms 3.?

Ballbarian · #20 October 4th, 2006, 09:15 AM

Yes. I have used it for editing various dom2 mod files and all of my map files. The one Dom3 map file that I got my paws on was Vim friendly as well.