Difference between revisions of "User talk:Purplemana"
Purplemana (talk | contribs) |
GrampaSwood (talk | contribs) (→Medic bug: new section) |
||
(One intermediate revision by the same user not shown) | |||
Line 64: | Line 64: | ||
− | I've had this happen when trying to edit this wiki before. I just don't understand why people are so opposed to making useful information obvious in the first paragraphs of the weapon's intro. Like, do you think that "the equializer can 2 shot most buildings at low health" is more important than "the equalizer has a massive, unlisted downside"? Why even have an intro if the weapon chart already explains almost everything about the weapon? | + | ::::::I've had this happen when trying to edit this wiki before. I just don't understand why people are so opposed to making useful information obvious in the first paragraphs of the weapon's intro. Like, do you think that "the equializer can 2 shot most buildings at low health" is more important than "the equalizer has a massive, unlisted downside"? Why even have an intro if the weapon chart already explains almost everything about the weapon?<small>— ''The preceding unsigned comment was added by'' '''[[User:Purplemana|Purplemana]]''' ([[User talk:Purplemana|talk]]) • ([[Special:Contributions/Purplemana|contribs]]) 23:43, 5 November 2022</small> |
+ | |||
+ | {{outdent|7}}Remember to sign your comments. | ||
+ | The information that's currently on the page mentions that the damage scales, that's obvious enough rather than having to spell out exactly what "scaling" means. The intro covers the basic information and the damage and function times section goes into more detail.<br>[[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) 23:04, 5 November 2022 (UTC) | ||
+ | |||
+ | == Medic bug == | ||
+ | |||
+ | Hi there, | ||
+ | |||
+ | I've removed the Medic bug due to the proof using a custom HUD, this means that the custom HUD could've caused the bug rather than the game.<br>[[File:BLU Wiki Cap.png|20px|link=Wiki Cap]] | [[Help:Group rights|<span style="color:green;font-family:TF2 Build;">s</span>]] | [[User:GrampaSwood|<font color="DB9C1F">GrampaSwood</font>]] ([[User talk:GrampaSwood|<font color="DB9C1F">talk</font>]]) 09:02, 21 July 2023 (UTC) |
Latest revision as of 09:02, 21 July 2023
Hello, Purplemana!
Welcome to the Team Fortress 2 Official Wiki!
Here are a few links to get you started:
- If you're not too familiar with editing wikis, you might like to start with Help:Editing.
- If you already are familiar with wikiediting, you might want to try Help:Style guide.
- Recent Changes will let you see others' contributions as they happen.
- To make Recent Changes more useful for all users, remember to provide an edit summary in the "Summary" field before you save your changes.
- You can set the wiki to prompt you for a summary in your preferences.
- When posting on an article's Talk page you should add four tilde symbols or ~~~~ onto the end.
- This will add a signature and timestamp to your comment so others can easily tell who posted it.
- Any new sections on an article's Talk page should be added to the bottom of the page and not to the top.
- When editing normal article pages, don't sign your contributions.
- You can use the button in the editing toolbar to quickly add a signature.
- If you have any questions or need any help, please feel free to leave a message for a staff member.
- If you have trouble with anything on the wiki or you're not sure about a specific topic, feel free to join the IRC.
- You can also customize your user page if you like.
- When uploading images for use on your user page, please add the prefix User Purplemana to the file's name.
- Additionally, if you would like to add any self-made content to the wiki, please do so by adding the prefix User:Purplemana/ to the page title when you create the page.
Once again, welcome to the Team Fortress 2 Wiki!
-- WelcomeBOT (talk) 17:09, 5 July 2021 (UTC)
Recent edits
Hi there,
This edit is not trivia, it's how the weapon works. It's not trivia if it's the functionality of a weapon. Additionally also XofY.
This edit essentially says "another weapon doesn't have this bug", which is irrelevant.
This edit is not trivia, it's how the weapon works.
This edit is a bug about the Backscratcher, which is irrelevant to the Escape Plan. Additionally also XofY.
This edit is a feature of the Crusader's Crossbow and has nothing to do with critical hits. Additionally also XofY.
This edit summary is not acceptable. These edits were all removed with valid reasons, be friendly to other users.
GrampaSwood (talk) 21:54, 5 November 2022 (UTC)
- Hello swood
- Apologies if I'm doing this incorrectly, uve never used user talk before.
- Firstly, the trivia facts were my bad, i didn't realize that for it be trivia, it couldn't be specific things like unique ways the weapon works.
- However, what i believe was valid was how every single change i made was undo-ed, even the valid parts! Like, my tomislav change literally just wrote out what was in a tooltip, yet he still undo-ed it without even asking by asling me for :"evidence" of something that was already on the wiki! And for the equalizer, he undo-ed the entire thing, even the part I added that was separate from the trivia.
- Purplemana (talk) 22:05, 5 November 2022 (UTC)
- Regardless of how much you think your edits are valid, getting aggressive like this is not acceptable.
GrampaSwood (talk) 22:14, 5 November 2022 (UTC)
- Regardless of how much you think your edits are valid, getting aggressive like this is not acceptable.
- Fair, I apologize. Still, I have no idea why the equalizer text was removed, if it wasn't you. Well, you did undo it in the most recent change, which has me really, really confused. If you didn't remove it the first time, why did you just :::undo the page?
- Purplemana (talk) 22:22, 5 November 2022 (UTC)
- I changed the intro to mention that the damage scales with the health, as opposed to the damage increasing with health. This merges both sentences into one, with more detailed info being available down the page.
GrampaSwood (talk) 22:33, 5 November 2022 (UTC)
- I changed the intro to mention that the damage scales with the health, as opposed to the damage increasing with health. This merges both sentences into one, with more detailed info being available down the page.
- But...that explaination doesn't mention the "base" damage of the equalizer is lower than stock. Your explanation makes it sound like it starts at 65, then scales up, which it doesn't do (it starts lower, then eventually becomes higher). ::::To be perfectly honest, I didn't even notice your edit, as the two words (scales vs increasing) are often used interchangeably.
- Purplemana (talk) 22:38, 5 November 2022 (UTC)
- It's fine as-is, there's a section dedicated to the damage that makes it obvious already.
GrampaSwood (talk) 22:39, 5 November 2022 (UTC)
- It's fine as-is, there's a section dedicated to the damage that makes it obvious already.
- I've had this happen when trying to edit this wiki before. I just don't understand why people are so opposed to making useful information obvious in the first paragraphs of the weapon's intro. Like, do you think that "the equializer can 2 shot most buildings at low health" is more important than "the equalizer has a massive, unlisted downside"? Why even have an intro if the weapon chart already explains almost everything about the weapon?— The preceding unsigned comment was added by Purplemana (talk) • (contribs) 23:43, 5 November 2022
Remember to sign your comments.
The information that's currently on the page mentions that the damage scales, that's obvious enough rather than having to spell out exactly what "scaling" means. The intro covers the basic information and the damage and function times section goes into more detail.
GrampaSwood (talk) 23:04, 5 November 2022 (UTC)
Medic bug
Hi there,
I've removed the Medic bug due to the proof using a custom HUD, this means that the custom HUD could've caused the bug rather than the game.
| s | GrampaSwood (talk) 09:02, 21 July 2023 (UTC)