Difference between revisions of "Category talk:Functions"
imported>DragoonWraith (Integrate OBSE functions together with Vanilla functions? (filtering one or the other would be maintained)) |
imported>DragoonWraith m (undocumented script function header) |
||
Line 13: | Line 13: | ||
I am quite willing to do the work to set this up, but I'm not into unilateral decisions like this, so I would like some feedback. | I am quite willing to do the work to set this up, but I'm not into unilateral decisions like this, so I would like some feedback. | ||
Unducumented script functions found | == Unducumented script functions found == | ||
* DumpMasterFileSeekData | * DumpMasterFileSeekData |
Revision as of 12:24, 8 June 2007
OBSE
Dragoon Wraith TALK 13:24, 8 June 2007 (EDT): When OBSE first came out, I went and made it its own section, complete with function categories and the like. I fell away from Oblivion modding, and those pages have not been updated in my absence.
Noticing the lack of those functions, mmmpld went and accomplished the impressive feat of cataloging all functions, OBSE and Vanilla, here.
Given that this is considered useful, should OBSE functions be included on this main Functions page? We would, of course, still have Vanilla functions categories, and it would be easy to filter out OBSE functions for users who do not use OBSE.
It would mean a few things. First, this page would be quite a bit larger than it is. Second, this page is linked to directly from the first page, and OBSE is not officially supported by Bethesda (which may lead to some issues, or may not). Third, we would need to create additional OBSE and Vanilla versions of each function category, so we would have, for example, Actor Functions, Actor Functions: Vanilla, and Actor Functions: OBSE - this is the only way to maintain the ability to filter out only the kinds of functions we want to see. It would also mean more categories listed at the bottom of each functions' page - for example, you might see "Functions | Functions: Vanilla | Actor Functions | Actor Functions: Vanilla" - I don't mind this, but it could be an issue.
The advantages is that it's much easier for scripters who are actually using OBSE, without making things more difficult for scripters who don't. The functions wouldn't be segregated, and it would be easier to see what functions are available.
I am quite willing to do the work to set this up, but I'm not into unilateral decisions like this, so I would like some feedback.
Unducumented script functions found
- DumpMasterFileSeekData
- StartMasterFileSeekData
- SetSceneIsComplex i
- SetNoAvoidance i
- SetAllVisible i
- SetAllReachable i
- ShowViewerStrings
- ShowNameMenu
i=Integer parameter
Are they useful for anything? --JustTim 12:28, 10 May 2006 (EDT)