Talk:Main Page

Tips and Tricks

Any possibility of having the Tips And Tricks article added to the list ? --Daedalus 02:18, 13 December 2008 (UTC)

Might go well here: Getting Started under Helpful Articles

--Quetzilla 02:26, 13 December 2008 (UTC)

Wiki as PDF

Is there Any way to get ALL of this in PDF?

No there isn't, but Lord Gannondorf is compiling a modmaker manual you may be interested in. Here's the thread on the GECK forums.

--Qazaaq 21:54, 12 January 2009 (UTC)

Load Doors

Is there any possibility of someone creating a page pertaining to them? They're fairly important aspects, yet are barely touched upon, and I'm not the only person having trouble with them.

Editor Warnings and Solutions

Is there a list of editor warnings and solutions anywhere? I've been looking, but I can't seem to find one. I know that many of the warnings can be ignored, but some of them are important, and some of them can be fixed. If there isn't a list already, it might be worthwhile to add one. People who have questions about these warnings should be able to look them up on the wiki instead of googling them or asking on the forums, which wastes everyone's time. It might also be useful as a bug list for non-benign errors which could be corrected in a patch. Truant 17:04, 6 May 2009 (UTC)

I have an incomplete document that lists many scripting-related warnings and what to do about them. I was planning on completing, or at least doing a bit more work on it, before uploading it anywhere, but if you'd like I suppose I could upload it to the Wiki now.
-- Cipscis 23:24, 6 May 2009 (UTC)

After giving the matter some thought, here are some tentative suggestions.

The wiki has a 'Solutions' category which can be used as an umbrella category for the following subcategories:

• Editor warnings and solutions. A more or less comprehensive list of editor warnings and how to correct them. Whether or not specific warnings can be safely ignored or should be corrected before releasing a mod should also be clearly indicated. These should be copied and pasted directly from EditorWarnings.txt so that they can be easily searched for by users. (An exception should be made for warnings which refer to specific references--like warnings which include specific cell coordinates or the names of missing textures--in which case generic warnings should be used instead.) These should probably be listed alphabetically on their own page and linked to from other pages so that all of the editor warnings are listed in a single document.
• Editor bugs and workarounds. These are glitches like rendering issues in the render window, difficulty saving input to text input fields in the region editor, problems saving heightmaps without saving the plugin first, etc. These are run-of-the-mill bugs that won't show up anywhere as warnings and should probably be listed by tool: heightmap editor bugs, region editor bugs, render window bugs, etc. It is probably best if this information is actually included on the wiki pages for each of these tools and then linked to from this list rather than duplicated.
• Common modding errors and how to avoid them. These are 'best practices' for releasing clean mods that work as intended without errors. These should be organized by task: generating heightmaps, generating regions, generating LOD, etc. It is probably best if this information is actually included on the wiki pages for each of these tools and then linked to from this list rather than duplicated.
• Solutions to common modding tasks. These are workflows or scripts that solve common modding tasks like the ones that are already listed on the solutions page.
• FAQs for common questions about platform compatibility, etc. The existing FAQs page is fine as is.

The solutions category currently has the last two items, and information is available regarding some of the issues for the second and third items in various places on the wiki, but the first item is completely absent and a source of a great deal of concern and confusion for a lot of people.

Including all of this information in a single location (even if much of it consists merely of links) should go a long way toward solving a lot of these problems for a lot of people, cut down on the frequency of requests for help on the forums, and improve the overall quality of mods. (It might also be a good idea to include redirect pages for 'troubleshooting' and similar terms to lead people directly to the Solutions category.) Truant 12:58, 9 May 2009 (UTC)

Need More Examples

Some script examples only show you some of the function, and not other options that go with the function.

For example:

Syntax

---

Enable FadeIn:Int{Default = 1}

Example

---

TerminalRef.Enable

It does not show anything about "FadeIn" in the example.