The Fallout Script Extender, or FOSE for short, is a modder's resource that expands the scripting capabilities of Fallout 3. It does so without modifying the Fallout3.exe or the G.E.C.K. files on disk, so there are no permanent side effects.

Compatibility:

FOSE supports these versions of Fallout 3 (from either a retail DVD or Steam):
- 1.0.0.15
- 1.1.0.35
- 1.4.0.6 (original release)
- 1.4.0.6 (alternate release, found on steam and some European patches)

FOSE is compatible with the 1.1.0.36 G.E.C.K.

Incompatibilities:
* FOSE is not compatible with the original, unpatched DVD or Steam version. Either version patched to 1.0.0.15 or 1.4.0.6 will work.
* FOSE is not compatible with the Direct2Drive (D2D) or the Russian version of Fallout 3 protected by StarForce. FOSE will never be compatible with these versions, as they are encrypted and it would be illegal to break the encryption.
* FOSE is currently incompatible with Windows Live, so when running via fose_loader.exe, Live will be disabled. Live functions as an anti-cheat mechanism, so it disables itself if it detects any in-memory modifications to the executable, despite the fact that Fallout has no multiplayer component. Since Live cannot tell the difference between the modifications we make and the modifications a cheating program would make, we will probably never be directly compatible. To download DLC and updates, simply launch Fallout normally. Live stores DLC and save files in a separate folder when active, so some things may need to be moved around - see the official Fallout forums for more information.

This initial release adds 189 new scripting functions including:
- basic input functions based on DX scancodes
- basic form list functions
- debugging console functions
- various weapon and inventory item Get and Set functions
- script versions of several console functions
- Looping functions (Label, Goto)
- GetCrosshairRef
- get and set game setting and INI functions
- loaded mod informtion functions
- reference walking functions
- Basic UI Functions (GetUIFloat, SetUIFloat, SetUIString)
- basic math and bit flag functions
- GetGameRestarted, GetGameLoaded
- temporary base form cloning functions

Can I add something to requests (assuming it isn't available already)

SetWeaponFireRate or similar? you seem to have pretty much everything except that when dealing with "weapons"

there is a GetWeaponFireRate...so hopefully this is possible ^_^

EDIT: also...I know its possible to change the max ammo in a clip...but is it possible to change the current ammo in a clip?
Changing the max ammo only affects the gun upon reload so being able to change current ammo would be a big help here.

I hate to sound pushy, but will FOSE support the following in the next version

Also...either I'm using the command wrong, or http://fose.silverlock.org/fose_command_doc.html#SetWeaponAmmo isn't working correctly. I change ammo from 10mm to .556 but the gun continues to use 10mm

Thanks again for all your hard work and this amazing tool,
TheDamned

I am not sure whether a SetWeaponFireRate would work. If I remember correctly, SetWeaponFireRate seems to be calculated from other fields and is not settable directly in the GECK. I am not sure whether changing it directly would have any effect. But we can certainly look at it for v2.

We don't know how to change the current ammo yet. We haven't found the place where it is stored. We've had several requests for it, but we've not had much luck finding it yet.

Have you caused the weapon to reload yet? Several threads ago we discovered that until the current weapon's clip runs out Fallout will continue to use the old ammo unless a reload happens. Wherever the current ammo count is stored is also where the old ammo itself is stored. Until the weapon is reloaded it will continue to use the old ammo. We've suggested that people force a reload by changing the clip size for the weapon and using TapControl 7. When we locate the current clip count and current ammo info (which may be stored in the UI somewhere) we'll be able to help more. We'll probably include a Reload function which will force a reload using the current ammo and would work even if the clip was full.

When I say Fire Rate I mean the value Highlighted in

Be sure to thank Ian for his quick work looking into 1.4.0.6.

Ah - that one we can change. I thought you meant the Attack Shots/Sec field on the Art and Sound tab which is calculated. I can easily add a SetWeaponFireRate for v2.

creating a very simple workaround to things like schematic issues overriding vanilla bench scripts, etc.

Is there any way I can use the russian version of the game patched to 1.4, with FOSE?

Perhaps OT, but the workbench issue has a great work-around mod: http://www.gamesas.com/bgsforums/index.php?showtopic=961589.

When I say Fire Rate I mean the value Highlighted in

As for forcing a reload...not sure if that will be an option (at least for what I am working on) thanks for the tip/info though I'm sure I'll find it useful in the near future ^_^...For a future "force reload" command would it be possible to force a reload without playing the animation?

Thanks,
TheDamned

Thank you for retrograding to support V1.0.015. I'm really enjoying having a fully functional VATS and having FOSE at the same time.

That value is only used if the 'Automatic' flag is checked. The factor which determine the weapon's Rate of Fire reside in the Art and Sound tab. There are two entries in the Animation sub section. The first, "Multiplier", is a number which is multiplied by the Jam & Reload time set by the Reload animation that is selected at the bottom under "Reload Anim". The second, "Attack Multiplier", is a number which is multiplied by the Attack animation time set by the Attack animation that is selected at the bottom under "Attack Anim". As for calculating the results of it, just do a little math with what the GECK says the numbers are and you'll have the settings for each of them. When the Automatic flag is checked, these multipliers are still used, but the Fire Rate is multiplied by the result of the Attack Multiplier's equation.

And that's how attack animations work.

Yes but this could be useful in having Automatic Rifles be able to alternate between.
"Slow accurate" and "Fast inaccurate".

Yeah I been playing around with animation multipliers to try get a slower firing weapon than 1 but the animations seem to have long periods of no animation but at the start and end meaning at the end of the animation you have to weight still to do something...
Not to mention its asthough your moving in slow motion...
A way to actually change the speed of the weapon would be really useful.

I have only just really began to understand the work of FOSE and I think I may deffinately have to read through alot of your threads....

Changing animations as a means of controlling Fire Rate is a poor method in my opinion and , as you seem to have figured out, can be quite buggy.

TheDamned

EDIT: sorry for going off-topic here... :angel:

I still don't have FO3 yet, but I thought I'd see if I could port my recent FPS capper OBSE plugin to run on FOSE instead anyway, since I've heard that fallout has some stuttering problems. I downloaded 1.1 beta 2:

Has anyone written a FOSE plugin yet? Does FOSE support plugins atm? I see an API, but I'm not sure if it's intended to be used yet or not. Could you guys add a sample plugin project for FOSE like there is for OBSE please?

I had a bit of trouble with the project file for FOSE there... possibly I did something very wrong, I feel very clumsy around damned project files. I got it working, but I had to add everything in src\common, everything in src\fose_common, winmm.lib, and I had to write code for Bitstring::Dispose.

BTW, the Bitstring code there looks bugged... the 2nd constructor is calling Alloc without initializing members, and Alloc is calling Dispose, which then has no way of telling whether or not the pointer is initialized.

Hi guys, first off I think it's neccessary that I pay you BIG respects for your work. Without FOSE, half of our mods wouldn't be possible, and especially not the one I'm working on currently. Thank you a lot!

The reason I'm posting here is nothing severe, just something that confused me. It's about the documentation actually. While generally very well written, I happened on a little something today. The functions GetWeaponResistType and SetWeaponResistTime take as a parameter an integer, using the code ResistValue. However, when I click on it, I'm brought to the code list for ActorValues, and the ResistValue list seems missing. Now either these two are the same (then maybe pointing it out would be a good thing, because it's rather confusing the way it is) or something went a-missing in the docs. Could you clear this up for me?

we found with OBSE that documentation consumed a lot of time that could have been better spent on development.

Yes, Documenting stuff is allmost as time-consuming as making stuff, I know. And I think you did a great job with the FOSE-docs. Changing the title of the ActorValues List to ActorValues/ResistType would be completely sufficient in to avoid confusion this case I think.
Thanks, and keep fighting the good fight!