User Tools

Site Tools


dev:proposals:paintertool

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
dev:proposals:paintertool [2022-06-25 15:06]
blockhead Add my version of the proposal
dev:proposals:paintertool [2022-06-29 08:44] (current)
56independent Colour controller!
Line 80: Line 80:
  
 ... Further discussion to take place at the conference (soon TM) ... Further discussion to take place at the conference (soon TM)
 +
 +==== 56i's Proposal ====
 +I propose that first, we begin by copying the bikes tool to stop forcing people who wish to colour their trains to have to install another mod which is unrelated to what they want to do.
 +
 +Then, as time progresses, Blockhead's proposal is implemented.
 +
 +Then, as even more time progresses, all systems are merged into one:
 +
 +  * You have components for //all// trains (a single one for single-component trains), which is compatible with the Konstal.
 +  * You have presets, which are compatible with DLXtrains system
 +  * You have RGBA sliders, which are compatible with the E231 system.
 +
 +When these systems are merged, it makes future livery additions easier as they can fit with a paradigm instead of inventing their own.
 +
 +Below is a sketch of the formspec:
 +
 +{{:dev:proposals:56i_formspec.png|}}
 +
 +One can clearly see how it is arranged. The left controls the colour, the centre the component the colour is applied to (Listed are wheels, body and doors, but the specific components can change) and on the right some presets (pictured are those suitable for replicating the london underground). 
 +
 +Also, there is a save button which can save the livery to a slot, and adds the livery to presets.
 +
 +Any region can be greyed out or reduced to one item. For DLXtrains, maybe only the preset is enabled, and for the E231, only the Colour is applied.
 +
 +The method of applications are as such:
 +
 +^ Method ^ Description ^ Usecase ^
 +| ''/colour <train ID>'' command | brings up the formspec. Either owning the train or ''colour_train'' privelages are required to be able to run the command | Remotely changing an entire train's colour |
 +| Paintbrush | an inventory item which can be used to paint a train through right-clicking, saves between uses | For when you want to colour a specific carriage |
 +| Train right-click menu | As above, does not save | When you cannot use a paintbrush |
 +| LuaATC | A series of commands which let you do various editing | Automatically colouring trains |
 +
 +Also, and i know this is a stretch, but the livery painter should work on LuaATC controlling elements the same way it does to the E231. This helps prevent confusion with nearby LuaATC controlling elements.
 +
 +An API to change the colour of the LuaATC controller from within is also a good idea, which allows it to give live information on state (red means a train is now approaching a station, pink it has stopped, and red that a train is departing, and then blue when it has no control of a train ''event.ID == nil'').
dev/proposals/paintertool.1656162406.txt.gz · Last modified: 2022-06-25 15:06 by blockhead