I've always found it kind of annoying that the concepts page is a long list of types rather than individual pages like the classes, or even the Prototypes and Types of data stage. Even though many of the concepts are just as complex as classes, just declarable instead of obtainable.
Like look at PathFinderMapSettings and how long it is. Especially with each field having a description of how exactly it affects things.
There's also AutoplaceControl and how long each description is. having those crammed into a little table makes them a little hard to read.
Finally there's the Filters, and how each of them have a bunch of subtypes. All the values you can filter off of gets kind of drowned out by the list of types that add fields. This causes me to forget that I can filter on whether a prototype is "hidden" rather than just the value of a specific field.
I would also prefer the events also got their own page, but that weighs on me less.
Besides these examples that I think are complex enough to necessitate not being drowned and surrounded by other entries, I just find myself losing my place. if I ctrl-f to find a specific phrase, I now have no clue where I am in relation to the concept I was trying to find something in.
Concepts should have different pages like Types
-
- Inserter
- Posts: 39
- Joined: Sat Aug 05, 2023 1:20 am
- Contact:
Re: Concepts should have different pages like Types
+1 for the love of god +1
coder? i hardly know her!