Skip to content
This repository has been archived by the owner on Aug 21, 2023. It is now read-only.

vehicle chaining #941

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

Oricana-16
Copy link

About The Pull Request

Using a cable coil on a vehicle, then on another object (people structures etc) you can chain the object to the vehicle, making them get pulled (and tripped) when the vehicle moves.

Why It's Good For The Game

Could be used for very fun shenanigens, + uses a component for the connection, so we can use this for a lasso traitor item or something similar later in the future

Testing Photographs and Procedure

Screenshots&Videos

Demo Video
https://cdn.discordapp.com/attachments/1063182410033926196/1076948449121017986/2023-02-19_14-23-24.mp4

Changelog

🆑
add: Added vehicle chaining, use cable coil on a vehicle then on something else to drag it behind the vehicle. You can free someone by using help intent or wire cutters on them.
code: Added a chain component, which lets you make one atom/movable follow another
/:cl:

src.max_dist = max_dist
src.equal_force = equal_force

tether_beam = owner.Beam(target, "usb_cable_beam", 'icons/obj/wiremod.dmi')
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should probably use the maximum distance flag on this, unsure if it will help with the choppy beam, that will most likely require updating the beam on move

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

try calling tether_beam.recalculate() on movement to get it to redraw nicer

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tried this, it did make it better, it's jumping ahead instead of lagging behind, but it is a lot less choppy.

2023-02-19.22-19-17.mp4

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thats because of glide, without glide it would look fine how you'd solve this would be to make a recalculate proc that animates the beam from its old location to its new location based on the parents glidesize

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Im having trouble animating it since 1 beam made up of a bunch of smaller ebeams. even if I did get it to animate I think it would still be scuffed if the parts dont move perfectly. do you know of anywhere I could look at that has beams with animated movement like how we want it?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

okay yea that won't work looking at beam code now, hm this will have to do until we get something better than current beam code

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants