-
Tools
-
-
Entries
-
 CA_BIF_BUF_Utils.zip
Here's the full suite of official TW BIF & BUF utilities.
Purpgrab makes BIFs from TGAS. Drag the Tga into the DOS window to create. Purple 255,0,255 be be transparent.
Seqgrab makes multiframe BIFS.
Buffy the Bif slayer makes BUFS from BIFS ( a BUF is a BIF with a shadow which will appear semi-transparent, palette colour 0)
The code recolours certain palette spreads on the stratpieces for their coloured bases, palette spreads 2-15 & 16-31.
Get your dpaint out...
|
See also
Guides
Guides & FAQ
Tools
|
|
|
|
MTWedit15-src.ZIP
Free source code for Delphi 6-7.
Engineer
ver. 1.5
***
This is Medieval Total WAR 1.x units editor. You can use it free for non commercial projects and home use.
All comments on russian forums: http://www.twow.ru/forums/ - English message allowed.
***
Features:
1. Load units from "crusaders_unit_prod11.txt".
2. Select and show units properties - read articles on forum - how change unit properties.
3. Look for all units files, and show them.
4. Edit unit properties. Just press save bttn before exit!
5. Duplicate existing MTW units into new one (CREATE YOU OWN NEW UNIT). All unit files also copyed.
6. Save:
"crusaders_unit_prod11.txt" with new additional units.
write new files "\Loc\Eng\names.txt", "\Textures\Men\deadpage coords.txt" and "\Loc\Eng\Descriptions.txt" with new names and descriptions.
7. Remove selected unit and all it files.
8. Load, Save, remove and show all added units as You own MOD.
***
WARNING FOR beginners!
1. You can't change unit's during the game, - start new company game after each add/remove units.
2. Save this files befor using editor:
Medieval - Total War\crusaders_unit_prod11.txt
Medieval - Total War\Loc\Eng\names.txt
Medieval - Total War\Loc\Eng\Descriptions.txt
Medieval - Total War\Textures\Men\deadpage coords.txt
- you can lose them.
3. Do not change text files manually, editor calc strings & intervals
***
With best regards,
Engineer
|
|
|
|
|
MTWEdit15.ZIP
Engineer
ver. 1.5
***
This is Medieval Total WAR 1.x units editor. You can use it free for non commercial projects and home use.
All comments on russian forums: http://www.twow.ru/forums/ - English message allowed.
***
Features:
1. Load units from "crusaders_unit_prod11.txt".
2. Select and show units properties - read articles on forum - how change unit properties.
3. Look for all units files, and show them.
4. Edit unit properties. Just press save bttn before exit!
5. Duplicate existing MTW units into new one (CREATE YOU OWN NEW UNIT). All unit files also copyed.
6. Save:
"crusaders_unit_prod11.txt" with new additional units.
write new files "\Loc\Eng\names.txt", "\Textures\Men\deadpage coords.txt" and "\Loc\Eng\Descriptions.txt" with new names and descriptions.
7. Remove selected unit and all it files.
8. Load, Save, remove and show all added units as You own MOD.
***
WARNING FOR beginners!
1. You can't change unit's during the game, - start new company game after each add/remove units.
2. Save this files befor using editor:
Medieval - Total War\crusaders_unit_prod11.txt
Medieval - Total War\Loc\Eng\names.txt
Medieval - Total War\Loc\Eng\Descriptions.txt
Medieval - Total War\Textures\Men\deadpage coords.txt
- you can lose them.
3. Do not change text files manually, editor calc strings & intervals
***
With best regards,
Engineer
|
|
|
|
|
LMM4v1_BETA_VERSION.zip
LukMapMaker Installation instructions
-------------------------------------
This utility has been tested on Windows XP Home Edition. It should work
with NT and 2000 providing you have the latest release (version 5.6) of
Microsoft Windows VB Script.
This utility requires 3 third-party objects. A GUI interface, a Graphics
package and BifReader 2.2a.
BifReader 2.2a is included in the LMM download, by permission of the the
author RSW, and requires no installation as such.
The GUI, "wshltwtnonmodaldialog.ocx", is also included in this download,
again by kind permission of the author - Jim Warrington. Check out his site
at the following link - http://home.att.net/~wshvbs/
The last one, "csImageFileTrial.dll", will require a trial version download
(read the FAQ for a bit more info).
The OCX and DLL objects will require moving to your SYSTEM32 directory and
then registering within Windows.
GUI OCX
-------
1) Move the OCX "wshLtWtNonModalDalog.ocx" from the LMM root folder into
your "C:\WINDOWS\SYSTEM32" folder
2) Register this OCX via the Start/Run command. Enter the following -
"Regsvr32 wshltwtnonmodaldialog.ocx"
It should now be registered on your PC.
Graphics DLL
------------
1) Download the file "csImageFileTrial.dll" from the link -
http://www.chestysoft.com/imagefile/download.asp
2) Unzip the folder "csift" (or "csift20") and move the DLL "csImageFileTrial.dll"
into your "C:\WINDOWS\SYSTEM32" folder
3) Register this DLL via the Start/Run command. Enter the following -
"Regsvr32 csImageFileTrial.dll"
It should now be registered on your PC.
Finished?
---------
Yes. You should now be able to run the VB Script file "LukMapMaker.vbs".
Wellington.
Other versions:
LBMPaletteInOut.zip
LukMapMaker_GUI_OCX.zip
LMM3v3_BETA_Version.zip
LMM3_BETA_VERSION.zip
LMM2_PROVISIONAL_VERSION2.zip
LukMapMaker_PROVISIONAL_VERSION.zip
Samplemaps:
ChinaMap.zip
LMM3_EXAMPLE_Britain_Original.zip
LMM4_GMM_EXAMPLE_HOLYLAND.zip
LukMapMaker2_EXAMPLE_MiddleEast.zip
LukMapMaker_EXAMPLE_Britiain.zip
LukMapMaker_EXAMPLE_WestMed.zip
|
|
|
|
|
LBMPaletteInOut.zip
LBMPaletteInOut is a small utility for importing or extracting
palettes (a table of 256 3-byte RGB colours) by either -
- Extracting the palette from a valid LBM file into a 'text palette'
- Importing a 'text palette' into a valid LBM file
It does this by retaining 'text palettes' that represent the actual
hex palette. These 'text palettes' follow the same convention as
the text palette in LukMapMaker.
After installing this zip into a folder you should have 4 files -
- LBMPaletteInOut.vbs
- BinaryTable.bin
- wshLWForm.ocx
- LBMPalette_Example.txt
You must install and register the OCX, so ...
Installation
------------
1) Move the OCX "wshLWForm.ocx" into your "C:\WINDOWS\SYSTEM32" folder
2) Register this OCX via the Start/Run command. Enter the following -
"Regsvr32 wshLWForm.ocx.ocx"
It should now be registered on your PC.
Using LBMPaletteInOut
---------------------
Every execution allows 1 operation only, either an Import or an Extract.
LBMPaletteInOut requires ALL files, either LBM's or text pallettes, to be
present in this root folder.
Any LBM files that you require to either Import or Extract the palette from
will require moving to this root folder 1st. If you are using the Extract
operation then after running LBMPaletteInOut you will have to copy the LBM
file back into it's original location.
The format of the text palettes is simple (and follows the LukMapMaker format
for it's own "LBMPalette.txt"). You can edit, create, amend these text palettes
as you wish, then import them into the appropiate LBM.
File conventions and usage
--------------------------
LBMPalleteInOut recognises an LBM file as being '***.blm' where *** can be
anything.
LBMPalleteInOut recognises a 'text palette' as being a text file named
'LBMPalette***.txt' where *** can be anything.
When Extracting a palette from an LBM it will create a text palette of the
format 'LBMPalette_xxx.txt' where 'xxx' is the name of the LBM. For example,
extracting the palette from the file 'LukMap2.lbm' will create a text palette
named 'LBMPalette_LukMap2.txt'.
And that's about it. I've provided a text palette example. You will have to copy
an LBM file from your MTW directory into order to test LBMPalleteInOut. If you
have an hex editor it should be easy to amend/create a text palette, Import it
into an LBM and then check the results.
Example of swopping pallettes
-----------------------------
One final example. If you wish to swop palettes between 2 LBM files, lets call
them xxx.lbm and yyy.lbm you should -
1) copy both LBMs to the LBMPaletteInOut folder
2) run LBMPaletteInOut, Extracting the palette from xxx.lbm, and thus creating
the (text palette) file LBMPalette_xxx.txt
3) run LBMPaletteInOut, Extracting the palette from yyy.lbm, and thus creating
the (text palette) file LBMPalette_yyy.txt
4) run LBMPaletteInOut, Importing LBMPalette_xxx.txt to yyy.lbm
5) run LBMPaletteInOut, Importing LBMPalette_yyy.txt to xxx.lbm
6) copy/move both lbms back to their original folders
Obviously, if you wish to change the palettes you can amend the 256 entries in
text palette files after step 3) - before the Import steps.
Note: I recommend you don't keep too many text palettes or LBM files in this folder
as it may be difficult to see the wood from the trees.
Have fun
Wellington
Older version
LBMPaletteInOut.zip
|
|
|
|
|
