User talk:Bot npc archer
Contents
Hello, Bot npc archer!
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 Bot npc archer 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:Bot npc archer/ to the page title when you create the page.
Once again, welcome to the Team Fortress 2 Wiki!
-- StarHorder 13:22, 25 November 2013 (PST)
Bienvenue !
Salut, et bienvenue sur le wiki ! Tu as l'air d'être assez familier des wikis, ou en tout cas t'es déjà à l'aise avec la syntaxe, une bonne chose ! Si tu as des questions sur quoi que ce soit, n'hésite pas à m'ajouter sur Steam (le lien est sur mon profil). Encore bienvenue et à bientôt ! ;) Brucelian (talk) 10:09, 26 November 2013 (PST)
Discussions
Heyo, Please do not post on discussion that have been inactive for a long period of time. You just revived a topic that ended in 2010. Please check the date before posting in a discussion. Thanks. Ashes (talk) 09:54, 30 November 2013 (PST)
Er, it's wrong. This talk page has been edited for the last time on January, 2013. Bot npc archer (talk) 09:57, 30 November 2013 (PST)
Ah, this is right. Bot npc archer (talk) 10:04, 30 November 2013 (PST)
Map articles
I appreciate your enthusiasm for creating new map pages, but it would be good if you focused on more well known maps, such as those here, rather than cp_cloak which although fun, is not very *playable*. Darkid (Talk | Contribs) 08:48, 29 December 2013 (PST)
About community maps? Bot npc archer (talk) 11:00, 29 December 2013 (PST)
- Well that and, I'd like to point this out. You should really only make a translated page about maps if there is an english page first. That way we can have a base of the translations instead of straight up translations we don't know if they're correct or not. Ashes (talk) 13:30, 29 December 2013 (PST)
- It was good if you made before a English page, so other people (like me) could translate as well. -- MarcoDoctorwho talk | contributi 13:33, 29 December 2013 (PST)
- Well that and, I'd like to point this out. You should really only make a translated page about maps if there is an english page first. That way we can have a base of the translations instead of straight up translations we don't know if they're correct or not. Ashes (talk) 13:30, 29 December 2013 (PST)
Voodoo-Cursed Spy screenshot
Hello, can you please re-do your screenshot without showing any extra items? Keep everything stock besides the Voodoo-Cursed Spy Soul. Keep in mind that the file name should be better, I'll rename it. Thanks. ▪ - 21:18, 24 July 2014 (PDT)
I have updated the file. Bot npc archer (talk) 15:58, 9 August 2014 (PDT)
Classic patches
Hi there,
I see you've made some new patch pages, however the moddb source link doesn't lead to a page that actually has any patch notes on it whatsoever, only a patch file for Half-Life. Is there any other way you can prove the validity of these updates?
GrampaSwood (talk) 18:40, 25 May 2022 (UTC)
- Hello, the release notes are in the patch executable and only there. They have never been directly written on a webpage.
- I don't think linking the executable itself is the right thing either. If you have another suggestion, I would gladly accept it.
- Bot npc archer (talk) 18:53, 25 May 2022 (UTC)
- If there is any way to link this image on the page instead of the moddb page, that'd be better (perhaps with both of them, but putting "Gotten from executable on: [link to moddb]" after it). Although it may introduce complications when you have more lines.
GrampaSwood (talk) 19:01, 25 May 2022 (UTC)
- If there is any way to link this image on the page instead of the moddb page, that'd be better (perhaps with both of them, but putting "Gotten from executable on: [link to moddb]" after it). Although it may introduce complications when you have more lines.
- The source link is built from the
source-title
and thesource
fields by Template:Patch_layout, so images cannot be inserted there directly. I tried placing the picture in the Release Notes themselves as some other patch notes do but it clips through the template and sizes under 300px are hardly readable.
- The source link is built from the
- I'm not sure what's the best way to put it. Changes in the template might be needed, unless the display issue can be fixed from within the page itself…
- Bot npc archer (talk) 19:28, 25 May 2022 (UTC)
- Oh sorry, I meant linking the file. Such as using
[[:File:HL1100-patch-layout-clipping.png]]
, this produces File:HL1100-patch-layout-clipping.png.
GrampaSwood (talk) 19:40, 25 May 2022 (UTC)
- Oh sorry, I meant linking the file. Such as using
- I see. Still, the
source
field only builds external links and thesource-title
is ignored ifsource
is missing/empty. This means that the ModDB page still has to be specified as source, or the picture's full external must be linked insource
and the patch download link must be placed in the patch notes below.- Bot npc archer (talk) 19:51, 25 May 2022 (UTC)
- I see. Still, the
Perhaps a ref would work instead.
GrampaSwood (talk) 19:53, 25 May 2022 (UTC)
- What do you think of this?
- Bot npc archer (talk) 20:08, 25 May 2022 (UTC)
- That's pretty much perfect, however that image doesn't seem to contain the actual patch notes for that page (It does say "Added Ricochet", so perhaps there's one for TFC too?).
GrampaSwood (talk) 20:17, 25 May 2022 (UTC)
- That's pretty much perfect, however that image doesn't seem to contain the actual patch notes for that page (It does say "Added Ricochet", so perhaps there's one for TFC too?).
- Actually, the whole version history is stored as-is in the text file, and notes for all games are in the same document since patches shipped everything for Half-Life, Half-Life: Deathmatch, Team Fortress Classic, etc. I filter out changes that do not affect TFC at all.
- I can make a screenshot showing the changelog but a single screenshot cannot cover the whole thing, however. I can make multiple screenshots at worst, although the template only supports up to three source links.
- Bot npc archer (talk) 20:25, 25 May 2022 (UTC)
- If there's a text file, that can also be uploaded to the wiki and then simply reference the lines that those patch notes are on. For example if an update's patch notes go from line 30 to line 45, you'd put <ref>[[:File:Filename.txt|Patch notes file]] line 30-45.</ref>.
GrampaSwood (talk) 20:29, 25 May 2022 (UTC)
- If there's a text file, that can also be uploaded to the wiki and then simply reference the lines that those patch notes are on. For example if an update's patch notes go from line 30 to line 45, you'd put <ref>[[:File:Filename.txt|Patch notes file]] line 30-45.</ref>.
- The text file is self-contained in the executable, but it is a text file. File:HL-RELNOTES.TXT.
- Please view here for how it looks like.
- Bot npc archer (talk) 20:41, 25 May 2022 (UTC)