The New Vegas Script Extender is a project to provide additional scripting functionality for modders. Many of you will be familiar with our work on the Oblivion Script Extender (OBSE) and the Fallout Script Extender (FOSE). NVSE will be a continuation of that work.

There have been lots of questions swirling around various posts about what we are doing and when we are doing it. I'll try and answer those basic questions below. The thread will serve as a place to update you on our progress, and for you to put in requests for functionality (either to be ported from previous versions or functionality specific to New Vegas.)

FAQ

• We are working on the basics of the Script Extender, using FOSE as a jumping off point for functionality.
  
• New Vegas is still very young, and being patched on a regular basis. Each time a patch comes out, some amount of rework is required for NVSE to function. We do not want to release until New Vegas becomes stable, as supporting multiple patches can be very labor intensive.
  
• As a steam-only game, the New Vegas executable is encrypted. We have received support from Valve for loading NVSE into the steam wrapper when launching New Vegas. So, we are in business. Thanks a ton to Valve for their continued support.

So - what functionality do you folks want for our initial release? Having this information will help direct our porting efforts.

Implemented for v1


Requested Functionality

• Inventory walking functions
  
• String vars
  
• GetGameLoaded/Restarted
  
• UI Functions
  
• GetCrosshairRef
  
• RemoveAllTypedItems variations
  
• Get/Add/RemoveWeaponMod

Good luck with the build! I know this version is more of a challenge then before - we'll be here to cheer you on and complain (the usual drill).

Cheers,

Miax

Excellent news, thanks behippo & team.

The must-haves, to me, are the formlist functions (add/remove/get), loops and keypress detection. Then getequippedobject, ref walking and inventory walking come next.
However, are they easier/harder to keep updated than the form changing ones like setweaponXXX etc.?

How difficult they are depends on the scope of the changes being made with the patches. The biggest thing that happens with the patches is a change in the memory addresses. We've got maybe 50 pieces that are dependent on the address in memory (the address to patch the command table to add our functions is a good example.) To update these we just need to find the new places in memory. When they start making changes to the internal classes, however, is when things get much more complex.

The formlist functions and inventory functions are actually just like the form changing functions (get/setweaponXXX). They depend on the definition of the internal class, and as long as it doesn't change there is no need to update them. This is the main reason we've been able to just bring a pile of functions over from OBSE to FOSE (and now to NVSE). Once the basic class information is decoded, most of that is just busy work.

Loops and keypress detection are more complicated, but essential. I imagine they will be in the first version.

I'll add a running list of suggestions to the first post so people can see what has been requested.

How's about my string vars then behippo?

Always going on about your string vars, DarN! I'll add them to the list. Perhaps I can get scruggsy to help work on those. But we will get them done this time.

My apologies about FOSE, actually. I got really burned out and sorta dropped development for a year. Only one real release of FOSE (compared to 19 now for OBSE) is pretty sad. But I am all recharged and ready to go. OBSE and FOSE tended to work in frantic spurts. Lots of improvement in small amounts of time until real life sets in. I'm really going to try and get NVSE (and perhaps FOSE as well) to parity with OBSE.

Huzzah! Can't wait for NVSE to come to fruition. Wishlist:

• GetNVSEVersion
  
• GetNVSEBeta
  
• GetNVSEBetaRevision
  
• IsControl
  
• SetIsControl
  
• IsKeyPressed
  
• GetKeyPress
  
• GetGameLoaded
  
• GetGameRestarted
  
• GetWeaponHasScope
  
• SetWeight
  
• Get/SetNumericGameSetting
  
• Get/SetNumericIniSetting
  
• SetUIString
  
• SetUIFloat
  
• GetCrosshairREF
  
• GetNOID
  
• GetRecordCount

Thanks for the update. Can't wait!

You're preaching to the choir. I'm pretty much in the same situation, so I fully understand where you're coming from.

Hell, I achieved pretty much what I wanted with the functions you provided, it's just that it bloats everything to the point of ridicule. I must confess I'm drooling at the array and string stuff the OBSE users have access to though. :liplick:

Well now that functionality is tested and seems safe, it ought to be pretty easy to move over to both. I'll really try to get those in the first version. The likelihood depends on how long they keep patching the game.

Which UI functions in particular do you need?

If you match the FOSE functions for the UI, DUINV should work with NVSE out of the box.

- GetUIString would be a logical choice once string vars are in.
- I also seem to remember some issues with parameter passing that I had back in the day. I don't recall exactly what though - that thread is probably long gone by now.
- A way to get to the various list items would be a huge help.

Here's a post I made in a different thread about what I want in NVSE:



You could do the version of RemoveAllTypedObjects that I want by passing it a formlist of every single form in the game aside from the ones that are in one specific form, so I don't think it should be too difficult for you to do.

Of course, I also want loops/formlist subtraction/inventory walking/button pressing functions, too, but that's the only one that I'm positive wasn't in FOSE (were inventory walking functions in FOSE? I don't remember...:/).

I'm not the UI expert that scruggsy was, but I will see what I can do.

I'll have to take a look at this after I have the basics up and running. I've been out of the loop for a bit, and I am not sure I understand exactly what you want. I'm sure I'll have a better sense after I've got the form list functions going.

One helpful thing would be a version of RemoveAllTypedItems that uses a form list for inclusion rather than exclusion.

The other would be get/mod/set weight functions for items. I can manage without, but it would be handy.

That's exactly what I just asked for:p

RemoveAllTypedItems works a lot like RemoveAllItems, except you can tell it to remove just certain types of items, and you can tell it not to remove certain items (you can also make it so it doesn't display a ton of notifications that you gained/lost items, which is great). It's used when going into the energy weapons shop in Freeside (Silver Rush?) and almost certainly the casinos in the Strip to remove you of your weapons, but allow you to take some specific weapons with you (the hidden ones, I think the Silenced 22 Pistol being one of them). Of course, it also maintains item health.

EDIT: By 'only certain types of items' I mean you can tell it to remove Weapons, Apparel, Chems, etc., going by the Object Type Code (so 40 is Weapons, 31 Misc, etc)

The get/set/modweight is very easy (assuming vanilla doesn't provide them). The other seems doable as well.

Doesn't look like there's a vanilla get/set/modweight.

Vanilla Script Commands: 117 new/not in FO3

Might be a handy reference until there's a GECK Wiki.

Heh, I guess I skipped over your post.



Very cool. I don't see a way of doing the weights in vanilla so if it's there already I'm just blind to it. All I know of is setting the value for items. Give me a year and I'll probably have a bunch more item related requests.

If both of these are doable, my bag mod will be a lot easier to manage. :goodjob:

Some nice menu shortcuts there. Thanks.

Thanks. I hadn't dumped that out to be sure yet. There does seem to be some useful functions. I'll have to look, but I am wondering whether GetRecticuleObject returns the base object type, or an actual ref to that object. If it is the latter, then GetCrosshairRef won't be needed this time. If not, I will just work off of their implementation to get the ref (which they have to have for part of their function.) I'll get a command doc list up on the NVSE site as soon as I've gotten some more things live.

Seemed to fit here. It's a chunk of a http://www.gamesas.com/index.php?/topic/1122265-initial-technical-details/page__view__findpost__p__16508545, just alphebetized and color coded. I almost asked for Con_SetCameraFOV, but there's already a SetCameraFOV (finally). Might help reduce requests for already covered functions here.

I created http://www.gamesas.com/index.php?/topic/1127542-new-script-functions/ to keep track of new/changed script functions, though I've only tested one of the new ones so far, so only that one has any detail written about it.

I'd hope that all of the 'key' commands make it in the first cut:

GetControl
TapKey
IsKeyPressed
HoldKey
ReleaseKey
GetNumKetsPressed
GetKeyPress

Nice to have, but not vital:
SetIsControl*
IsControl*

The key and control commands will all be there for the first release.

all i really want is this:

con_closeallmenus

so that i can get my "activate key closes containers when they are open" back.

tnx for all your work btw