Printable View
Hi, I am totally unfamiliar with moding and would like to learn how. Unfortunately the most advanced thing I know how to do is run the game and play it. Do I need to download software? Are there special cheats in-game? I know these questions have probably been asked before, but I have been unable to find any answer, so if you know where I can find out and don't feel like reiterating a whole set of instructions, just redirect me.
Thanks a bunch!
the only thing i know about moding is that it is trial and error. its either oyu get it right or you fail.
as for cheat codes. there is always
www.gamefaqs.com
as for moding tools. there is
these program lets you edit the unit production where the soliders and stuff with there stats..
Gnome_CrusadeUnitEditorv1[1].1.zip
as for editing buidling info this tool helps..
Gnome_UnitBuildProj_Editorv2[1].0.zip
just use google search or you can head to the repository and go to unit forum and get the direct link to the files.
the only hint im gonna give you is that.
go to your my documents. C:my documents make a folder call it what ever..
now go to your c:programs\ where ever you placed your medevial directory.
highlight crusade_unit_prod.txt
and the
crusade_build_prod.txt
copy them ctrl +c or right click these highlighted files and copy.
paste these files in your new folder you created in my documents.
that way after using the programs listed above. and the game doesn't wanna load. you can always have the orignal souce files.
to fix any errors jsut copy the orignal files in your new my document and then past in the C:programs\where you have medevial total war. and yes to over write
as i said its all trial and error the programs listed aboe give greate info mation as to how to go abouts editing things.
çuestion: what does the Gnome editor do that can't be altered from the Crusaders_Unit_Stats file? (I´ve seen it being brought up several times, and I wonder)
I second Unknown Guy in that I would try using wordpad, or preferably notepad++ to edit the unit, build and projectile stats files. I find that the gnome editor is a great tool for making sense of the files and for viewing and understanding them, but when it comes to editing and saving, it can corrupt them and leave you tearing your hair out trying to fix the error. For the build prod in particular I wouldn't use the gnome editor at all, as I've found that to the most troublesome. If you have excel or openoffice you can import the files as tab delimited text files, make changes and then export them again in the same way. This is probably how the developer worked on them. If you are going to try doing this, be certain to preserve all tabs, as a missing tab character means a non working unit/build prod file.
@Cambyses II thank mate. i was half asleep when i responded..
as camb said. the whole point of gnome editor is to familiarze yourself with the layot of the txt info inthe build_prod and unit_prod.
if you get lost while manualy editing it you can always load up the gnome editor and figer out where exactly it is your lookiin for wether it be
which unit can be used by what culture or what faciotns avaibel to what. as well as figuring out which area the unit stats are..
gnome is a good refecrance to figureing out where things are.
some times it ok to use to edit and sav.e but as cambyses said before
it cna corrupt and make oyu wanna tear your hair out (if oyu had any)
in my case cause i shav.e
its scratch the shit out of my scalp. lol:wall:
Gnome editor's only downfall is that sometimes it pastes a load of scrawl that seems to have come from the clipboard or the last entry in the file. For example:
Then it'd paste some of the last stats on the end of it like this:Quote:
VikingThralls INFANTRY 125 3 1 0 82 100 3 DISCOURAGED { CASTLE} "DEFENDER,SPEAR" EARLY YES "HEIGHT( 85 ), RADIUS( 25 ), SCALE( 120 ), PROJECTILE_TYPE( NONE ), SAMURAI( NO ), MARCH_SPEED( 6 ), RUN_SPEED( 10 ), CHARGE_SPEED( 11 ), MIN_TURNSPEED( 2 ), MAX_TURNSPEED( 8 ), TURN_TO_MOTION_SPEED( 8 ), MAX_INMOTION_TURN( 96 ), FORMATION_WIDTH_SPACING( 60 ), FORMATION_LENGTH_SPACING( 60 ), ENGAGEMENT_THRESHOLD( 1500 ), CHARGE_BONUS( 7 ), MELEE_BONUS( -2 ), DEFENCE_BONUS( -3 ), ARMOUR_LEVEL( 1 ), HONOUR_LEVEL( -2 ), AMMO( 0 ), FORMATIONS_PREFERRED_NUM_ROWS( 6 )" NO "own_unit_tooltip1, own_unit_tooltip2, other_unit_tooltip1, other_unit_tooltip4" "NEWPEASANT, YES, YES" "ID_DENMARK, ID_SWEDEN, ID_NORWAY" "Missile, Shocktroop, Spear, Cavalry" "SKIRMISH(0), ADVANCE_PARTY(1),
OUTFLANKING_FORCE(0), MAIN_BODY(2), HOLD_TERRAIN(2), RESERVE(1), REINFORCEMENT(1), ASSAULT(1), ASSAULT_COVER(0), ASSAULT_COVER_CASTLE_ATTACK(0), COVER(0)" 2 UNFORMED LARGE YES 1 NO 1 4 SPEAR NO EARLY NO_FACTION
The way I solve this problem is this:Quote:
"SKIRMISH(0), ADVANCE_PARTY(1),
OUTFLANKING_FORCE(0), MAIN_BODY(2), HOLD_TERRAIN(2), RESERVE(1), REINFORCEMENT(1), ASSAULT(1), ASSAULT_COVER(0), ASSAULT_COVER_CASTLE_ATTACK(0), COVER(0)" 2 UNFORMED LARGE YES 1 NO 1 4 SPEAR NO EARLY NO_FACTION
Each time you save using gnome editor, try opening up the game. If there are errors and it's not quite working right, open up the file that you've edited in gnome editor, using notepad, and scroll down to the last unit, building or projectile entry. If there is a whole load of scrawl or junk, remove it and paste it into a blank notepad.
Attempt to run the game now, if it seems to work fine, you've just fixed the problem. If it doesn't look through the file with wordpad, and look out for things like
Double quotes: ""
Missing commas
or out of place characters like question marks etc. that you might've put in by accident.
And if you've ever taken something out that you shouldn't have, it'll always be in that notepad that has all your bits and pieces.
I recommend notepad++. Ensure that tabs, carriage returns and spaces are visible and wrap is turned on. This ensures that you can see exactly where the errors may be. Usually the incomplete line that Raz is referring to can be deleted. It tends to be a partial repeition on the last data row in the file. The rest of the rubbish and lines of tabs from the end of the file can be removed also, just ensure there is a carriage return and line feed character (CRLF) at the end of the file. That seems to do the trick.
:bow: