Nescius' talk page
Same reason
Concise Pages
I understand the idea behind making it so you don't have to scroll through a whole bunch of mostly-stock keywords, but removing some of these templates entirely feels like a little much. for one thing, it can be really annoying to track down the removed keyvalues and I/O if you aren't familiar with the template system. for another, it can make it look like they don't have certain inputs and KVs when they should. also
{{KV Targetname}} is deprecated.
I think it'd generally be better to put the mostly-expected stuff in a scrollbox. most of the "stock-ish" templates (like {{I BaseEntity}}) are supposed to do this on their own? except I think suddenly a bunch of them started turning noscroll on by default. (most of them can still have noscroll set to 0 to force them to scroll.) — Kestrelguy (talk) 18:12, 23 October 2022 (PDT)
- Listing those kio is most of the time irrelevant and just makes the page cluttered without knowing what to look for. Let’s take for example info_landmark. There is no reason to use any of the baseentity kio other than targetname. All of those put in there just makes the page look ugly and people that don’t know much about info_landmark will be confused why even list everything when only targetname is relevant. Also they would have to scroll through all the clutter to get to the "See Also" section or maybe will completely overlook it. I was thinking of putting baseentity kio on point entity and brush entity pages since they are always one click away from each entity but not sure. The scroll box looks even worse imo and it still lists lot of completely irrelevant stuff for most entities. Even better example than info_landmark is prop_health_cabinet. Check how it looked before my edit it was horrible mess. Like 10 irrelevant templates and 10meters long page. Nescius (talk) 22:09, 23 October 2022 (PDT)
Regarding the explanation on how to decrease the counter in game_scavenge_progress_display
Hello, about a month ago, you've updated the page to say that it is possible to decrease the number of cans filled counter using VScripts. I've wanted to do this for a personal project a couple of years ago but could never find any info on it, so I assumed it was a Valve limitation. When I noticed that the page has been updated to say that it is possible with VScript my interest has piqued. But it's been nearly a month now and the explanation is still marked as todo, so I thought I should follow up on this. I would definitely appreciate it if you could add the explanation soon!--Proaxel (talk) 15:50, 2 October 2023 (PDT)
- Added VScript example on that page. Hopefully it helps. Honestly that todo would probably stay there forever if you didn't ask Nescius (talk) 09:49, 5 October 2023 (PDT)
- Thank you! If you don't mind I would like to describe I want to use it for and then you can tell me if this is sound. Please bear with me, I'm still a rookie to VScripts in general. A quick summary: The map has two different scavenge events that survivors must complete in order to progress, one earlier in the level and one towards the end. The problem is that the game_scavenge_progress_display for the second scavenge event carries over the amount of cans poured from the first event, so on the second event players are often confused as to why they already have X/Y cans, why is it showing X being greater than Y, and all that. So to resolve this, I should do the following:
- * For the first event's game_scavenge_progress_display (named scavenge_event_first), add the following KeyValue alongside the "targetname" and "max" : "vscripts" "game_scavenge_progress_display_enhancement.nut"
- (When specifying the nut file for the vscripts KeyValue, it is already relative to the scripts/vscripts folder right?)
- * On the first event's math_counter, add the following output: "OnHitMax" "scavenge_event_first,FireUser3,,0,-1"
- So what should happen is that the first event goes as usual. And then once survivors reach the second event, the HUD counter should reappear and be back to zero. Is this all correct?--Proaxel (talk) 05:10, 8 October 2023 (PDT)
- Added VScript example on that page. Hopefully it helps. Honestly that todo would probably stay there forever if you didn't ask Nescius (talk) 09:49, 5 October 2023 (PDT)
Valve Developer Community:Moderator elections
Hi: You have been accepted as a moderator. Please be sure to read up on Help:Etiquette and Valve_Developer_Community:Terms of Use. PabloS (talk) 12:20, 17 June 2024 (PDT)
- Thanks! All the votes were nice surprise. Tested my page deletion privilege to delete few of my mistakenly made pages :d Nescius (talk) 12:35, 17 June 2024 (PDT)
The bot and suffixes
I thought you didn't want the lang suffixes as they create the search clutter problem. What changed? Cvoxalury (talk) 11:39, 4 July 2024 (PDT)
- There are lot of redirect pages that have :<lang> suffix. Trying to remove as much of them as possible. So far deleted like 500 of such redirects that had 0 links to it. But many of them are still linked from other pages, so what I am doing is simply changing the links to not go through the :<lang> page redirect and can be safely deleted. I am still against the suffixes and what I am doing here is for lowering the clutter. Nescius (talk) 11:46, 4 July 2024 (PDT)
Bot + Template:L + Categories
The bot appears to be making an error when using L with category links. Example.
So the link was supposed to be :Category:Stuff, but becomes LCategory|Stuff. Which is two errors in one, it seems.
Manually I didn't find a way to use L with categories, so I resorted, on a couple translating pages, to manually putting :Category:Ru/Stuff.
Also, I'll ask here, is there currently a way to use L with links like {{source|4.1}}? Cvoxalury (talk) 10:49, 11 July 2024 (PDT)
- Template:LCategory is intended. It only converts links to the category not when categories are added i.e. [[:Category:Something]] will by converted to {{LCategory|Something}} but when it's just [[Category:Something]] that will be left untouched. If we were on Ru/ prefix page and used {{LCategory|Level Design}} it would create [[:Category:Ru/Level Design|Level Design]] which is proper link Level Design. For {{source|4.1}} to consider languages I think game icon or whatever template it uses can be modified for that. Nescius (talk) 11:34, 11 July 2024 (PDT)
- You plan for it to be largely automated, I assume? In that case: the bot's going to take the this-is-a that's typically on the multipage, and move it to /en, and copy it to all the lang/ pages? I've previously done that manually to some pages (not many) that only had /en. Would that cause some issues? (also, I'm pretty sure there's a number of MultiPages that also include things like icons, infotables, [[File: ]] illustrations. Will it be able to grab them too? Cvoxalury (talk) 02:38, 12 July 2024 (PDT)
- I am planning to automate MultiPages that don't use no-en-subpage or page parameter or are on protected pages. Those will be done manually to not overly complicate the script. I am basically copying stuff that's above and below {{multipage}} to the /lang pages and converting categories to use Template:ACategory on /lang pages. Nescius (talk) 02:45, 12 July 2024 (PDT)
New template is broken
The new language template just straight up doesn't work. Only the english flag is appearing now and whenever I press it it turns out to just be an image.
Also the "L|" before any link is really annoying since most of those pages I haven't gotten around to translating yet. --MarvinG
- I accidentally left a curly bracket in edit about 10 mins ago. Fixed shortly after. Nescius (talk) 14:39, 11 July 2024 (PDT)
- Ok cool but can you please not add the "L|", I really don't like the fact it makes all the links red.
- The L was added already on 99% of non english pages. I don't really see a good solution to the red links but I would say it's a good thing to quickly know what needs translation and do it. If L wasn't used you would have to go around changing english links everytime when you make a translation for a new page which doesn't sound very good Nescius (talk) 14:45, 11 July 2024 (PDT)
- Yeah I get that but like, there's only 2 active croatian users on this entire site so it seems kind of redundant, to me at least, but I see what you're getting at. Welp I better get to translating then.
- Wait I just realized, this broke the this is a template. Now every translated page is gonna have it in english.
- Yeah I get that but like, there's only 2 active croatian users on this entire site so it seems kind of redundant, to me at least, but I see what you're getting at. Welp I better get to translating then.
- The L was added already on 99% of non english pages. I don't really see a good solution to the red links but I would say it's a good thing to quickly know what needs translation and do it. If L wasn't used you would have to go around changing english links everytime when you make a translation for a new page which doesn't sound very good Nescius (talk) 14:45, 11 July 2024 (PDT)
- Ok cool but can you please not add the "L|", I really don't like the fact it makes all the links red.
Main Page's setup
Creating a topic here, because atm there's feels like several ongoing discussions on its page, and it's more of a technical moment anyway.
Do you have any insight about why the Main Page needs to use strings at this time?
I assume the reasoning was, since strings can be translated by just adding to them a language code and the text, the formatting and even most of code on the translated pages can stay the same.
But why is that a concern? Even before multipage removal, they were all split pages, so translating them on the spot made the most sense and was the easiest. Even if someone adds a new language to it right now, what, they're supposed to be translating by constantly saving changes on the strings page, then reloading their main page? That's so backward.
I mentioned the technical moment. Question is, what's the perf difference between including {{string}}s and including just text directly? Can we/you measure it? Cvoxalury (talk) 01:30, 14 July 2024 (PDT)
- I see the benefit of it that it's easy to make the design consistent on all the translated pages and update it fast if needed by keeping strings. Most of the main page stuff is inside Template:MainPage which is then transcluded on all the translated pages. Since we want templates to remain universal it makes sense to simplify it there with strings. As for the strings used on the main page itself in the footer that should be probably moved to a template otherwise string usage there doesn't help much. Nescius (talk) 03:20, 14 July 2024 (PDT)
request
Hello! Could you move Alternative Languages to the correct page name? Related translations are broken. DarkKong (talk) 09:10, 14 July 2024 (PDT)
- Moved it. If by related translations you mean the autolang titles then that needs its own page under Valve_Developer_Community:Zh/Alternative_Languages for example Nescius (talk) 09:24, 14 July 2024 (PDT)
Question regarding Recent Changes and your bot
Hello, I've noticed that your bot often does large amounts of edits at once. The work you are doing is awesome, but I was wondering if you were able to hide your bot's actions like how VDCBot's edits are hidden behind the Show Bots button. Unless you would like to keep the bots edits easily visible, I just think that it would make looking through Recent Changes for human edits easier.
As it stands right now, if someone were to vandalize a page when your bot edits 50+ pages at once (the default recent changes log length) it would get easily hidden, which could lead to to take a while before the edit were to get noticed. Just a concern I have. Of course, I could be missing something and it's not an actual concern and I am just overthinking, but that's just something I thought of. -Equalizer, aka the better pickaxe (talk) 17:48, 27 July 2024 (PDT)
- Aware of this and unfortunately it seems I would need have bot user group on that account to be able to mark it as bot edit. I am marking all the edits as minor at least so the "hide minor edits" can be used sometimes when it's not lot of moves, deletions or new pages. Also watchlist should not be as flooded Nescius (talk) 17:52, 27 July 2024 (PDT)
Images on your user page
I'd ideally like to limit the amount of images specifically meant for user pages to 1 or 2—yours has ~13. I'd kindly ask that you get rid of some of them. Thanks. PabloS (talk) 14:09, 13 August 2024 (PDT)
some translation pages have been deleted
Hello! Due to titles those pages used have not been changed to the correct format, they have been deleted by bots, such as Momentary rot button/zh and Func brush:zh-cn. And there aren't copies for them on the wiki. Could you restore them and move to the correct pages? DarkKong (talk) 16:18, 13 August 2024 (PDT)
- Moderators don't have the restore privilege unfortunately so I can only recreate the pages which wouldn't restore the page history. I see those pages were removed by CrematorBot so need to write to admin User talk:PabloS. I see that those pages were made by you so if you want to simply recreate them I can copy their contents and paste to your user page or just recreate them myself --Nescius (talk) 16:25, 13 August 2024 (PDT)
- Well, I think you can copy the contents and paste them, then I will recreate them. Thank you. DarkKong (talk) 16:31, 13 August 2024 (PDT)
- pasted here User:1416006136/Sandbox --Nescius (talk) 16:35, 13 August 2024 (PDT)
- Well, I think you can copy the contents and paste them, then I will recreate them. Thank you. DarkKong (talk) 16:31, 13 August 2024 (PDT)
Why did you delete CDynamicProp template pages?
Hello. I see you deleted Template:KV_DynamicProp, Template:I_DynamicProp, Template:O_DynamicProp. Currently, CDynamicProp is a red link. I want to convert those red links in Class Hierarchy boxes into blue links. I saw that CBaseEntity uses templates so I want to build more pages like that. So I don't understand why you deleted Template:KV_DynamicProp and related Inputs and Outputs pages?
When navigating to archived page and looking at its history, I see that those were very useful decent quality templates contributed by many people but you single-mindedly decided that they must not exist and used your moderator power to delete them. I don't support your decision. Gameplayer (talk) 14:01, 9 September 2024 (PDT)
- If I deleted them you wouldn't be here linking them and you would need admin powers to restore them but ok. I archived them because their content was moved to prop_dynamic and there was no need for those templates anywhere at the time --Nescius (talk) 16:45, 9 September 2024 (PDT)