Talk:JavaScript - Revision history

Jonesey95: rm gibberish

2025-05-31T12:41:54Z

rm gibberish

← Previous revision		Revision as of 12:41, 31 May 2025
Line 122:		Line 122:
	Alternatively, remove "Features > Promises and Async/await" altogether, as it is already covered by the following two entries (Promises, Async/await) [[User:Lunamason\|Lunamason]] ([[User talk:Lunamason\|talk]]) 01:53, 30 May 2025 (UTC)		Alternatively, remove "Features > Promises and Async/await" altogether, as it is already covered by the following two entries (Promises, Async/await) [[User:Lunamason\|Lunamason]] ([[User talk:Lunamason\|talk]]) 01:53, 30 May 2025 (UTC)
	:{{done}}<!-- Template:ESp --> I opted for your second suggestion. [[User:DrOrinScrivello\|DrOrinScrivello]] ([[User talk:DrOrinScrivello\|talk]]) 18:14, 30 May 2025 (UTC)		:{{done}}<!-- Template:ESp --> I opted for your second suggestion. [[User:DrOrinScrivello\|DrOrinScrivello]] ([[User talk:DrOrinScrivello\|talk]]) 18:14, 30 May 2025 (UTC)

	== Semi-protected edit request on 31 May 2025 ==

	{{edit semi-protected\|JavaScript\|answered=no}}
	[[Special:Contributions/41.76.172.24\|41.76.172.24]] ([[User talk:41.76.172.24\|talk]]) 11:47, 31 May 2025 (UTC)
	<small><big>Small text</big></small><sub>
	<gallery>
	Subscript text
	</gallery>
	#REDIRECT [[<br>
	Target page name]]
	</sub>Brian.cc

	== Semi-protected edttttit request on 31 May 2025 ==

	<big><small>Big text</small></big>{{edit semi-protected\|JavaScript\|answered=no}}
	<small><sub>Small text</sub>
	<gallery>
	* Example.jpg\|Caption1
	* Exa
	=====
	===== Heading text =====
	=====
	===== Heading text =====
	″≈ =====
	=====
	mple.jpg\|Caption2
	</gallery>
	</small> [[Special:Contributions/41.76.172.24\|41.76.172.24]] ([[User talk:41.76.172.24\|talk]]) 11:51, 31 May 2025 (UTC)<code>hp</code>
	<nowiki>
	===== Insert non-formatted text here =====
	=====
	===== Heading text =====
	===== Heading text =====
	=====
	</nowiki>

41.76.172.24: /* Semi-protected edttttit request on 31 May 2025 */ new section

2025-05-31T11:51:48Z

Semi-protected edttttit request on 31 May 2025: new section

← Previous revision		Revision as of 11:51, 31 May 2025
Line 134:		Line 134:
	Target page name]]		Target page name]]
	</sub>Brian.cc		</sub>Brian.cc

			== Semi-protected edttttit request on 31 May 2025 ==

			<big><small>Big text</small></big>{{edit semi-protected\|JavaScript\|answered=no}}
			<small><sub>Small text</sub>
			<gallery>
			* Example.jpg\|Caption1
			* Exa
			=====
			===== Heading text =====
			=====
			===== Heading text =====
			″≈ =====
			=====
			mple.jpg\|Caption2
			</gallery>
			</small> [[Special:Contributions/41.76.172.24\|41.76.172.24]] ([[User talk:41.76.172.24\|talk]]) 11:51, 31 May 2025 (UTC)<code>hp</code>
			<nowiki>
			===== Insert non-formatted text here =====
			=====
			===== Heading text =====
			===== Heading text =====
			=====
			</nowiki>

41.76.172.24: /* Semi-protected edit request on 31 May 2025 */ new section

2025-05-31T11:47:09Z

Semi-protected edit request on 31 May 2025: new section

← Previous revision		Revision as of 11:47, 31 May 2025
Line 122:		Line 122:
	Alternatively, remove "Features > Promises and Async/await" altogether, as it is already covered by the following two entries (Promises, Async/await) [[User:Lunamason\|Lunamason]] ([[User talk:Lunamason\|talk]]) 01:53, 30 May 2025 (UTC)		Alternatively, remove "Features > Promises and Async/await" altogether, as it is already covered by the following two entries (Promises, Async/await) [[User:Lunamason\|Lunamason]] ([[User talk:Lunamason\|talk]]) 01:53, 30 May 2025 (UTC)
	:{{done}}<!-- Template:ESp --> I opted for your second suggestion. [[User:DrOrinScrivello\|DrOrinScrivello]] ([[User talk:DrOrinScrivello\|talk]]) 18:14, 30 May 2025 (UTC)		:{{done}}<!-- Template:ESp --> I opted for your second suggestion. [[User:DrOrinScrivello\|DrOrinScrivello]] ([[User talk:DrOrinScrivello\|talk]]) 18:14, 30 May 2025 (UTC)

			== Semi-protected edit request on 31 May 2025 ==

			{{edit semi-protected\|JavaScript\|answered=no}}
			[[Special:Contributions/41.76.172.24\|41.76.172.24]] ([[User talk:41.76.172.24\|talk]]) 11:47, 31 May 2025 (UTC)
			<small><big>Small text</big></small><sub>
			<gallery>
			Subscript text
			</gallery>
			#REDIRECT [[<br>
			Target page name]]
			</sub>Brian.cc

DrOrinScrivello: /* Semi-protected edit request on 30 May 2025 */ answering edit request

2025-05-30T18:14:49Z

Semi-protected edit request on 30 May 2025: answering edit request

← Previous revision		Revision as of 18:14, 30 May 2025
Line 117:		Line 117:
	== Semi-protected edit request on 30 May 2025 ==		== Semi-protected edit request on 30 May 2025 ==

	{{edit semi-protected\|JavaScript\|answered=no}}		{{edit semi-protected\|JavaScript\|answered=y}}
	Add https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise as the missing citation under Features > Promises and Async/await.		Add https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise as the missing citation under Features > Promises and Async/await.

	Alternatively, remove "Features > Promises and Async/await" altogether, as it is already covered by the following two entries (Promises, Async/await) [[User:Lunamason\|Lunamason]] ([[User talk:Lunamason\|talk]]) 01:53, 30 May 2025 (UTC)		Alternatively, remove "Features > Promises and Async/await" altogether, as it is already covered by the following two entries (Promises, Async/await) [[User:Lunamason\|Lunamason]] ([[User talk:Lunamason\|talk]]) 01:53, 30 May 2025 (UTC)
			:{{done}}<!-- Template:ESp --> I opted for your second suggestion. [[User:DrOrinScrivello\|DrOrinScrivello]] ([[User talk:DrOrinScrivello\|talk]]) 18:14, 30 May 2025 (UTC)

Lunamason: /* Semi-protected edit request on 30 May 2025 */ new section

2025-05-30T01:53:43Z

Semi-protected edit request on 30 May 2025: new section

← Previous revision		Revision as of 01:53, 30 May 2025
Line 114:		Line 114:
	:::He just stopped replying to the newer better suggestions.		:::He just stopped replying to the newer better suggestions.
	:::This is just a game of frustrating people. [[Special:Contributions/2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42\|2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42]] ([[User talk:2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42\|talk]]) 12:21, 8 April 2025 (UTC)		:::This is just a game of frustrating people. [[Special:Contributions/2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42\|2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42]] ([[User talk:2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42\|talk]]) 12:21, 8 April 2025 (UTC)

			== Semi-protected edit request on 30 May 2025 ==

			{{edit semi-protected\|JavaScript\|answered=no}}
			Add https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise as the missing citation under Features > Promises and Async/await.

			Alternatively, remove "Features > Promises and Async/await" altogether, as it is already covered by the following two entries (Promises, Async/await) [[User:Lunamason\|Lunamason]] ([[User talk:Lunamason\|talk]]) 01:53, 30 May 2025 (UTC)

MrOllie: Reverted 1 edit by 2405:3800:832:89DF:8AC3:FF9C:AE2B:E564 (talk) to last revision by MrOllie

2025-05-08T01:32:52Z

Reverted 1 edit by 2405:3800:832:89DF:8AC3:FF9C:AE2B:E564 (talk) to last revision by MrOllie

← Previous revision		Revision as of 01:32, 8 May 2025
Line 114:		Line 114:
	:::He just stopped replying to the newer better suggestions.		:::He just stopped replying to the newer better suggestions.
	:::This is just a game of frustrating people. [[Special:Contributions/2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42\|2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42]] ([[User talk:2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42\|talk]]) 12:21, 8 April 2025 (UTC)		:::This is just a game of frustrating people. [[Special:Contributions/2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42\|2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42]] ([[User talk:2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42\|talk]]) 12:21, 8 April 2025 (UTC)

	== Love Animation ==

	.heart { fill:red; position:relative; top:5px; width:50px; animation: pulse 1 s ease infinite; #heart { position: relative;width:100px; height:90px; text-align:center; font-size:16px; @keyframes pulse { 0% {transform:scale(1);} 50% {transform：scale(1.3);} 100% {transform:scale(1);} } [[Special:Contributions/2405:3800:832:89DF:8AC3:FF9C:AE2B:E564\|2405:3800:832:89DF:8AC3:FF9C:AE2B:E564]] ([[User talk:2405:3800:832:89DF:8AC3:FF9C:AE2B:E564\|talk]]) 01:06, 8 May 2025 (UTC)

2405:3800:832:89DF:8AC3:FF9C:AE2B:E564: /* Love Animation */ new section

2025-05-08T01:06:20Z

Love Animation: new section

← Previous revision		Revision as of 01:06, 8 May 2025
Line 114:		Line 114:
	:::He just stopped replying to the newer better suggestions.		:::He just stopped replying to the newer better suggestions.
	:::This is just a game of frustrating people. [[Special:Contributions/2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42\|2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42]] ([[User talk:2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42\|talk]]) 12:21, 8 April 2025 (UTC)		:::This is just a game of frustrating people. [[Special:Contributions/2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42\|2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42]] ([[User talk:2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42\|talk]]) 12:21, 8 April 2025 (UTC)

			== Love Animation ==

			.heart { fill:red; position:relative; top:5px; width:50px; animation: pulse 1 s ease infinite; #heart { position: relative;width:100px; height:90px; text-align:center; font-size:16px; @keyframes pulse { 0% {transform:scale(1);} 50% {transform：scale(1.3);} 100% {transform:scale(1);} } [[Special:Contributions/2405:3800:832:89DF:8AC3:FF9C:AE2B:E564\|2405:3800:832:89DF:8AC3:FF9C:AE2B:E564]] ([[User talk:2405:3800:832:89DF:8AC3:FF9C:AE2B:E564\|talk]]) 01:06, 8 May 2025 (UTC)

MrOllie: Restored revision 1284564664 by 2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42 (talk)

2025-04-14T19:42:29Z

Restored revision 1284564664 by 2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42 (talk)

← Previous revision		Revision as of 19:42, 14 April 2025
Line 114:		Line 114:
	:::He just stopped replying to the newer better suggestions.		:::He just stopped replying to the newer better suggestions.
	:::This is just a game of frustrating people. [[Special:Contributions/2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42\|2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42]] ([[User talk:2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42\|talk]]) 12:21, 8 April 2025 (UTC)		:::This is just a game of frustrating people. [[Special:Contributions/2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42\|2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42]] ([[User talk:2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42\|talk]]) 12:21, 8 April 2025 (UTC)

	== Creating a runner game involves several key components, including game mechanics, graphics, and user input handling. Here's a basic outline to help you get started: --- 🛠️ Game Components 1. Player Character: Movement: Implement continuous forward movement and allow the player to control jumping or crouching. Physics: Apply gravity to simulate realistic movement. 2. Obstacles: Generation: Randomly spawn obstacles at varying intervals. Collision Detection: Detect collisions between the player and obstacles to trigger game-over conditions. 3. Scoring System: Distance-Based Scoring: Award points based on the distance traveled. High Score Tracking: Keep track of the highest score achieved. 4. Game Loop: Update: Continuously update game elements (player position, obstacles, score). Render: Draw updated elements to the screen. Input Handling: Respond to user inputs (e.g., jump, crouch). --- 💻 Sample Code Snippets Java (Using JavaFX) // Initialize player and obstacles Player player = new Player(100, 500); List<Obstacle> obstacles = new ArrayList<>(); // Game loop AnimationTimer gameLoop = new AnimationTimer() { @Override public void handle(long now) { updateGame(); render(); } }; // Update game elements private void updateGame() { player.update(); for (Obstacle obstacle : obstacles) { obstacle.update(); if (obstacle.collidesWith(player)) { // Handle collision } } obstacles.removeIf(obstacle -> obstacle.getX() < -100); } // Render game elements private void render() { gc.clearRect(0, 0, canvas.getWidth(), canvas.getHeight()); player.render(gc); for (Obstacle obstacle : obstacles) { obstacle.render(gc); } } For a detailed guide on building an endless runner game in Java, refer to this tutorial: HTML5/JavaScript (Using Phaser Framework) // Initialize Phaser game const config = { type: Phaser.AUTO, width: 800, height: 600, scene: { preload: preload, create: create, update: update } }; const game = new Phaser.Game(config); function preload() { // Load assets } function create() { // Set up player and obstacles } function update() { // Update game elements } For a comprehensive example using Phaser, check out this project: --- 📚 Additional Resources Unity 2D Endless Runner Course: A complete course to create an endless runner game in Unity. Unreal Engine C++ Tutorial: Learn to code an endless runner game using Unreal Engine and C++. --- If you need more detailed code examples or assistance with a specific aspect of game development, feel free to ask! ==

	Creating a runner game involves several key components, including game mechanics, graphics, and user input handling. Here's a basic outline to help you get started:
	🛠️ Game Components
	1. Player Character:
	Movement: Implement continuous forward movement and allow the player to control jumping or crouching.
	Physics: Apply gravity to simulate realistic movement.
	2. Obstacles:
	Generation: Randomly spawn obstacles at varying intervals.
	Collision Detection: Detect collisions between the player and obstacles to trigger game-over conditions.
	3. Scoring System:
	Distance-Based Scoring: Award points based on the distance traveled.
	High Score Tracking: Keep track of the highest score achieved.
	4. Game Loop:
	Update: Continuously update game elements (player position, obstacles, score).
	Render: Draw updated elements to the screen.
	Input Handling: Respond to user inputs (e.g., jump, crouch).
	💻 Sample Code Snippets
	Java (Using JavaFX)
	// Initialize player and obstacles
	Player player = new Player(100, 500);
	List<Obstacle> obstacles = new ArrayList<>();

	// Game loop
	AnimationTimer gameLoop = new AnimationTimer() {
	@Override
	public void handle(long now) {
	updateGame();
	render();
	}
	};

	// Update game elements
	private void updateGame() {
	player.update();
	for (Obstacle obstacle : obstacles) {
	obstacle.update();
	if (obstacle.collidesWith(player)) {
	// Handle collision
	}
	}
	obstacles.removeIf(obstacle -> obstacle.getX() < -100);
	}

	// Render game elements
	private void render() {
	gc.clearRect(0, 0, canvas.getWidth(), canvas.getHeight());
	player.render(gc);
	for (Obstacle obstacle : obstacles) {
	obstacle.render(gc);
	}
	}

	For a detailed guide on building an endless runner game in Java, refer to this tutorial:
	HTML5/JavaScript (Using Phaser Framework)
	// Initialize Phaser game
	const config = {
	type: Phaser.AUTO,
	width: 800,
	height: 600,
	scene: {
	preload: preload,
	create: create,
	update: update
	}
	};

	const game = new Phaser.Game(config);

	function preload() {
	// Load assets
	}

	function create() {
	// Set up player and obstacles
	}

	function update() {
	// Update game elements
	}

	For a comprehensive example using Phaser, check out this project:
	📚 Additional Resources
	Unity 2D Endless Runner Course: A complete course to create an endless runner game in Unity.
	Unreal Engine C++ Tutorial: Learn to code an endless runner game using Unreal Engine and C++.
	If you need more detailed code examples or assistance with a specific aspect of game development, feel free to ask! [[Special:Contributions/37.111.158.202\|37.111.158.202]] ([[User talk:37.111.158.202\|talk]]) 19:34, 14 April 2025 (UTC)

37.111.158.202: /* Creating a runner game involves several key components, including game mechanics, graphics, and user input handling. Here's a basic outline to help you get started: --- 🛠️ Game Components 1. Player Character: Movement: Implement continuous forward movement and allow the player to control jumping or crouching. Physics: Apply gravity to simulate realistic movement. 2. Obstacles: Generation: Randomly spawn obstacles at varying intervals. Collision Detection: Detect collisions between the play...

2025-04-14T19:34:59Z

/* Creating a runner game involves several key components, including game mechanics, graphics, and user input handling. Here's a basic outline to help you get started: --- 🛠️ Game Components 1. Player Character: Movement: Implement continuous forward movement and allow the player to control jumping or crouching. Physics: Apply gravity to simulate realistic movement. 2. Obstacles: Generation: Randomly spawn obstacles at varying intervals. Collision Detection: Detect collisions between the play...

← Previous revision		Revision as of 19:34, 14 April 2025
Line 114:		Line 114:
	:::He just stopped replying to the newer better suggestions.		:::He just stopped replying to the newer better suggestions.
	:::This is just a game of frustrating people. [[Special:Contributions/2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42\|2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42]] ([[User talk:2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42\|talk]]) 12:21, 8 April 2025 (UTC)		:::This is just a game of frustrating people. [[Special:Contributions/2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42\|2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42]] ([[User talk:2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42\|talk]]) 12:21, 8 April 2025 (UTC)

			== Creating a runner game involves several key components, including game mechanics, graphics, and user input handling. Here's a basic outline to help you get started: --- 🛠️ Game Components 1. Player Character: Movement: Implement continuous forward movement and allow the player to control jumping or crouching. Physics: Apply gravity to simulate realistic movement. 2. Obstacles: Generation: Randomly spawn obstacles at varying intervals. Collision Detection: Detect collisions between the player and obstacles to trigger game-over conditions. 3. Scoring System: Distance-Based Scoring: Award points based on the distance traveled. High Score Tracking: Keep track of the highest score achieved. 4. Game Loop: Update: Continuously update game elements (player position, obstacles, score). Render: Draw updated elements to the screen. Input Handling: Respond to user inputs (e.g., jump, crouch). --- 💻 Sample Code Snippets Java (Using JavaFX) // Initialize player and obstacles Player player = new Player(100, 500); List<Obstacle> obstacles = new ArrayList<>(); // Game loop AnimationTimer gameLoop = new AnimationTimer() { @Override public void handle(long now) { updateGame(); render(); } }; // Update game elements private void updateGame() { player.update(); for (Obstacle obstacle : obstacles) { obstacle.update(); if (obstacle.collidesWith(player)) { // Handle collision } } obstacles.removeIf(obstacle -> obstacle.getX() < -100); } // Render game elements private void render() { gc.clearRect(0, 0, canvas.getWidth(), canvas.getHeight()); player.render(gc); for (Obstacle obstacle : obstacles) { obstacle.render(gc); } } For a detailed guide on building an endless runner game in Java, refer to this tutorial: HTML5/JavaScript (Using Phaser Framework) // Initialize Phaser game const config = { type: Phaser.AUTO, width: 800, height: 600, scene: { preload: preload, create: create, update: update } }; const game = new Phaser.Game(config); function preload() { // Load assets } function create() { // Set up player and obstacles } function update() { // Update game elements } For a comprehensive example using Phaser, check out this project: --- 📚 Additional Resources Unity 2D Endless Runner Course: A complete course to create an endless runner game in Unity. Unreal Engine C++ Tutorial: Learn to code an endless runner game using Unreal Engine and C++. --- If you need more detailed code examples or assistance with a specific aspect of game development, feel free to ask! ==

			Creating a runner game involves several key components, including game mechanics, graphics, and user input handling. Here's a basic outline to help you get started:
			🛠️ Game Components
			1. Player Character:
			Movement: Implement continuous forward movement and allow the player to control jumping or crouching.
			Physics: Apply gravity to simulate realistic movement.
			2. Obstacles:
			Generation: Randomly spawn obstacles at varying intervals.
			Collision Detection: Detect collisions between the player and obstacles to trigger game-over conditions.
			3. Scoring System:
			Distance-Based Scoring: Award points based on the distance traveled.
			High Score Tracking: Keep track of the highest score achieved.
			4. Game Loop:
			Update: Continuously update game elements (player position, obstacles, score).
			Render: Draw updated elements to the screen.
			Input Handling: Respond to user inputs (e.g., jump, crouch).
			💻 Sample Code Snippets
			Java (Using JavaFX)
			// Initialize player and obstacles
			Player player = new Player(100, 500);
			List<Obstacle> obstacles = new ArrayList<>();

			// Game loop
			AnimationTimer gameLoop = new AnimationTimer() {
			@Override
			public void handle(long now) {
			updateGame();
			render();
			}
			};

			// Update game elements
			private void updateGame() {
			player.update();
			for (Obstacle obstacle : obstacles) {
			obstacle.update();
			if (obstacle.collidesWith(player)) {
			// Handle collision
			}
			}
			obstacles.removeIf(obstacle -> obstacle.getX() < -100);
			}

			// Render game elements
			private void render() {
			gc.clearRect(0, 0, canvas.getWidth(), canvas.getHeight());
			player.render(gc);
			for (Obstacle obstacle : obstacles) {
			obstacle.render(gc);
			}
			}

			For a detailed guide on building an endless runner game in Java, refer to this tutorial:
			HTML5/JavaScript (Using Phaser Framework)
			// Initialize Phaser game
			const config = {
			type: Phaser.AUTO,
			width: 800,
			height: 600,
			scene: {
			preload: preload,
			create: create,
			update: update
			}
			};

			const game = new Phaser.Game(config);

			function preload() {
			// Load assets
			}

			function create() {
			// Set up player and obstacles
			}

			function update() {
			// Update game elements
			}

			For a comprehensive example using Phaser, check out this project:
			📚 Additional Resources
			Unity 2D Endless Runner Course: A complete course to create an endless runner game in Unity.
			Unreal Engine C++ Tutorial: Learn to code an endless runner game using Unreal Engine and C++.
			If you need more detailed code examples or assistance with a specific aspect of game development, feel free to ask! [[Special:Contributions/37.111.158.202\|37.111.158.202]] ([[User talk:37.111.158.202\|talk]]) 19:34, 14 April 2025 (UTC)

2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42: /* Semi-protected edit request on 29 March 2025 */ Reply

2025-04-08T12:21:30Z

Semi-protected edit request on 29 March 2025: Reply

← Previous revision		Revision as of 12:21, 8 April 2025
Line 112:		Line 112:
	:Please explain how this can be controversial! [[Special:Contributions/2A00:FBC:E1FB:13BD:158B:C9C3:CD94:6E6D\|2A00:FBC:E1FB:13BD:158B:C9C3:CD94:6E6D]] ([[User talk:2A00:FBC:E1FB:13BD:158B:C9C3:CD94:6E6D\|talk]]) 11:07, 4 April 2025 (UTC)		:Please explain how this can be controversial! [[Special:Contributions/2A00:FBC:E1FB:13BD:158B:C9C3:CD94:6E6D\|2A00:FBC:E1FB:13BD:158B:C9C3:CD94:6E6D]] ([[User talk:2A00:FBC:E1FB:13BD:158B:C9C3:CD94:6E6D\|talk]]) 11:07, 4 April 2025 (UTC)
	::Sure - the policy is found at [[WP:SUNS]]. The relevant bit is that editors should respond to "either uncontroversial improvements (correcting typos, grammar, or reference formatting; improving the reliability or efficiency of template code) or are already supported by a consensus of editors, usually on the protected page's talk page." Since you have at least one editor disagreeing, it's not obviously a consensus opeion yet. [[User:PianoDan\|PianoDan]] ([[User talk:PianoDan\|talk]]) 16:20, 5 April 2025 (UTC)		::Sure - the policy is found at [[WP:SUNS]]. The relevant bit is that editors should respond to "either uncontroversial improvements (correcting typos, grammar, or reference formatting; improving the reliability or efficiency of template code) or are already supported by a consensus of editors, usually on the protected page's talk page." Since you have at least one editor disagreeing, it's not obviously a consensus opeion yet. [[User:PianoDan\|PianoDan]] ([[User talk:PianoDan\|talk]]) 16:20, 5 April 2025 (UTC)
			:::He just stopped replying to the newer better suggestions.
			:::This is just a game of frustrating people. [[Special:Contributions/2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42\|2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42]] ([[User talk:2A00:FBC:EAD3:EB97:F83E:310C:4505:5E42\|talk]]) 12:21, 8 April 2025 (UTC)