This is fast tutorial, just replace the 'aaaaaaaa' with what ever you wish.
Old Friend, on 07 March 2010 - 08:10 AM, said:
Make a new .txt file and rename it as aaaaaaaa.baf and put it to a folder called aaaaaaaa, then put the following code into it ans save, using
this:
IF
Global("a_pack","Locals",1)
THEN
RESPONSE #100
GiveItemCreate(S:StrRef*,O:Object*,I:Usage1,I:Usage2,I:Usage3)
SetGlobal("a_pack","Locals",2)
DestroySelf()
END Where the S:StrRef* is the item files name without the .itm
The O:Object* is
LastSummonerOf(Myself)
And the I:Usage1-3 are numbers of charges, etc. the items extended headers have.
Old Friend, on 07 March 2010 - 08:10 AM, said:
Some lines must be added to baldur.bcs
It's far better to add this line to the .cre's individual script... which is easy to do with WeiDU.exe mod...
The setup-aaaaaaaa.tp2 part is this kind(for aaaaaaaa.cre that's stored in the mods own folder called aaaaaaaa of all things):
BACKUP ~aaaaaaaa/backup~
AUTHOR ~Your name, Contact at (where?)~
BEGIN ~aaaa mods component name~
COMPILE ~aaaaaaaa/aaaaaaaa.baf~
COPY ~aaaaaaaa/aaaaaaaa.cre~ ~override/aaaaaaaa.cre~
WRITE_ACII 0x0248 ~aaaaaaaaaa~ The you just copy a possible setup-*modname*.exe that's already in the game directory and rename it as setup-aaaaaaaaa.exe and start it... it will give you the possibility to install the "aaaa mods component name" component.
Edited by Jarno Mikkola, 07 March 2010 - 10:04 AM.
Cerberus v1.05,
MegaModKits v1.01L,
iiSpellSystemAdjustments v7.1; mods by
Jarno Mikkola the Imp.
FAQ for the Megamods. The Frequently Answered Questions.
Markaan Raneshark said:
PS: I am probably still editing the post above.
PPS: Even though I am a cruel person, I'll never post direct downloading links to you, without warning, unless you'll already see the download counter.
Darpaek, on 26 January 2010 - 09:58 PM, said:
BWS - Standard = not imba. Tactical = stupid hard. Expert = broke.
In case the BG2 game crashes, open up the 'baldur.ini' in your game folder, and under the [Program Options] section in the file, make a new line and type in 'Logging On=1' (without the '' quotes, unless the line is already there)... Save the file and exit. Now go back into the game and try to reproduce the crash. Then look in your game folder again for the Baldur.err file and open it with the Notepad to analyze its contents, or let us do it.
Miloch, on 07 July 2010 - 07:06 PM, said:
Always post the contents of your baldur.err in the case of crashes. I seem to be repeating this like 5 times every time I log on here :P.