WikiObjects and Object Sets
The kinds of objects you can build with, how they differ, and how object sets save your builds.
GamerX is a building server: you can build anything with objects. On the classic GamerX many building tools were for admins only. GamerX.mp has no admins, so they are open to everyone.
The kinds of objects
| Kind | Who sees it | Page |
|---|---|---|
| Player objects (POBs) | Only you (others can copy your build into their own view) | player-objects |
| Streamed objects | Everyone in the same virtual world | streamed-objects |
| Holding objects | Everyone: they are attached to your character | holding-objects |
| Vehicle objects | Everyone: they ride on a vehicle | vehicle-objects |
Objects use GTA San Andreas object model IDs (for example 1655 is a ramp). GamerX.mp also has its own custom objects, numbered from 20000: 20000 is the Cluckin' Bell hat. You need an open.mp or SA-MP 0.3.DL client to see custom objects.
Object sets
A build is saved as a named object set. Player objects and streamed objects share the same sets, so a set saved one way can be loaded the other way.
| Command | What it does |
|---|---|
/sapo <name> | Save all your player objects as a set |
/samso <name> | Save your streamed objects as a set |
/saso <name> | Save every streamed object on the server as your set |
/lpos <name> [owner] | Load a set as player objects (only you see them) |
/lsos <name> [owner] | Load a set as streamed objects (everyone sees them) |
/psos <name> [owner] | Preview a set in world 999 |
/usos <name> [owner] | Unload the streamed objects you loaded from a set |
/mysets [player] | List your sets, or someone else's |
/dpos <name> | Delete one of your sets |
/tpobs | Allow or stop others copying your objects and sets (on by default) |
A name that is already in use is never overwritten: pick a new name to save again.
Sets can also hold moving objects that slide from step to step and loop; /mol lists the streamed objects that move. Event and race maps load their own object sets automatically (see building-events and races).
| Command | What it does |
|---|---|
/sapo /spos /saveplayerobjectset | Save a player object set to the filename specified |
/smso /samso /smsos /savemystreamobjects /savemystreamedobjects /saveallmystreamobjects /saveallmystreamedobjects | Save all streamed objects they created to the flename specified |
/saso /ssos /saveallstreamobjects /savestreamobjectset | Save all streamed objects to the file specified |
/lpos /loadplayerobjectset | Load a player object set that has previously been saved |
/lsos /loadstreamobjectset /loadstreamedobjectset | Load a streamed object set from the filename supplied (if it exists) for streaming |
/psos /previewstreamedobjectset /previewstreamobjectset | Load a streamed object set from the filename supplied (if it exists) for streaming ONLY in Virtual World 999 |
/usos /unloadstreamobjectset /unloadstreamedobjectset | "unload" a streamed object set that was previously loaded |
/mysets /listsets /objectsets | - |
/dpos /deleteplayerobjectset | Delete a player object set file (it cannot be undeleted) |
/tpobs /togglepobsharing | Enable or disable sharing of their player objects |
/mol /movingobjectlist | View a list of all moving objects |
Object sets per area
San Fierro, the airports, Area 69 and every spawn can have their own object set. It loads only while someone is near and unloads a minute and a half after the last player leaves, so the server only holds what players can see. Hosts and Mappers manage them:
/mapareaslists the areas, their sets and whether they're loaded./setmaparea <set> <area>gives a set file an area (nonetakes it off: it then loads at every startup)./addmaparea <key> <size> [name]adds an area centred where you are;/deletemaparea <key>removes one.
Who made what
Every streamed object has its own number for good and remembers who made it, when, and, if it's a copy, which object it was duplicated from. This stays with it through saving, loading and map files. Loading someone else's set doesn't make its objects yours: the people who made them are kept, and what you add is yours.
/soinfo [number]: who made a streamed object (your selected one if you don't give a number), when, and what it was copied from./mapcredits [name]: how much each player made, as a table with each person's share and how many of theirs are copies. Give the name of a loaded map or a saved set; with no name it counts the streamed objects in your world.- GamerXServer or GamerXmp: everything from the original GamerX is marked GamerXServer: its map files and their objects, object sets, events, races, teleports, saved cars and properties. Everything made here is GamerXmp. An object a player copied over from a classic map still counts as GamerXServer's. In a map file saved in game, an object nobody can be named for shows as GamerXmp.
- Objects saved in a player's set before 2026-10-31 count as made by whoever saved the set, unless the classic has the same object at the same spot.
/ei <event>,/raceinfoand/teleinfosay where each one comes from, and the website's Files list shows it next to the maker.
| Command | What it does |
|---|---|
/objectinfo /soinfo /whomadeit | Who made a streamed object and when: /soinfo [streamed object number] (without a number: your selected one) |
/mapcredits /whomade /objectcredits | Who made the streamed objects in your world, or a server map's objects: /mapcredits [map name] |
Object editor
Most kinds of objects can be moved with the mouse editor (/epo, /eso, /evo) or with the overlay editor that has arrow buttons (/eso2, /eho2).