SOE<->SEQ converter

[Mapfiend]

I have written a SEQ<->SOE map converter script (it converts both ways) and have it on my site for the time being, though it will likely be moved to Fatal's site.

Some of the major features are:
1. Preserving colors most of the time (using white otherwise) when converting SOE->SEQ and all the time when converting SEQ->SOE
2. Rebuilding lines when converting SOE->SEQ wherever possible(like colored lines are grouped together up to 250 points)
3. Preserving point locations
4. Correctly flipping the signs on X and Y coords (though I'm still not sure if the Z should be /10 or not)

Disclaimer: I have not extensively tested this script, but it does work with the maps I tested, both SOE and SEQ.
Converting SOE->SEQ takes a *bit* longer than SEQ->SOE (due to the complexity of the SEQ format)

If you find any bugs or eccentric behavior with it, let me know here.

http://www.k-r-g.com/convert.php

[quackrabbit]

I am not sure if you know this or not, if you do then sorry for posting this info.

When you are converting a map from SOE to SEQ format and you can not find a color "name" in RGB.txt you can convert the RGB values to hex and use that value instead.

For example, if color values from the SOE format map are 120, 200, 100 you can use #78c864 as the color in the SEQ map - no need to drop the color detail and substitue white.

[quackrabbit]

Bleah, I can't edit my post... The hex values must follow the # symbol.

Also, your map converter does not correcly convert SEQ maps to SOE maps if the color is in this format.

[who_me_use_seq]

Thanks Mapfiend. That is very handy.

[Mapfiend]

quackrabbit,
I didn't know about the hex colors. I'll fix that tonight, thanks for the info.

[Mapfiend]

ok, I fixed the hex color feature. It will now use hex colors (#RRGGBB) if it can't find the color in RGB.txt for SEQ maps, and will correctly convert them back to decimal for the SOE maps.

[Mapfiend]

ok, found a rather large problem when converting original SOE maps to SEQ.
Not really sure if it is the user doing it or if it is the SOE mapper, but a MOST of the coordinate pairs don't "match up". I'm totally unfamiliar with how the cartography stuff works, so not sure what to blame it on
the result is that SEQ maps generated from SOE originated maps are almost as large as the SOE original.
I'm going to add a "fuzzy" feature to the SOE parser, so if the previous set of coords are within, say, 5 of the next set of coords, it will just continue the line.
This should cut down on redundant M,Line,Color entries and cut map size considerably.

[SeqTester]

Is there a size limit on this? I wanted to take the SOE-PoK map and turn it to a SEQ-Map but it keeps saying "failed to upload poknowledge.txt ".

I think it may be a timeout issue being my cable modem is capped on my send and the file is 500kish..

Thanks,
ST

[Mapfiend]

yeah, there is a filesize limit of 300k right now. I'll raise that when I get home from work. Or you can break the file in half and do it in 2 parts, Then merge them into an SEQ file.

[SeqTester]

Hmm.. why did I not think to split it up, thanks I will try that after dinner.

ty,
ST

[Mapfiend]

I upped the file size limit to 500k (Damn, SOE maps can be HUGE)
and fixed the line optimization. SEQ maps generated from SOE maps are now a LOT smaller.

Not sure if anyone has noticed this or not, but maps generated in game are written backwards. It appears that instead of each new coordinate set (line) being appended to the bottom of the file, it is placed on line 1 and all previous lines are pushed down one.
SOE maps that were previously converted from SEQ are NOT written this way, so I have taken that into account as well.

Let me know if you find any other bugs

[Amadeus]

Well..I found a new plane of Hate SOE map ..but it's 770k

Got a PM into mapfiend, maybe he'll have an answer for me

[Mapfiend]

Amadeus, check your PM

[HRPuffinstuff]

Hello,

I tried using the map converter on the new Chardok B map available from maps.eq-toolbox.com. Downloaded the txt file to my linux box, went to www.k-r-g.com/convert.php, browsed for my filename and hit "post", waited a few moments, got the result back, cut and pasted it into /usr/local/share/showeq/Chardokb.map. At first glance everything seemed normal. But . . .

When zoning into Chardok B, it appears that the map converter set the number of points in EVERY line to 0. "Ok" I think to myself, "this is about a 30 second script to fix this". It was, wrote a simple little awk (perl is the debbil I tell you! awk is the only true script interpreter! But I digress . . .) script to replace the 4th field with the actual number of line points. My simple little script worked fine and showeq know longer gave me 800 or so warning messages. But . . .

I get no lines on the map. Skittles show up, labels show up, but no lines whatsoever. Any idea what could be amiss with the map file? (I've seen this in other zones/maps also, notably Fear)

TIA,

HR

[KaL]

Check the color of each line. I think the converter gives you grey0 and you can just convert to gray or something.

Like, bring it up in vi and do a

:%s/grey0/gray/