Category talk:Settings

Updating the page now, but I notice that closing and reopening the game settings window can change the variables that are shown in it. Where do we report construction settings bugs again? --Stickman 23:57, 31 March 2006 (EST)

If I noticed anything was misspelled I put a (sic) there. Sic is an editor's term that basically means "intentionally misspelled" and is often used when quoting some written work that missues spelling or grammar. See also sic on Wikipedia. I figured it would help avoid spur-of-the-moment "oh he made a typo here" corrections.

There are also a few oddities I didn't draw notes on. For example fAItalktoNPCtimer is one of the few that only capitalizes AI and NPC instead of using title capitalization. "Standoff" also only appears as one word, as near as I can tell, so "off" is always lowercase. When they use the word "to" it may or may not be capitalized. All the rules are out the window when dealing with facegen strings.

I assume the correctness will all eventually be double checked when people made sub pages for them with circles and arrows and a paragraph on the back of each one explaining what each one is.

Lastly, this page should be split into sections. It's 4:30am and I just spent the last few hours transcribing variable names. I'm in no mood to do that, but I did have an idea on how to play the game:

Two sections. If they know the variable name they're looking for, they can look at an alphabetical listing (divided into pages or variable type (eg, float, integer, string) and then alphabetical. Or if they know what it's related to, they can check the "subject" section and get info on things like facegen, xbox specific (a place to dump them), chargen, and until we get it all sorted, the all-inclusive "unknown" category.

I'll see about getting to the task later if no one else has. If I can figure out how to play this wiki game well enough. --Stickman 07:30, 1 April 2006 (EST)

Category size

As new articles are created for this category its going to explode in size. Can a webmaster weigh in on how we're to organize this stuff. A single massive article might be better than hundreds of small articles. MegaBurn 19:12, 2 April 2006 (EDT)

I'm of the position that settings should be split into general sections like Bribery. This page is almost entirely useless. Individual settings pages should have Redirects to their appropriate page. Daego 19:22, 2 April 2006 (EDT)

That might work for tutorials and/or general use article. This page is still necessary and its usefulness will increase as more articles are added. An alternative is splitting the category into 3 subcategories for f, i, s settings but thats still pretty ugly organization. 4 articles might be better, general article, f article, i article, and s article, then delete the setting specific articles that have already been created. Someone who's a sysop or higher needs to settle this... MegaBurn 19:36, 2 April 2006 (EDT)

This page isn't entirely useless, when categories reach 200+ they split across multiple pages and it becomes a royal PITA to swap pages when looking for related things. Go here (category:functions) and you'll see what I mean, paging between page1 and page2 to look for related functions isn't helpful. If sub categories (bribery, spellcasting) are needed, or useful for organization, then we create them as necessary and see what happens as the wiki evolves. FWIW there's nothing to "settle" at the moment, create some pages and see how they're used, if they become irrelevant then remove them, if not then expand on them. --Halo112358 20:12, 2 April 2006 (EDT)

--Kkuhlmann 16:39, 7 April 2006 (EDT): Why restrict yourselves to one solution? Script functions is organized in multiple ways: there are categories for each function type (Movement Functions, Player Functions, Crime Functions, etc.), and each command includes the Category:Functions (so it appears on the main page) as well as its particular function type (sometimes more than one). That way you get the best of both worlds -- one big category where you can see everything if you want to, plus smaller subcategories if you want to delve. It might help to put a higher level category above these pages (again, similar to the way script functions are organized) so that the massive multi-page list isn't the first thing you hit.

Monolithic list split

I chunked the monolithic list on the category page into three pieces, float, int & string settings - each of those is it's own include template. The category page still looks the same but now you can edit the sections without having to scroll through ~50Kb of text. We could also include those lists on other pages if we wanted to, though I really don't see a reason why we would. --Halo112358 19:08, 7 April 2006 (EDT)

Here's a separate page for the massive settings list: Comprehensive_Settings_List. I haven't moved the list off of the Category page because I wanted to see what people thought of the idea first. I think it's probably a good idea to make the list a "click for huge page of data" kind of thing instead of shoveling 50Kb of text at people as soon as they land in the Settings category.If no one objects I'll do it sometime next week - otherwise let's chat. --Halo112358 19:43, 7 April 2006 (EDT)

Collapsing similar pages

I've collapsed a number of similar pages into lists to reduce the number of articles appearing in the settings category. If you're adding new articles that deal with a number of similar settings, ie: iLockLevelMaxVeryEasy, iLockLevelMaxEasy, iLockLevelMaxAverage, iLockLevelMaxHard, etc.. please consider a list page instead of a number of small pages. This also makes future edits faster, instead of updating 5-10 pages you only need to update one.

Note: In some cases it would be nice to add redirect stubs into categories that aren't as full, I've tried creating redirect stub pages of this form:

#REDIRECT [[Collapsed Page XX]]
 [[Category:Foo Category]]

Unfortunately mediawiki doesn't support these sorts of stubs, everything after the #REDIRECT declaration is ignored. If this ever changes, or someone finds a workaround, please drop me a note. --Halo112358 19:26, 22 April 2006 (EDT)

--Mrflippy 16:40, 4 May 2006 (EDT): Try putting the category tag on the same line as the redirect as such:

#REDIRECT [[Collapsed Page XX]] [[Category:Foo Category]]