15 replies to this topic

[japheth]

Well, since I'm in Tennessee and I have absolutely nothing to do outside of work, I've coded up a few features that could be useful.

PATCH_GAM

I coded PATCH_GAM in response to the various threads I've read where people need to get their BG1 NPC's into the game.

Here's the syntax:

COPY ~mymod/mynpc.cre~ ~override/mymod/mynpc.cre~
(Do your SAY/WRITE_BYTE/whatever else here)
PATCH_GAM ~mynpc~ ~ar2600~ #123 #456

Where ~mynpc~ is the name of your cre file *without* the .cre extension, ~ar2600~ is the area name that you want your NPC to start in *without* the .are extension, #123 is the x co-ordinate and #456 is the y co-ordinate.

It will then splice in your cre file into any saved games (in the save and mpsave directories) and it will also add your NPC entry into the default baldur.gam (for starting new games).

Note however, that there is absolutely *no* way of backing this up other than backing up all saves in the save and mpsave directory to a backup folder.

I haven't wrote any code to backup the saves yet since I can't figure what variable Wes uses for the backup folder. (Wes, maybe you could add this?)

PATCH_GAM will only work with BG1 baldur.gam files. If you try it with any other IE game, WeiDU will choke.

ADD_STORE_ITEM

ADD_STORE_ITEM is just something I did out of boredom.

Here's the syntax:

COPY_EXISTING ~ribald.sto~ ~override/ribald.sto~
ADD_STORE_ITEM ~myitem~ #20 #0 #0 #1 #5

Where ~myitem~ is the name of your item file *without* the .itm extension, #20 is the first extension header's # of charges, #0 is the second extension header's # of charges, #0 is the third extension header's # of charges, #1 are the item flags (more on this below) and #5 are the # of items in stock.

The flags work as follows:

#1 Identified
#2 Stealable
#4 Unstealable
#3 Identified & Stealable
#5 Identified & Unstealable

In most cases putting #1 for the flags is fine.


I could code up some more feature like ADD_STORE_ITEM if people think there's a need for them. (e.g. Like ADD_TRIGGER for areas or something.)

I'll post the diffs for this when I get a chance to get on my laptop this afternoon.

[japheth]

I could code up some more feature like ADD_STORE_ITEM if people think there's a need for them.  (e.g. Like ADD_TRIGGER for areas or something.)

Ghrey was just wondering about this for BoB last night.

Ah, he needs something like ADD_TRIGGER?

Oh, and I should also note that ADD_STORE_ITEM will work on any .sto version.

[japheth]

Yeah, I plan on adding ADD_MAP_ENTRY later on. I did this the "hard" way a few months back using WeiDU's READ_BYTE/SHORT/LONG and WHILE loops.

Nice point about checking to see if it's already there. I'll write that out today or tonight sometime.

[weimer]

Japh, you are a small god. This is just the sort of creeping featurism we embrace with WeiDU. Send me the diffs at your leisure.

[Idobek]

As you are asking; I have some of suggestions:

1) ADD_CREATURE_ITEM ~newitem~ (#flags)
- this would work like ADD_STORE_ITEM and would add the new item into the first available inventory slot.

2) OVERWRITE_CREATURE_ITEM ~itemslot~ ~newitem~ (#flags)
- self explanatory, I think.

3) ADD_CONTAINER_ITEM ~containernumber~ ~newitem~ (#flags)
- as you are playing with area files, I thought I'd throw this in. It can be done with scripting but this would be much more elegant.

Also, I wonder if you could look into "this" for me? If I am doing something wrong I'd like to know. Otherwise, make it work. Pretty please.

Have fun, and as Wes says; you are a god.

[Loriel]

I was gone for a few days, pondering this very issue while I didn't have my computer. Let me be the one hundred and eleventh person to say, "Japh, you rock!"

EDIT: Casting my vote for ADD_AREA_TRIGGER

[hlidskialf]

*Ahem...* Bitching Japh!

[Gabrielle]

This would be great for those of us that are involved in BG 1 mods. B)

[japheth]

I've revised the syntax for ADD_STORE_ITEM a bit.

It works like this now:

ADD_STORE_ITEM [optional_plus] ~myitem~ #10 #0 #0 ~IDENTIFIED~ #5

The [optional_plus] is for overwriting items already in the store. So... if you're worried that the item might already be in there, just stick the + in there and it will do one of the following:

a) Overwrite the item if it's there .
b) Add the item if it isn't there.

I've made adding the flags a bit easier as well. Here's the list of valid flags you can use:

• IDENTIFIED
  
• UNSTEALABLE
  
• STOLEN
  
• IDENTIFIED&STOLEN
  
• IDENTIFIED&UNSTEALABLE

That's about it.

[Idobek]

From Idobek (ie. me):

2) OVERWRITE_CREATURE_ITEM ~itemslot~ ~newitem~ (#flags)
- self explanatory, I think.

From Ghreyfain:

TakeItemReplace() works fine for this, in ToB at any rate.

The problem with doing this by script is that you (or at least I) can't then equip the item. (I have tried a whole host of commands to try and do this.) Hence my suggestion. I would revise my suggestion a little though:

OVERWRITE_CREATURE_ITEM ~itemslot~ ~olditem~ ~newitem~ (#flags)

Another suggestion: READ_ASCII, is detailed "here".

[Gabrielle]

Looking at this which is the final code for doing this for stores?

Plus I would like to make a request that added things like this would be put up some where or put into the Weidu ReadMe as a tutorial. Looking for something that was added to Weidu in these forums is timeing.

[Idobek]

The final code for ADD_STORE_ITEM is as per Japh's post on Sep 9 2003.

The first 3 #'s are the number of charges of the extended headers. The last # is for the number in stock.