Split cargo shuttle to its own component (#23926)
* Split cargo shuttle to its own component If mappers want 1 morbillion of them this is easier to manage. * balls
This commit is contained in:
@@ -0,0 +1,19 @@
|
||||
using Robust.Shared.Utility;
|
||||
|
||||
namespace Content.Server.Shuttles.Components;
|
||||
|
||||
/// <summary>
|
||||
/// GridSpawnComponent but for cargo shuttles
|
||||
/// <remarks>
|
||||
/// This exists so we don't need to make 1 change to GridSpawn for every single station's unique shuttles.
|
||||
/// </remarks>
|
||||
/// </summary>
|
||||
[RegisterComponent]
|
||||
public sealed partial class StationCargoShuttleComponent : Component
|
||||
{
|
||||
// If you add more than just make an abstract comp, split them, then use overloads in the system.
|
||||
// YAML is filled out so mappers don't have to read here.
|
||||
|
||||
[DataField(required: true)]
|
||||
public ResPath Path = new("/Maps/Shuttles/cargo.yml");
|
||||
}
|
||||
Reference in New Issue
Block a user