User talk:Hearmeout

BNDEP MAN Buses

Do you have any proof that SMB3043S perms 23, and that the 3 A95 batch 2s are all perm 168? For the record, when you put SG5761S as 168 perm on Sunday, that bus hasn’t even done 168 yet. Also, these buses have not done the services mentioned that frequently to be considered perms yet.

AirFan19

Reply from my talk page

Blud, these buses are still interchangeable. Take 184 and 302 bendy buses, I have seen those perm bendy buses doing 302 and not 184 on some days. Also 176 perm buses still doing 190. So do not undo those edits again unless you show evidence

RobloxXF

Reply

Hi,

Regarding the ads, most ad are really duplicate between various model, so if really wants for legacy sake, I am ok for a page to consolidate all the ads section.

In the past wiki going against the idea of creating individual pages quite a long time ago is because of

1. The former deployment is mainly fixed deployment → Bus fan community would rather keep it simple for their own recording needs
2. There is lots of administrative member helping to ensure correctness and following rules.

But with the lacks of admins, and lots of rouge editor, many conflict do happens in pages reverting quite often between to and fro, especially with the rego and change of bus fleet.

Alternative, there is a clause in the rule that say: Only create if there are meaningful meaning in creating those page, which is why I decided to roll in, and include more meaningful page like a service guide instead for general public, therefore reducing the need of frequent update. (Somemore if there is something wrong or rouge editor is quite obvious)

Please feel free to experiment with the ideas and concept you have.

Regards

Since Columns

Hi,

I was wondering why you remove the 'since column'? My understand for putting that in is so that it is easier for editor to transfer to former deployment as it a record for first deployment rather than finding the history.

Re:

I am ok. Just thinking how can we better improve it. Because the since is to indicate the month/year from last change/deployment for easier reference.

As for the order, I believed there are some feedback regarding merge columns position which result in harder to track deployment.

Shall we try this order: Operator -> Registration -> Current Deployment -> Livery (if any) -> Former Deployment.