- getpos [axis] = returns the position in axis value of the selected
object –
getpos x
- setpos [axis] [value] = sets the position of the selected object –
setpos z 200
- getangle [axis] = returns the angle of the selected object –
getangle y
- setangle [axis] [value] = sets the angle of the selected object –
setangle x 45
- rotate [axis] [value] = rotates the selected object manually –
rotate x 45
Your axis are X,Y,Z
Helpful when placing or positioning objects:
- disable = disable object (click on object first to retrieve item
code)
- markfordelete = permanently remove object (click on object first to
retrieve item code)
- player.placeatme [item_code] = place any object or item at your
current position
- tcl = toggle clipping, you won't collide with objects and gravity has no effect on you, allows you to place objects on high walls, ceilings and
up in the air if you like
- twf = toggle wireframe, gives you a wireframe perspective of your
surroundings and objects
Objects can be placed regardless of clipping or collisions with other objects, but you may find that returning after the location cell has reloaded that these objects have moved again.
Circumvent this by "picking up" the item after positioning it through the console, then "dropping" it again. While doing this, take care not to shift or move the item (this can prove difficult sometimes), the method here is to "reset" the item with clipping and object collision on.
Clipping seems to toggle off once you start redefining an item's positioning with absolute values, you can leave your book half poking out the desk and walk out the building, it's fine - until you come back to find the book tossed across the room by physics. "Resetting" an object this way, after moving it around, can save you that surprise later.
I had to deal with this problem while attempting to place a map of the dragon burials on a table top, problem was my z axis value for positioning was actually clipping into the table surface, when I returned the map was lying beneath the table, as though it had "fallen through".
This doesn't seem to be the case with CONT objects like "apiaries" or "strongboxes".
e
.