Difference between revisions of "GetCurrentRegion"

From the Oblivion ConstructionSet Wiki
Jump to navigation Jump to search
imported>DragoonWraith
m
imported>DragoonWraith
m (it's hard to even call this deprecated, since I don't think it's intended at all.)
Line 1: Line 1:
{{Deprecated}}
{{Function
{{Function
  | origin = OBSE
  | origin = OBSE
  | summary = Returns the region in which the player is currently located, if any. In interior cells, generally returns 0. Regions in exterior cells can overlap, therefore it's possible for the player to be in several regions simultaneously, so [[GetCurrentRegions]] is probably the better function to use.
  | summary = Intended to return the region in which the player is currently located, if any. In interior cells, generally returns 0.  
 
However, regions in exterior cells can overlap, therefore it's possible for the player to be in several regions simultaneously, and which this function will actually return is undefined. Therefore, [[GetCurrentRegions]] is the better function to use.
 
In fact, this function was never actually documented in the OBSE command docs, so it is entirely possible that the OBSE team may decide to stop supporting it (unlike regular deprecated functions, which will usually still be supported even if they are not recommended).
  | name = GetCurrentRegion
  | name = GetCurrentRegion
  | returnVal = region
  | returnVal = region

Revision as of 00:40, 7 January 2012

Template:Deprecated

< [[::Category:Functions|Category:Functions]]

A function added by the Oblivion Script Extender.

Syntax:

(region:form) GetCurrentRegion

Intended to return the region in which the player is currently located, if any. In interior cells, generally returns 0.

However, regions in exterior cells can overlap, therefore it's possible for the player to be in several regions simultaneously, and which this function will actually return is undefined. Therefore, GetCurrentRegions is the better function to use.

In fact, this function was never actually documented in the OBSE command docs, so it is entirely possible that the OBSE team may decide to stop supporting it (unlike regular deprecated functions, which will usually still be supported even if they are not recommended).


See Also