UniMapGen v2.62

[Perun]

Few additions/changes:

- variable-colored pins for domains
- highlight no longer obscures colorboxes (description tree and domain stats)
- domain map now automatically resizes cells to optimally fill the grid box (domain stats)
- saving of project files is now possible regardless of creation method
- domain color boxes in description tree are slightly bigger (16x16, like terrain boxes)
- terrain boxes in description tree are now framed
- all trees now have proper toolwindows for text that doesn't fit into column width (sorry for overlooking this earlier )
- actual view now displays current location's description and domain (second brackets) and description of location ahead

More to come soon! And as always, please comment!

Cheers!

Oh yes, get it here: Lair of the Dragonlord

[Natmus]

Everything seems to work very well, Igor

As for suggestions for further development, I would first like to hear from Jean-Yves about his requirements.

One minor thing I just realised I would like is an "Undo" option, when you paint something in error, and have to choose another feature to re-paint the same cell. Just having a simple undo button wold be nice, but I realise that would you to keep a record of actions, and a record of what were in that cell before. But if you could ...?

[Matija]

Another suggestion: multiselct by clicking on the map.

[merlin]

Igor,

As you appear to be on a roll... are you interested/ready to get your editors up a running with the latest TME? I would like to see your scenario editor working with a Live TME, and it would help me to tweak the areas of the engine that are still outside of editing...

If you are then I have lots of requirements and will be happy to give you continuous feedback... also I will make a version of the latest TME available so that others can play around with it as well?

What do you think?

[sparrowhawk]

Well I have to say that it's really great :-)

You asked for some feedback on specifics of what would make my life easier, and how this could help with others adding their own scenarios. Here goes:

• I may have missed the option, but if not it would be great to be able to assign descriptions to the domains (so that you could then export your domain list as part of the SQL export - I can supply the SQL)
  
• On the SQL export wizard, could the MU-specific page include a check box to export the mu text file too, so that you don't have to export twice? Very minor point but it would add to the already high level of polish
  
• More significantly, below is the LoM scenario map file. Could UMG add an option to create the array element automatically. If not, then at least to add double quotes around each line and a comma at the end of each line (except the last?)
  
• If you're going to export to MU, I would check all the MU options by default, as they are all needed (except trimming FW)
  
• More once I've played around with it further. But so far so excellent :-)
  

Here's the map file for LOM (the html is not displaying consecutive spaces correctly as they are not hard spaces, but you get the idea I hope:


<?php
 //Midnight Map Data - Lords of Midnight

 $map = array(
 // 01        10        20        30        40        50        60   65
 // ¦¦        ¦         ¦         ¦         ¦         ¦         ¦    ¦<br>    "ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ", //0
   "ZZZR S MMC           S   ZZL   H       ZZL  R S   Z S   S  ZZZ T Z", //1
   "ZZ   DMMMMM   S FF      ZZZZDD     S    S   DDDEDD   H     NZZE SZ",
   "Z   DMMMMMMM   FFFF  L ZZMMMMMDDD         DDDDDDDDDDN  L DD ZZS ZZ",
   "Z FDDNMMMMMFFF FFFFH  NMMMMMMMRMM   E S  DDDDDDKDDDDDD       Z ZZZ",
   "Z FFEC MMMMFFF  FF  DDMMMNFTFKMMMMR        DSDDDDDNDDD  D S  LZZZZ",
   "Z  FFF  MFFFFF   L  MM CFFFFF  VMMMMMMM   L DDDDDDDDDDD        ZZZ",
   "Z  FFFF  FFFFFF     RMMDDR       KMMMMMMM    NDDDDDDR   L   D   ZZ",
   "Z S FFF  FFFFFFFF    LMMKDD V C       C MMRF     DD     MMM N TE Z",
   "Z    S  FFFFHMFFFF    EMMMMFL  MMMMMMMMDDK   SFE E H  NMMMKMMMM  Z",
   "Z  LLLLLFFFNVT VFF     MMMMMMD MMMMMMTMMK L  FFF     S  MMMMEMME Z", //10
   "Z H     NFFDKELRFF R    FMMMMM MMMMEMMMMMR  FFFFF L L  FNMMEMME  Z",
   "Z  LLLLL FFFDD FFF    K   KMMM MMMDDDDDMMDDNFFTFFFF  F S MMMM S  Z",
   "Z    DD FFFFFFFFF     MM  DDMMCMM   DKDDDDFFFFFFKFFFK   DMMM   K Z",
   "Z   DDDDDFFFFFF  K  MMMDDD DD      L   L FFFEFFFFFFF   DKE  D    Z",
   "Z   DDDLDDR    S   MMMDDR          FFFFFFFFFFFFF VFF  DD   D VV  Z",
   "Z  DRDDDDD N L    MMMF             FFFRFFFFFFLFFR    F  L C     NZ",
   "Z  DDDNDDDD    K MVM  L   E K      KFFFFVFFCFFFFF R  KV    VRFFS Z",
   "ZS DDDDDVDE     MMMMK               FFFFFFFFFFNFFV    VV E  FFFF Z",
   "Z  DDDDDDDDD     MMMD  K  FF      L FFFFFMMFFFFFFF ELL KRFFFLFFFFZ",
   "Z MMDD RDD   FF  EMMD  FFFFFF L  L L   FFFFFFVEFFF    MMMMFFF FFFZ", //20
   "Z MMMD       MMK    DDFFFFEFFF    L LDRFFFFF  E   K MMMMMFKFFVFFFZ",
   "Z RMMM  L  MMMMMM  C DFFVFFFFF     L LD FFFK H  R MMMMMMFFFFFF FFZ",
   "Z  MMM    MMMMMMMM   FFFFFFFF   KV DL D  DDDDDDKMMMMMM HFFFTFFLFFZ",
   "Z  HMM    MMMRVMMMM E FFFFFF       D L  K   VMMMMMMM E   FFFFFF VZ",
   "Z  MMF  E MMMTEMMM    MMMMMMM     DN L    LMMMMMM RF   V KFFFV R Z",
   "Z FMME  M  MMMMMM   VMMMMMMMMMM  KMM RR  EMMMMM     V L V     N  Z",
   "ZKMMM  FMM  MMMMFLDMMMMMMMMMMMMMMMMM    MMMMM KMMMMMM  K R  L  RFZ",
   "Z MMM  MTMM FMMMMD MMMMFRVDMMMMMMMMK  TMMMMM V EMMMMMMMMMMMV DDFFZ",
   "Z  MM  MMMM FMMMR K   LDD  EDMMM     MMMMMMK T    VMMMMMMMMV RDDFZ",
   "Z SFF  MMMM FMMM   MM D  C     K   MMMMMMR  DMMFFD  K     C     LZ", //30
   "Z   C  MNMM  MMMELMMMMMR  RMMMMMMMMMMMMM  V MMMMMMMMMMMMM    TT  Z",
   "Z   M  MMMM  MMMMMMTMMM   MMMMMMMMMMMMMN EDDRMMMMMMMMMMMK  R   LEZ",
   "Z   MM MMMM   MMMMMMMMK KMMMMMMMMMMMMR     DC      V        FV E Z",
   "Z  SMM MMMMM  KMMMMM     MM        K    F   L   V L  N  V L    F Z",
   "Z  MMM  MM R    R           H  K    LR    L  DD H           K    Z",
   "Z  MMMM M         L               FFF   V E  VDDDDD V  E       V Z",
   "Z KMMMM    FFFF MM    K         FFFFFFFFFF R DDDDDDLDDR   V      Z",
   "Z   MM L  FFFFFFF          E   FFFFFFFFFFF   DDNDVDDDDDDD        Z",
   "ZZ  DD   FFFFFFFFF            VFFFVEFFFF     DDDDDFDEDDKDDD   RFFZ",
   "ZZ E DD FFFFFDFFFF  R       K FFFFDFNFF  F F   DLDDDDDVDDD LFFFFFZ", //40
   "ZZ   DDDRFFFDT  F      K  K   FFFFFFFFR V        KDDDDDDD  FFFFFFZ",
   "Z   MM D FFF DDFFF L VDDD     RFFFFFVF   H K NV     DRDDKFFFFFFFFZ",
   "Z  MMMN   FFFFFFF K DDDDDDDR C   FFFF     L   D D V  DD FFFFFFFFFZ",
   "Z  MMMM    FFFFFN DDFDDEDVDDDF V  L   K  E D D L R      FFFFCFNFFZ",
   "Z  MMMMM D  FFF  DDDDDDDDDDDDDL        D  V        VD FFFFFFFDFFFZ",
   "Z R MMMMM DD        DDDDDDDVDD EV  V    R   MCME D    FFFFFFFLFFFZ",
   "Z  S MMMMMM  R L  MML  VDDDDD KMM    L   M K MMMMMD  L VFFFFFEFFFZ",
   "Z     MMKMMK     HMM     DDD  MMM R   VEMM M RM ME     FFFFFFFTFFZ",
   "Z    EMMMMMM   L  MMF     L  MMMFDD VEMMMM MM MR K  E FFFFFFFFVFFZ",
   "Z   RMMMMMMMM    RMMFFK VD FMMMF   NMMMTMM MM K MML DVFFF  FFFF FZ", //50
   "Z N MMMMMMMMME L MMMNDDDD FMMMD   MMMMMMMR MMM MEMM  R K  V FFF FZ",
   "Z  MMMMFFFMMMM   MMMDDV   FMMD V MMMMMFFKD KMM MMMMKVLDD L FFFHFFZ",
   "Z  MMM  V EMMM L MMVD    VMMMD  MMMME REV MMMM KMMMMMMT  DDFF FFFZ",
   "Z  MMMV E  MMM   MMDD    MMMD       LD MMMMMMM MMVMMM MMMM  L  FFZ",
   "ZD MMM TD VMMK L MMD   FMMKD V     MMMMMMMM MK MMMEMMM MKMMMM VN Z",
   "ZD MMMV K  C     MM    MMMD    FFMMMMMMMMMMMMM MRMMMM MMMMMMM  R Z",
   "ZD MMMF V MMM   MMK   KMMMDE  FFCMMMMMKV F MMM MMMDDEMMMMMHMMML  Z",
   "ZD EMMMEFKMMMK  MM   FMMML  RFFFMMMNDDD LV FMM MM R  FVE MMMMM  FZ",
   "Z L MMMMMMMM    M V  FMMM     FFMMFV VDDK  DD   EV  LD VLKMMMD FKZ",
   "Z    MMMMMMM   MM    MMME  FFF FMM DH V RDDK  C  D DF R  E D L   Z", //60
   "ZZE  K    R    KR   RRMMK FFFFF   K  T E  LD V  F    V D D  KM V Z",
   "ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ"  //62
 // ¦¦        ¦         ¦         ¦         ¦         ¦         ¦    ¦<br>  // 01        10        20        30        40        50        60   65
   );

?>



The // comments are not essential, although they are useful!

[sparrowhawk]

One other thing - the MU world lives in database tables mostly, so as an old fashioned database boy, I always refer to coordinates as Row-Column (Y,X). Would it be possible to have an option to view coordinates in that order, rather than the more traditional X,Y format?

[Perun]

OK, here are replies to all messages, chronologically:

Natmus said:

One minor thing I just realised I would like is an "Undo" option... snip...

Good idea. It will probably be somewhat difficult to implement in full, but I'll certainly give it a try.

Matija said:

Another suggestion: multiselct by clicking on the map.

I've been thinking about adding also. Some logic have to be changed, though, if implemented. Will see about it, as it helps a lot.

Merlin said:

...snip...What do you think?

Of course. I had started the mesced project to support tme, but since you announced a new version I've stopped to see what needs to be changed/added/removed. Now I'm not sure if I need to continue to develop mesced, since unimapgen's features seem to convergence to those of mesced. I'll probably continue to develop unimapgen with support for both m/mu and tme. So, any input is mostly welcome, especially descriptions of data structures, as well as differences between tme/lom and tme/ddr!

Jean-Yves said:

I may have missed the option, but if not it would be great to be able to assign descriptions to the domains (so that you could then export your domain list as part of the SQL export - I can supply the SQL)

Yes, SQL would be most helpful. This feature was never announced on the forum, so it wasn't implemented.

On the SQL export wizard, could the MU-specific page include a check box to export the mu text file too, so that you don't have to export twice? Very minor point but it would add to the already high level of polish

OK, that's easy. Name would be automatically designated as same as the SQL's, except for extension, right?

More significantly, below is the LoM scenario map file. Could UMG add an option to create the array element automatically. If not, then at least to add double quotes around each line and a comma at the end of each line (except the last?)

Sure, no problem. Does this mean that mmf file's structure has to be changed? Or should I introduce the new file format?

If you're going to export to MU, I would check all the MU options by default, as they are all needed (except trimming FW)

SQL export is meant for general use, not specifically for m/mu. I could (and most probably would) introduce the option to automatically check them all as you suggested.

One other thing - the MU world lives in database tables mostly, so as an old fashioned database boy, I always refer to coordinates as Row-Column (Y,X). Would it be possible to have an option to view coordinates in that order, rather than the more traditional X,Y format?

Isn't the order of fields in SQL clauses arbitrary? But, if that makes your life easier... ;D

Thank you all for all the suggestions. I hope they will be implemented as soon as possible.

[sparrowhawk]

Perun said:

Yes, SQL would be most helpful. This feature was never announced on the forum, so it wasn't implemented.


insert into DOM_Domains
(DOM_SCN_ID, DOM_Description)
values
(1, "Muhaha")


DOM_SCN_ID is the scenario id

OK, that's easy. Name would be automatically designated as same as the SQL's, except for extension, right?

Correct.

Sure, no problem. Does this mean that mmf file's structure has to be changed? Or should I introduce the new file format?

I never need the version without quotes, so you can drop it if you like.

SQL export is meant for general use, not specifically for m/mu. I could (and most probably would) introduce the option to automatically check them all as you suggested.

OK, thanks

Isn't the order of fields in SQL clauses arbitrary? But, if that makes your life easier... ;D

My fault for not being clear - yes the SQL is fine as it is, but I meant on the dockable info palette, where the domain and description are shown

Thank you all for all the suggestions. I hope they will be implemented as soon as possible.

I should jolly well hope so! ;D

[sparrowhawk]

Another very useful thing - could you end ALL SQL statements with a semi-colon -; - so that I can do batch updates?

thank you!

[Perun]

Jean-Yves said:

Another very useful thing - could you end ALL SQL statements with a semi-colon ";" so that I can do batch updates? Many thanks

Aren't there already semicolons after every insert clause? Are you using v2.62?

[sparrowhawk]

OOps - was modifying the above message while you were posting.

Hang on...

Drat! Sorry, I was looking at output from Matija's tool, not UMG. Apologies!

[Perun]

Slightly offtopic here: maybe I wasn't paying attention about domains, but... what are they for?

[sparrowhawk]

Domains are used in the Bloody hand of battle report, as in "The Bloody hand of battle brings death to the domain of Marakith and Blood and Whispers".

[sparrowhawk]

Aaaaaaaahhhhhh! What a plonker!

I gave you all the wrong table name for map data. It's not MAP_MapLocations (that's a deprecated table that is no longer used).

It's actually MPD_MapDescriptions.

All field prefixes should therefore start with MPD_ rather than MAP_

Very, very sorry!

[Perun]

Jean-Yves said:

Aaaaaaaahhhhhh! What a plonker!

OFAH fan, are you, you wally?

Very, very sorry!

Corrected in a matter of seconds. Will be available in the next release.