User talk:Nescius

Same reason

File:UserAvatar-Nescius.png

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)

The script should be without file extension in vscripts keyvalue (there is no case actually where specifying .nut is needed that I know of). And yes it is relative to scripts/vscripts folder. FireUser3 will set the counter to 0 so that's correct. -- Nescius (talk) 12:28, 8 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)

Deleted in total 1060 :<lang> suffix redirect pages that had 0 links to them Nescius (talk) 14:35, 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)

Oh... sorry I was assuming it was an error. I guess it went over my head when it parsed a couple links that already used the 'hacky' way of directing to Category:Ru/. Cvoxalury (talk) 11:44, 11 July 2024 (PDT)

Very nice work with everything so far, by the way. Thanks a lot for putting it all in motion, and the new templates. Cvoxalury (talk) 11:57, 11 July 2024 (PDT)

Thanks! Hopefully multipage will be smoothly removed tomorrow which I plan to do Nescius (talk) 12:01, 11 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.