Development Cycle Archive
Thread: IT 7-6: Vertical Item Movement
Karquile wrote:
The workaround for now is to move stuff by name when the conflict exists. My alt in Bespine was able to
/move inert forward 50
and put some good Polymer on the shelf.
PS Editing doesn't work for usin this Forum because you apparently need the create_thread privilege. That might be a Forum bug.
Karquile wrote:
The problem occurs when there is an object within your targetable world whose name conflicts with one of the four direction keywords. And the classic example, most commonly biting us in the keister right now, is theFaction Base. If your city has one, it is probably named
Forward Outpost
and guess what. When you sit in your house and type /move forward 50, it assumes you meant the base. Which indeed is not in your house.
This also happens to me on live, but i have not been able to reproduce it consistently. It's kind of random, and it sometimes depends on what PC I am using.
LLJK_Griz wrote:
Sneezy wrote:
TC only bug: /move forwardusing the command lineSTILL creates a "That object is not in the building" error message. This error message is received on /move up now also.
This also exists on live, I have not been able to use /move forward in my house since publish 5.
This might not be totally on topic but here goes anyway.
Has anyone ever noticed that the /rotate command and the Rotate radial menu do just the opposite of each other? If you clck the radial on objects and do Rotate Right, you get the object to turn counter clockwise. If you type /rotate right 90, the object rotates clockwise.
While you are doing move up and down, could we maybe get this fixed too?
Lightsabersmith wrote:
This might not be totally on topic but here goes anyway.
Has anyone ever noticed that the /rotate command and the Rotate radial menu do just the opposite of each other? If you clck the radial on objects and do Rotate Right, you get the object to turn counter clockwise. If you type /rotate right 90, the object rotates clockwise.
While you are doing move up and down, could we maybe get this fixed too?
I have reported this in the (dim distant) past, but this might be a great time to get it fixed!
d0qtrX wrote:
This also happens to me on live, but i have not been able to reproduce it consistently. It's kind of random, and it sometimes depends on what PC I am using.
LLJK_Griz wrote:
Sneezy wrote:
TC only bug: /move forwardusing the command lineSTILL creates a "That object is not in the building" error message. This error message is received on /move up now also.
This also exists on live, I have not been able to use /move forward in my house since publish 5.
I just tested, it's Karquile's forward outpost bug. I'm like 500m from our base complex and apparently that's close enough to be targetted. Other people in the same town can don't have the problem because they're further away from the bases.
Karquile wrote:
So again, just a reminder that the workaround is to NAME the object:
/move glass up 20
As long as you know this trick, you should be able to move anything you're allowed to move. (They should still fix the targeting syntax.)
- A broken decryptor
- A camera
- A decorative shisha
- A photographic image
- A recorded image...
Good suggestion. I just now tried this with several of the "A" named objects. However, in every case the system returned the "format:" error message and the object did not move. Itriedit initially without caps (/move a_recorded_image up 10) and then carefully capitalizing just as the object was named (/move A_Recorded_Image up 10), but still no go.
Trayson_Antilles wrote:
Have you tried using object spaces? Most databases use _ instead of a space, so your A recording device would actually be A_recording_device. Worth a shot at any rate.