'Stations'
Posted: Sun Mar 15, 2015 6:36 am
The current way of making a station is with the use of inserter's to input/output items from wagons. Whilst this is effective and does work - it can be rather tedious when setting up all the inserter's and whatnot for your loading/unloading point.
My suggestion is for an actual entity of a 'station' that is the same length as a wagon (I believe wagons are different sizes depending on horizontal/vertical so maybe two versions of the station?). This would remove the need for complex loading/unloading points. As well as this most station setups currently have something along the lines of: Belt > Inserter > Chest > Inserter > Wagon, where the chest is used as a buffer. This could be simplified by having the 'station' entity have an internal inventory.
I am no coding genius but this solution may even increase performance since I figure there would only be one entity interacting with the wagon rather than 5-6, someone with a bit more knowledge care to educate me on whether this is the case?
Overall I believe having this 'station' entity will make it a lot easier to set up large rail networks with multiple stops.
My suggestion is for an actual entity of a 'station' that is the same length as a wagon (I believe wagons are different sizes depending on horizontal/vertical so maybe two versions of the station?). This would remove the need for complex loading/unloading points. As well as this most station setups currently have something along the lines of: Belt > Inserter > Chest > Inserter > Wagon, where the chest is used as a buffer. This could be simplified by having the 'station' entity have an internal inventory.
I am no coding genius but this solution may even increase performance since I figure there would only be one entity interacting with the wagon rather than 5-6, someone with a bit more knowledge care to educate me on whether this is the case?
Overall I believe having this 'station' entity will make it a lot easier to set up large rail networks with multiple stops.