User talk:Thespotter

!	Warning Point (6 March 2025)					!
	You have committed the follow offense that may warrant an immediate ban: Disruptive Editing Please edit properly for the change in deployment by (1) updating the Bus Deployments by Model for both current and former deployments, (2) respective service page for both current and former pages. If you are updating because you spotted the bus and not due to a change in deployment, please use the respective bus spotting page instead. If you believe that the bus is just a cameo or possible deployment change, with no concrete evidence, please use the respective bus spotting page instead. To differentiate between a permanent and a cameo, please observe the deployment of the bus over a period of 1 week (minimum), as bus may be redeployed away from it perm service due to maintenance schedule. Your edit are being reverted due to failure to update former deployment.

!	Warning Point (11 March 2025)					!
	You have committed the follow offense that may warrant an immediate ban: Disruptive Editing Please edit properly for the change in deployment by (1) updating the Bus Deployments by Model for both current and former deployments, (2) respective service page for both current and former pages. If you are updating because you spotted the bus and not due to a change in deployment, please use the respective bus spotting page instead. If you believe that the bus is just a cameo or possible deployment change, with no concrete evidence, please use the respective bus spotting page instead. To differentiate between a permanent and a cameo, please observe the deployment of the bus over a period of 1 week (minimum), as bus may be redeployed away from it perm service due to maintenance schedule. Your edit are being reverted due to failure to update former deployment.

Edit warring

You currently appear to be engaged in an edit war. This means that you are repeatedly changing content back to how you think it should be although other editors disagree. Users are expected to collaborate with others, to avoid editing disruptively, and to try to reach a consensus, rather than repeatedly undoing other users' edits once it is known that there is a disagreement.

Points to note:

Edit warring is disruptive regardless of how many reverts you have made

Do not edit war even if you believe you are right.

If you find yourself in an editing dispute, use the article's talk page to discuss controversial changes and work towards a version that represents consensus among editors. You can post a request for help at an appropriate noticeboard or seek dispute resolution. In some cases, it may be appropriate to request temporary page protection. If you engage in an edit war, you may be blocked from editing.

Your recent editing history shows that you are currently engaged in an edit war; that means that you are repeatedly changing content back to how you think it should be, when you have seen that other editors disagree. To resolve the content dispute, please do not revert or change the edits of others when you are reverted. Instead of reverting, please use the talk page to work toward making a version that represents consensus among editors. The best practice at this stage is to discuss, not edit-war; read about how this is done. If discussions reach an impasse, you can then post a request for help at a relevant noticeboard or seek dispute resolution. In some cases, you may wish to request temporary page protection.

Being involved in an edit war can result in you being blocked from editing—especially if you violate the three-revert rule, which states that an editor must not perform more than three reverts on a single page within a 24-hour period. Undoing another editor's work—whether in whole or in part, whether involving the same or different material each time—counts as a revert. Also keep in mind that while violating the three-revert rule often leads to a block, you can still be blocked for edit warring—even if you do not violate the three-revert rule—should your behavior indicate that you intend to continue reverting repeatedly.

Former Deployment

Your edits are being reverted due to (1) Failure to edit all relevant pages, (2) Never update former deployment

Alternative, take note of this new table:

Depot	Fleet Size	Fleet
Singapore Depot (SGDEP)	20	8 Single Deckers	10 Double Deckers	2 Articulated
		SG1900J SG1901G SD Model 1 SD Model 2	SG6800G SG6801D SG6802B SG6803Z SG6804X SG6805T SG6806R DD Model 1	SG8000K SG8001H BD Model 1

CollapseNotes
6 missing SD.

This table tell the following deployment for this service:

1. There is 2 perm SD Model 1 buses
2. There is missing perm buses for SD Model 1 and SD Model 2
3. There is 7 perm DD Model 1 buses, and 3 DD Model 1 buses that operates in flexi-deployment
4. There is 2 perm BD Model 1 buses
5. The duty size is 20 buses, with 8 SD buses slot, 10 DD buses slot, and 2 BD buses slot (and not there is 8 perm SD, 10 perm DD, 2 perm BD)

Regarding your edit

I am sure Supernutorcrazy already talked to you about your edits. Because of that, you did not see there is a former deployment table on the right-end side. You can use that to update what was formerly permed by typing the following "[PERM SERVICE] ([Month Year - Month Year])" this can solve you.

I am curious about why you always dont want to update relevant pages, so take a look at the perm service page, you can see a there is a rego in that service table? When it changed perm, remove that rego from the perm table and add it to a new service table. If you do not understand, refer to the table on top.

Thanks

Alphabetlorefan1 (talk) 11 March 2025, 11:25