Skip to main content

RemoteComponent

RemoteComponent is a component extension that allows you to easily give networking capabilities to your components.

You can access the server-side component from the client by using the .Server index on the component. You can access the client-side component from the server by using the .Client index on the component.

Fast tagging and untagging

You can encounter issues if you untag and then retag again quickly or unparent and reparent to the same location on the server. This is because the server will rebuild the component, but the client will not recognize that there was a change as collectionservice wont think anything is different and their remotes can become desynced.

RemoteComponent Usage Limitations

Accessing .Server or .Client is only safe to do so once the client has completed its extension 'Starting' cycle and began its :Start() method

Yielding accidents

When using RemoteComponent, you must have both a client and server component. If you do not, then the client will yield until the server component is created. If only one side extends RemoteComponent, then you may encounter infinite yields.

Types​

RemoteComponent​

</>
interface RemoteComponent {
Client: table?--

Only availible on the server. Set this to a table to expose it to the client.

Server: table?--

Only availible on the client. The indices of this are inferred from the server.

}
-- MyComponentServer.lua
local MyComponent = Component.new {
	Tag = "MyComponent",
	Ancestors = {workspace},
	Extensions = {RemoteComponent},
}

MyComponent.Client = {
	TestProperty = NetWire.createProperty(0),
	TestSignal = NetWire.createEvent(),
}

function MyComponent.Client:TestMethod(player: Player)
	return ("Hello from the server!")
end

-- MyComponentClient.lua
local MyComponent = Component.new {
	Tag = "MyComponent",
	Ancestors = {workspace},
	Extensions = {RemoteComponent},
}

function MyComponent:Start()
	self.Server:TestMethod():andThen(print)
end
Show raw api
{
    "functions": [],
    "properties": [],
    "types": [
        {
            "name": "RemoteComponent",
            "desc": "```lua\n-- MyComponentServer.lua\nlocal MyComponent = Component.new {\n\tTag = \"MyComponent\",\n\tAncestors = {workspace},\n\tExtensions = {RemoteComponent},\n}\n\nMyComponent.Client = {\n\tTestProperty = NetWire.createProperty(0),\n\tTestSignal = NetWire.createEvent(),\n}\n\nfunction MyComponent.Client:TestMethod(player: Player)\n\treturn (\"Hello from the server!\")\nend\n```\n\n```lua\n-- MyComponentClient.lua\nlocal MyComponent = Component.new {\n\tTag = \"MyComponent\",\n\tAncestors = {workspace},\n\tExtensions = {RemoteComponent},\n}\n\nfunction MyComponent:Start()\n\tself.Server:TestMethod():andThen(print)\nend\n```",
            "fields": [
                {
                    "name": "Client",
                    "lua_type": "table?",
                    "desc": "Only availible on the server. Set this to a table to expose it to the client."
                },
                {
                    "name": "Server",
                    "lua_type": "table?",
                    "desc": "Only availible on the client. The indices of this are inferred from the server."
                }
            ],
            "source": {
                "line": 67,
                "path": "src/remotecomponent/src/RemoteComponent.lua"
            }
        }
    ],
    "name": "RemoteComponent",
    "desc": "RemoteComponent is a component extension that allows you to easily give\nnetworking capabilities to your components.\n\nYou can access the server-side component from the client by using the .Server index\non the component. You can access the client-side component from the server by using\nthe .Client index on the component.\n\n:::caution Fast tagging and untagging\nYou can encounter issues if you untag and then retag again quickly or unparent and\nreparent to the same location on the server. This is because the server will rebuild the\ncomponent, but the client will not recognize that there was a change as collectionservice\nwont think anything is different and their remotes can become desynced.\n:::\n\n:::caution RemoteComponent Usage Limitations\nAccessing `.Server` or `.Client` is only safe to do so once the client has completed its \nextension 'Starting' cycle and began its `:Start()` method\n:::\n\n:::caution Yielding accidents\nWhen using RemoteComponent, you *must* have both a client and server component. If you do not,\nthen the client will yield until the server component is created. If only one side extends RemoteComponent,\nthen you may encounter infinite yields.\n:::",
    "source": {
        "line": 29,
        "path": "src/remotecomponent/src/RemoteComponent.lua"
    }
}