User talk:Nescius

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 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)