> For the complete documentation index, see [llms.txt](https://wiki.thescriptersguild.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.thescriptersguild.com/community/content/assets-and-kits/conveyor-belt-push.md). # Conveyor Belt Push

Creating conveyor belt movement that effectively interacts with players and physics objects can be difficult, as standard translation methods may not provide the necessary physical interaction required for gameplay. ## Implementation Methods ### Segmented Belt Script A highly effective approach involves a segmented belt script that uses a spawn mode object node. This method is preferred because it allows the conveyor to maintain custom textures easily while moving segments along a predefined path. To maintain performance and prevent object buildup, a deletion zone should be placed at the end of the belt to remove segments once they reach their destination.

Node graph — The revised belt script utilizes spawned segments and a deletion zone at the end.

{% hint style="info" %} Using the spawn mode object node allows the conveyor to preserve custom textures more effectively than other movement methods. {% endhint %} ### Physics-based Conveyor Belts Using the normal physics option on a conveyor belt allows for native physics interactions, such as moving players or physics crates placed on the surface.

Gameplay — A player navigates a conveyor belt system.

This method introduces specific movement dynamics: * Players run faster when moving in the same direction as the belt. * Players run slower when moving against the direction of the belt. * Stationary players being moved by the belt might not appear on radar. {% hint style="warning" %} Spawning multiple physics objects closely together in a constrained space may lead to instability; spawning objects individually and moving them one at a time can result in more reliable behavior. {% endhint %} ### Translation and Position Nodes The [Translate Object To Point](/scripting/nodes/objects-transform/translate-object-to-point.md) node can be used to move objects, though players cannot walk against the direction of movement or jump out of the affected area. Additionally, all objects within the area monitor are subject to this movement. To prevent non-player objects from being moved, a [Get Is Player](/scripting/nodes/players/get-is-player.md) node can be used to verify the identity of objects within the area monitor.

Alternatively, moving both the conveyor belt and the player simultaneously using `Set Position` can create an illusion of continuous movement. However, `Set Position` functions as a teleportation rather than a continuous translation over time. *** ## Source Data * Discord thread: [Conveyor Belt Push](https://discord.com/channels/220766496635224065/1048495100042416218/1048495100042416218) #### Contributors Koma\ TheProgrammer163\ Okom\ green --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://wiki.thescriptersguild.com/community/content/assets-and-kits/conveyor-belt-push.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.