Unreal Wiki - User contributions [en]

MediaWiki:Monobook.css

2009-07-29T01:37:43Z

Haarg: adjust for new syntax highlight extension version

/* <source lang="css"> */

/** Unreal Wiki Style **********************************************************
*
* Description: Adjustments to the style to give the site a bit more of a unique
* identity
*/

/* global background color */
body {
background: #cfe7ff;
}

/* indent sidebar boxes a tiny bit */
#p-navigation,
#p-search,
#p-tb {
margin-left: 0.4em;
width: 11.2em;
}

/* sidebar box background color */
#p-navigation .pBody,
#p-search .pBody,
#p-tb .pBody {
background: #eff7ff;
}

/* content and page tab background color */
#p-cactions li,
#p-cactions li a {
background: #e0f0f7;
}
#content,
table,
#p-cactions li.selected,
#p-cactions li.selected a,
#p-cactions li a:hover {
background: #eff7ff;
}

/* Legacy namespace content */
.ns-100 #content,
.ns-101 #content {
background: #eff7ff url(/w/images/LegacyBackground.png) top right no-repeat;
border-color: #909;
border-width: 2px;
}
blockquote.legacyquote {
background-color: #cfe7ff;
border: 1px solid #909;
margin: 1em 25%;
padding: 0.5em 1em;
}

/* UE1 namespace content */
.ns-102 #content,
.ns-103 #content {
/*background: #eff7ff url(/w/images/UE1Background.png) top right no-repeat;*/
border-color: #880;
border-width: 2px;
}

/* UE2 namespace content */
.ns-104 #content,
.ns-105 #content {
/*background: #eff7ff url(/w/images/UE2Background.png) top right no-repeat;*/
border-color: #13b;
border-width: 2px;
}

/* UE3 namespace content */
.ns-106 #content,
.ns-107 #content {
/*background: #eff7ff url(/w/images/UE3Background.png) top right no-repeat;*/
border-color: #800;
border-width: 2px;
}

/* page tab border color */
#p-cactions li {
border-color: #c0c0c0;
}
#p-cactions li.selected {
border-color: #aaa;
}

/* tab border hack for IE 6 and earlier */
* html #p-cactions li {
border: none;
background-color: transparent;
}
* html #p-cactions li.selected {
border: none;
background-color: transparent;
}
* html #p-cactions li a {
border-color: #c0c0c0;
}
* html #p-cactions li.selected a {
border-color: #aaa;
}

/* tab border hack for IE 7 */
*:first-child+html #p-cactions li {
border: none;
background-color: transparent;
}
*:first-child+html #p-cactions li a {
border-color: #c0c0c0;
}
*:first-child+html #p-cactions li.selected a {
border-color: #aaa;
}

/* personal links */
#p-personal li a:hover {
background-color: transparent;
text-decoration: underline;
}

/* heading and line color */
h1, h2 {
border-bottom: #cde solid 1px;
}
h1 {
color:#508;
}
h2 {
color:#40a;
}
h3 {
color:#0a0;
border-bottom: #cec solid 1px;
}
h4 {
color:#04a;
}
hr {
color: #909;
background-color: #909;
margin-top: 1em;
margin-bottom: 1em;
}

#mw-subcategories h3,
#mw-category-media h3,
#mw-pages h3 {
color: black;
border-bottom: none;
}

#siteNotice {
float: right;
font-style: italic;
text-align: right;
max-width: 40%;
}

/** Advertisement placement ****************************************************
*
* Description: Positions the advertisement correctly, and adjusts the footer
* bar to fit in well with it.
*/

#f-copyrightico {
top: 0px;
margin: 10px 0px 19px 8px;
}
#f-poweredbyico {
top: -4px;
margin: 0px;
}
#f-poweredbyico, #f-copyrightico {
height: auto;
}
#footer {
background: #eee;
border-top-color: #aaa;
border-bottom-color: #aaa;
min-height: 55px;
padding: 4px 0pt 1px;
}
/* hacks for IE6 (and earlier) */
* html #footer {
height: 55px; /* replacement for lack of min-height (actually has same effect) */
border-left-color: #aaa; /* IE6 can't have full-width footer, so left border needs proper color */
}
#footer li {
white-space: nowrap;
margin: 0px 0.9em;
}

/** Tab size inconsistency fix *************************************************
*
* Description: Fix tab sizes for when font dimensions are different (Mac).
*/

#p-cactions li {
padding-bottom: 0.2em;
}

#p-cactions li.selected a {
padding-bottom: 0.3em !important;
}

.ns-100 #p-cactions li a,
.ns-101 #p-cactions li a,
.ns-102 #p-cactions li a,
.ns-103 #p-cactions li a,
.ns-104 #p-cactions li a,
.ns-105 #p-cactions li a,
.ns-106 #p-cactions li a,
.ns-107 #p-cactions li a {
padding-bottom: 0.4em;
}

.ns-100 #p-cactions li.selected a,
.ns-101 #p-cactions li.selected a,
.ns-102 #p-cactions li.selected a,
.ns-103 #p-cactions li.selected a,
.ns-104 #p-cactions li.selected a,
.ns-105 #p-cactions li.selected a,
.ns-106 #p-cactions li.selected a,
.ns-107 #p-cactions li.selected a {
padding-bottom: 0.4em !important;
}

/** Source code highlighter modifications **************************************
*
* Description: Adjustments to the source code highlighter to fit better with
* the rest of the site style.
*/

div.mw-geshi {
background-color: #f9f9f9;
border: 1px dashed #2f6fab;
color: black;
padding: 1em;
}
div.mw-geshi pre {
background-color: transparent;
border: none;
color: inherit;
padding: 0;
margin: 0;
max-height: 50em;
}
.mw-geshi, .mw-geshi * {
line-height: 1.1em;
}

/* </source> */

Help:User page

2009-07-01T22:25:07Z

Haarg: Reverted edits by 146.83.8.31 (Talk) to last version by Wormbo

A '''user page''' is a page about a wiki user; someone who registered on the wiki, and is (most probably) a contributor. If you have registered, you can create your own user page. Your user page is linked in the top right. More importantly, others will see links to your user page from various places which assist wiki collaboration. This includes the 'Recent changes' and page 'history' displays (See [[Help:Tracking changes]]). You can also link to your user page within text of a wiki page, which is mainly useful on [[Help:Talk pages|talk pages]] when you sign your name.

== What to put on your user page ==
User pages are just as flexible as any other wiki page, and it's a page all about you, so generally people will leave you to freely write your user page in whatever format you like. Think of it as a 'profile' page. It's a feature to help other people know who you are, and to bring the online community closer together. You might like to mention where you are from and what your job is. You can also state what your main areas of interest are in relation to the topic of the wiki, and describe contributions you have made or are areas where you are interested in contributing.

=== User scratchpad / development area ===
You can use your user page as a scratchpad. An area for developing ideas without cluttering the main namespace. If subpages are enabled (See [[Help:Subpages]]), you may find them useful for creating sub pages under you user page. However you should avoid expending too much effort within your own area of the wiki. Be bold! Edit the main wiki articles! You can also use the shared [[Project:Sandbox|Sandbox]] page for quick (non-permanent) wiki experimentation.

== Other people's user pages ==

As mentioned above, you will see links to other people's user pages, in various places throughout the wiki.

=== User Contributions ===
When viewing another person's user page, an additional link "''user contributions''" appears in the 'toolbox' area (bottom left). This takes you to a list of all of this user's wiki edits. Use this to get an idea of how prolific a contributor somebody is, or to track down edits made by a user who is causing trouble/making bad wiki edits.

=== Editing someone else's page ===
It's generally considered bad etiquette to rewrite or reword another person's user page. Editing is not disallowed, but you should avoid adding information (or especially opinions) which might be misinterpreted as coming from that user, in situations where this could potentially cause upset. Some types of edit are widely acceptable, and unlikely to cause upset:

* Fixing wiki links, when a page has been [[Help:Moving a page|moved]] or [[Help:Deleting a page|deleted]]
* Fixing broken external links
* Categorizing or fixing categories of user pages.

=== User talk pages ===
Every user page has an associated talk page; a "user talk page". This is a special kind of talk page, for leaving messages directed at a particular user. See [[Help:Talk pages#User Talk pages]].

[[Category:Help|{{PAGENAME}}]]

Legacy:Using The Wiki

2009-06-12T00:07:05Z

Haarg: Reverted edits by 93.72.233.81 (Talk) to last version by Wormbo

Welcome to the Unreal Wiki. This page explains how to get the most out of the site.

==The Wiki Concept ==

{{innerbox| The Wiki is a real-life "Hitchhiker's Guide to the Galaxy", the black thing with "Don't Panic!" written (in big friendly letters) on its cover, only that anybody can edit it. It occasionally also represents the chaos of all the discussions in the Wiki, resembling the random recipes to the ''Pan Galactic Gargle Blaster'' and similar things.

}}

In other words: If you can't find it, ask somebody to add it. If nobody can help, find out and add it. Let the discussions go chaotic, but clean it up later.

A '''Wiki''' is a kind of website where anyone can edit pages. At the foot of every page you'll find a link "Edit text of this page." Clicking this will load a new page with a form containing the page text.

The idea is that everyone can easily and quickly contribute information and ideas (and stuff). You may add to or reorganize any page, except some where the original author has requested otherwise (such as personal contributor pages).

* '''Everybody can edit. That's a feature, not a security hole.''' So, yes, with very few exceptions you can just go ahead and overwrite a page full of content with some random garbage (and in fact that happens every once in a while). But all changes are logged, old revisions of a page are kept by the system and can be restored by anyone with only a few clicks. If you want to know more about how and why this site works, see the [[Legacy:Wiki FAQ|Wiki FAQ]].

* The raw text you edit is not HTML, but '''plain text with simple markup''' to produce features such as headers and lists. See [[Legacy:Wiki Markup|Wiki Markup]] for more.

* The [[Legacy:Sandbox|Sandbox]] has been established for '''practising Wiki markup editing.''' If you want to get a feel for how the Wiki system works, go there and try it out. Please don't make practice edits on other pages.

For more about contributing to the Unreal Wiki see [[Legacy:New Contributors Quick Start|New Contributors Quick Start]]. The rest of this page is about using the site to find information.

==Wiki Etiquette==

Contributing etiquette aside, there are a few points we'd like visitors to consider:
* Please don't use "harvester" or "offline reader" downloading programs to grab the entire contents of the Unreal Wiki. [[Legacy:Offline Wiki|Offline Wiki]] explains why and suggests alternatives.
* Please don't send emails with general mapping and coding questions to site contributors (such as tarquin or Mychaeel). What we know we tend to write here. What we don't know, we don't know. We recommend BeyondUnreal's [http://forums.beyondunreal.com/forumdisplay.php?forumid=13 Unreal Development] forums: posting here means that more people see your question, and the answers you get are also available for other people to read (if you add what you learn to the Wiki, even better).

==Finding Things==

The Unreal Wiki has over 2,000 pages. That's a lot of stuff. This site is a ''WikiWikiWeb'', and thus it's a ''web'' of pages rather than a hierarchy. Like other wikis, don't expect to take it all in at one sitting. Take some time to wander round.

There are various "ways in" to the Wiki:

===Topic Pages ===

The [[Legacy:Home Page|Home Page]] is the starting point for the site. Rather than list hundreds of links there, we've organized articles into '''topic pages''', such as [[Legacy:Architecture|Architecture]], [[Legacy:Lighting|Lighting]] and [[Legacy:Texture Topics|Texture Topics]]. Topic pages give an overview of a subject, and links to both tutorials and reference articles.

===Search Engine===

You can easily perform a full-text search of the Unreal Wiki. Just enter some terms (separated by spaces) and hit <code>Enter</code>. The Wiki will show you the pages that match your query best. (Enclose terms that contain blanks of their own in double quotes.)

@search@ '''Search the Unreal Wiki:''' <br />@input@ @submit@

There is a search field at the bottom of every page on the site. You'll find further tips on searching on the dedicated [[Legacy:Search|Search]] page.

===Browser Tabs ===

The [[Legacy:Wiki Integration|Wiki Integration]] page has tabs that plug in to most browsers. These allow you to create your own personal sidebar of frequently visited pages on the site. There are mIRC scripts too.

===Backlinks ===

You can backtrack with your browser's ''back'' button like with any other site. But you can also get a list of all the pages that link to the page you're reading. To do this, simply click the page's title text (the big bold heading right at the top).

===Related Topics ===

Most pages should give a list of "related topics" at the foot. If you think we've missed some, please add them!

===Categories===

Some pages are grouped in '''Categories'''. This is a sort of tagging system, where the "tag" is just a link at the foot of the page of the form "Category {''topic''}".

This is actually just an application of the backlink feature: we create a page called "Category Bob", and put a link to it on articles we want to be in that category. On the "Category Bob" page, clicking the title produces a list of all the pages that link there – which is those pages we chose to put into the category.

Any Category page it itself a member of the [[:Category:Legacy Category]]. So go there to get a list of all categories.

==Helping out==

So you've found more Unreal Engine info that you can shake a stick at. Want to help us get even better?

* [[Legacy:New Contributors Quick Start|New Contributors Quick Start]]

If you've got a minute to spare, take a look at [[Legacy:UnrealWiki To Do|UnrealWiki To Do]] :)

==What Next?==

More on the site at [[Legacy:Project FAQ|Project FAQ]] and [[Legacy:Project Aims|Project Aims]].

You can ask about the site at:
* [[Legacy:Project Discussion|Project Discussion]]
* [http://forums.beyondunreal.com/forumdisplay.php?forumid=249 Project forum]
* irc://irc.enterthegame.com/unrealwiki

The [[Legacy:MetaTopics|MetaTopics]] page has links to all the pages about the site.

Template:UT3

2009-03-08T23:43:52Z

Haarg:

{{#switch:{{{1|}}}
|icon=[[Image:Icon-UT3.png|link=Unreal Tournament 3|alt=UT3]]
|#default=[[Unreal Tournament 3]]
}}

Template:UT2004

2009-03-08T23:43:27Z

Haarg:

{{#switch:{{{1|}}}
|icon=[[Image:Icon-UT2004.png|link=Unreal Tournament 2004|alt=UT2004]]
|#default=[[Unreal Tournament 2004]]
}}

Template:UT2003

2009-03-08T23:43:02Z

Haarg:

{{#switch:{{{1|}}}
|icon=[[Image:Icon-UT2003.png|link=Unreal Tournament 2003|alt=UT2003]]
|#default=[[Unreal Tournament 2003]]
}}

Template:UT

2009-03-08T23:42:36Z

Haarg:

{{#switch:{{{1|}}}
|icon=[[Image:Icon-UT.png|link=Unreal Tournament|alt=UT]]
|#default=[[Unreal Tournament]]
}}

Template:UE3

2009-03-08T23:41:53Z

Haarg:

{{#switch:{{{1|}}}
|icon=[[Image:Icon-UE3.png|link=Unreal Engine 3|alt=UE3]]
|#default=[[Unreal Engine 3]]
}}

Template:UE2Runtime

2009-03-08T23:41:26Z

Haarg:

{{#switch:{{{1|}}}
|icon=[[Image:Icon-UE2Runtime.png|link=Unreal Engine 2 Runtime|alt=UE2Runtime]]
|#default=[[Unreal Engine 2 Runtime]]
}}

Template:UE2

2009-03-08T23:40:48Z

Haarg:

{{#switch:{{{1|}}}
|icon=[[Image:Icon-UE2.png|link=Unreal Engine 2|alt=UE2]]
|#default=[[Unreal Engine 2]]
}}

Template:UE1

2009-03-08T23:40:11Z

Haarg:

{{#switch:{{{1|}}}
|icon=[[Image:Icon-UE1.png|link=Unreal Engine 1|alt=UE1]]
|#default=[[Unreal Engine 1]]
}}

Template:U2XMP

2009-03-08T23:39:35Z

Haarg:

{{#switch:{{{1|}}}
|icon=[[Image:Icon-U2XMP.png|link=Unreal 2 Expanded Multiplayer|alt=U2XMP]]
|#default=[[Unreal 2 Expanded Multiplayer]]
}}

Template:U2

2009-03-08T23:38:56Z

Haarg:

{{#switch:{{{1|}}}
|icon=[[Image:Icon-U2.png|link=Unreal 2|alt=U2]]
|#default=[[Unreal 2]]
}}

Template:U1

2009-03-08T23:38:14Z

Haarg:

{{#switch:{{{1|}}}
|icon=[[Image:Icon-U1.png|link=Unreal 1|alt=U1]]
|#default=[[Unreal 1]]
}}

Template:RTNP

2009-03-08T23:37:32Z

Haarg:

{{#switch:{{{1|}}}
|icon=[[Image:Icon-RTNP.png|link=Unreal - Return to NaPali|alt=RTNP]]
|#default=[[Unreal - Return to NaPali]]
}}

MediaWiki:Opensearch-desc

2009-03-08T23:34:56Z

Haarg: Created page with '{{SITENAME}}'

MediaWiki:Editnotice-100

2009-03-08T23:34:28Z

Haarg: Created page with '<div id="mw-legacypageedit">Edits to legacy pages are strongly discouraged. Be sure that your edits are in line with the Legacy page license.</div>'

<div id="mw-legacypageedit">Edits to legacy pages are strongly discouraged. Be sure that your edits are in line with the [[Legacy:Project Copyright|Legacy page license]].</div>

User talk:Haarg

2008-12-10T13:37:20Z

Haarg:

== Quips ==

Can I have this extension? [[User:Dagoth|Dagoth]] 00:13, 23 November 2008 (UTC)
: Sure, although it's a bit of a hack. Not horrible mind you, but I only needed it to work with this site. I'll package it up in the next day or two. — [[User:Haarg|Haarg]] 13:37, 10 December 2008 (UTC)

Main Page

2008-07-26T00:40:13Z

Haarg: Reverted edits by Prefix (Talk); changed back to last version by ElMuerte

'''Welcome to the {{SITENAME}}.''' This site's goal is to provide comprehensive documentation of the [[Unreal Editor]], [[UnrealScript]] and all technical aspects of the [[Unreal Engine]].

If you came here as a player and are looking for details about the Unreal series of games, head over to BeyondUnreal's [[Liandri:|Liandri Archives]]. If you are a server administrator looking for information about running servers for Unreal series games, try the [[uadmin:|Unreal Admin Wiki]] instead.

{{ambox|type=serious|text=Please refrain from using an offline reader or similar tools to download the entire Unreal Wiki.

These tools put an insane stress on the server and will most likely get you banned immediately. The Unreal Wiki has a very dynamic nature, but if you want to download a recent snapshot, try our downloadable [[Project:Offline Wiki|Offline Wiki]] archive.}}

{{ambox|type=notice|text=We've recently [[Unreal Wiki:MediaWiki conversion|switched]] to the [[wp:MediaWiki|MediaWiki]] engine, and we're taking this opportunity to refresh the site's organization and content. The old content is available in full at [[Legacy:Home Page|the legacy home page]]. During this transition, you'll notice many red-colored links, which point to pages that don't yet exist. [[Project:Community Portal|See how you can help]] form the new, improved {{SITENAME}}.}}

__NOTOC__ __NOEDITSECTION__
{| cellpadding="0" cellspacing="10px" style="width:100%;"
| id="topic-list" style="vertical-align:top;" |
==Community==
The [[Project:Community Portal|Community Portal]] is the general place to find out what's going on and what needs to be done on the {{SITENAME}}.

New to the {{SITENAME}}? Feel free to join the other {{NUMBEROFUSERS}} users by [[Special:Userlogin|registering]]. The {{SITENAME}} is a community project and you are invited to [[Project:Helping out|help improve]] it. [[Project:Getting started|Getting started]] provides some tips on how to get started!

==Content==
The quickest way to find what you're looking for usually is the search box on the left. Otherwise, try one of the topical starting points below.

===General topics===
* [[Unreal Engine overview]]
* [[Modding overview]]
* [[Modding ideas|Modding ideas]]

===Mapping reference===
* [[Unreal Editor overview]]
* [[Mapping concepts]]
* [[:Category:Mapping tutorials|Mapping tutorials]]

===UnrealScript reference===
* [[UnrealScript overview]]
* [[:Category:Classes|UnrealScript API]]
* [[:Category:Programming tutorials|UnrealScript tutorials]]

===Modeling reference===
* [[Modeling overview]]
* [[:Category:Modeling tutorials|Modeling tutorials]]

Still can't find what you were looking for? You can browse through all of the [[:Category:Article categories|articles by category]] or the [[Legacy:Home Page|old {{SITENAME}} content]].

| style="vertical-align:top;" |
{| class="infobox infobox-pages" id="recent-edits" style="width:300px;float:none;margin-left:auto;"
|-
| style="text-align:center;font-size:smaller;" |''See [[Special:Recentchanges|Recent changes]] for all changes.''
|-
! Recent Updates
|-
|<dpl>
namespace=|UE1|UE2|UE3
count=5
ordermethod=lastedit
order=descending
mode=userformat
adduser=true
addeditdate=true
userdateformat=g:ia D, M j
format=<ul>,<li>[[%PAGE%|%TITLE%]]<br />%USER% - %DATE%,</li>,</ul>
noresultsheader=''None''
</dpl>
|-
! New Pages
|-
|<dpl>
namespace=|UE1|UE2|UE3
count=5
ordermethod=firstedit
order=descending
adduser=true
addeditdate=true
userdateformat=g:ia D, M j
format=<ul>,<li>[[%PAGE%|%TITLE%]]<br />%USER% - %DATE%,</li>,</ul>
noresultsheader=''None''
</dpl>
|-
! Recent Discussion
|-
|<dpl>
namespace=Talk|UE1_talk|UE2_talk|UE3_talk|Unreal_Wiki_talk|Category_talk|Legacy_talk
count=5
ordermethod=lastedit
order=descending
mode=userformat
adduser=true
addeditdate=true
userdateformat=g:ia D, M j
format=<ul>,<li>[[%PAGE%|%TITLE%]]<br />%USER% - %DATE%,</li>,</ul>
noresultsheader=''None''
</dpl>
|}
|}

Legacy:Home Page

2008-07-09T19:06:27Z

Haarg: minor change to test db issue

Welcome to the Unreal Wiki. The Unreal Wiki is dedicated to gathering documentation on the Unreal Engine. Not only can you browse the large quantity of material already here, but anyone can add or edit information instantly – no registration required. A [[:Category:Legacy Personal Page|large community]] of mappers, coders and modelers helps in this effort. [[Legacy:New Contributors Quick Start|Find out how]].

Need help finding your way around? Read [[Legacy:Using The Wiki|Using The Wiki]] to get started, or use the [[Legacy:Search|Search]] function. Use the ''Quick Navigation'' menu at the top to navigate within a page. To find out more about how the site operates, see the [[Legacy:MetaTopics|MetaTopics]] page.

See [[Legacy:Recent Changes|Recent Changes]] for local news, and [[Legacy:Featured Pages|Featured Pages]] for a rundown of what's new and cool.

{{innerbox|
'''Never use an offline reader to download the entire Unreal Wiki. If you do, we will ban you instantly and permanently.''' Offline readers put an insane stress on the web server because they follow each and every of the processing-intensive maintenance links on the Wiki that are used seldomly by real people. Don't say you haven't been warned.

We're providing the entire Wiki content as a '''convenient single download on [[Legacy:Offline Wiki|Offline Wiki]]''' though. It's smaller, zipped and downloads faster than what any offline reader could give you. Of course you can also save individual pages using your web browser without problems.
}}

==Tutorials ==

The Unreal Wiki holds many tutorials on a variety of subjects. Here are some starting points:
* [[Legacy:Terminology|Terminology]] gives a glossary of Unreal terms. Refer to this if you come across an unknown Unreal term here or on other sites. Consider this the Unreal Engine dictionary.
* [[Legacy:Mapping Lessons|Mapping Lessons]] – Start here if new to UnrealEd
* [[Legacy:UnrealScript Lessons|UnrealScript Lessons]] – Start here if new to scripting
* [[Legacy:Unreal Mapping FAQ|Unreal Mapping FAQ]]
* [[:Category:Legacy Tutorial|Search For All Tutorials]]

==Encyclopædia ==

===Mapping ===

These pages organize information on using UnrealEd to make maps into separate topic areas.

[[Legacy:Topics On Mapping|Topics on Mapping]] is the starting point for anything about map creation in Unreal. Here's a quick selection:
* [[Legacy:UnrealEd Interface|UnrealEd Interface]] – Reference for windows, menus and widgets
* [[Legacy:Map Optimization|Map Optimization]]
* [[Legacy:Texture Topics|Texture Topics]] – Using and making them
* [[Legacy:Lighting|Lighting]]
* [[Legacy:Dynamics|Dynamics]] – Triggers, sounds, music, things that react and change in maps
* [[Legacy:Mover Topics|Mover Topics]] – Doors, lifts, brushes that move
* [[Legacy:Bot Support|Bot Support]]
* [[Legacy:Gametype|Gametype]] – Specifics about mapping for gametypes and mods

===Coding ===

Covers how to write new code for the Unreal series of games. For the most part, this is done in the custom scripting language UnrealScript, although it can also be done in other languages such as C++ or Java.
* [[Legacy:UnrealScript|UnrealScript]] – Unreal's scripting language
* [[Legacy:Unreal Engine|Unreal Engine]]
* [[Legacy:Native Coding|Native Coding]] – Making DLL files for Unreal.
* [[Legacy:Class Tree|Class Tree]]
* [[Legacy:Making Mods|Making Mods]] and [[Legacy:Mutator Topics|Mutator Topics]]
* [[Legacy:Vehicles|Vehicles]]
* [[Legacy:Karma|Karma]]
* [[Legacy:Artificial Intelligence|Artificial Intelligence]] and [[Legacy:AI Scripting|AI Scripting]] – Monsters and NPCs

===Modeling ===

Links found in this section explain techniques used in modeling. This entails modeling of players, weapons and static meshes as well as skinning and getting your model ingame.
* [[Legacy:Topics On Modeling|Topics On Modeling]]
* [[Legacy:Unreal Modeling FAQ|Unreal Modeling FAQ]]

==Unreal Topics ==
* [[Legacy:New Features In UT200X|New Features In UT200X]]
* [[Legacy:Open Source|Open Source]]
* [[Legacy:Making Mods|Making Mods]]
* [[Legacy:Distribution|Distribution]]
* [[Legacy:Third-Party Components|Third-Party Components]] – Extra goodies to add to maps
* [[Legacy:Application|Application]] – Stuff to make life with UnrealEd a little smoother
* [[Legacy:Troubleshooting|Troubleshooting]] – Problems with UnrealEd itself and with maps
* [[Legacy:External Links|External Links]]

==Wiki Community ==
* [[Legacy:Mod Ideas|Mod Ideas]] – the UT200X Mod braintank.
* [[Legacy:Map Ideas|Map Ideas]] – the UT/UT200X Map braintank.
* [[:Category:Legacy Journal|Journals]] – Mappers and coders write about their learning curves.
* [[:Category:Legacy Rant|Rants]] – Wikizens' views of the (Unreal Engine) world.
* [[:Category:Legacy Personal Page]]
* [[Legacy:Log In|Log in]]
* irc://irc.enterthegame.com#unrealwiki

==Contact ==

Questions comments about the site? E-mail a [[Legacy:Wiki Admin|Wiki Admin]] or visit the [http://forums.beyondunreal.com/forumdisplay.php?forumid=249 Unreal Wiki forum].

==Editing this Page==
* [[:{{SUBJECTSPACE}}:{{BASEPAGENAME}}/Discuss]] – Suggestions for edits to this page
* [[:{{SUBJECTSPACE}}:{{BASEPAGENAME}}/Changes]] – An editable copy of this page

----

See [[Legacy:Project Copyright|Project Copyright]] for copyright information.

Category talk:Programming tutorials

2008-05-12T20:28:59Z

Haarg: New page: computergod666: WHAT ON EARTH HAPPENED?!! The site switches engines and all the UT-related information is gone! Not sheerly out of curiosity, where do I go for it now? :Try doing a search....

computergod666: WHAT ON EARTH HAPPENED?!! The site switches engines and all the UT-related information is gone! Not sheerly out of curiosity, where do I go for it now?
:Try doing a search. — [[User:Haarg|Haarg]] 20:28, 12 May 2008 (UTC)

Category:Programming tutorials

2008-05-12T20:28:45Z

Haarg:

This [[Project:Categories|category]] contains a list of all programming-related tutorials created on {{SITENAME}} so far.

[[Category:Tutorials| {{PAGENAME}}]]
[[Category:Programming articles| {{PAGENAME}}]]

UE2:RandomTrigger

2008-05-09T18:50:52Z

Haarg: updated due to changes to class infobox

{{Infobox class
| class = RandomTrigger
| custom = yes
| parent1 = Triggers
| parent2 = Actor
}}

This custom trigger will cause random events to fire from a dynamic list of event names.

==Properties==
===Main===
;array<name> EventList : A dynamic array of Events to trigger.

==Source Code==
<uscript>
//=============================================================================
// RandomTrigger
// Uses a random value to select from a dynamic array of Events when triggered.
// by SuperApe -- Sept 2005
//=============================================================================
class RandomTrigger extends Triggers
placeable;

var() array<name> EventList;

event Trigger( Actor Other, Pawn EventInstigator )
{
Event = EventList[ FRand() * EventList.length ];
TriggerEvent( Event, Other, EventInstigator );
}

//defaultproperties
//{
// Texture=Texture'Engine.S_Trigger'
//}
</uscript>

==Notes==
If this actor is compiled inside the Unreal Editor, edit the default property Display -> Texture manually as indicated in the comment at the bottom of the code using the <tt>"editdefault class=RandomTrigger"</tt> Unreal Editor console command. If you are [[Legacy:Compiling With UCC|Compiling with UCC]], simply un-comment the defaultProperties block.

==Related Topics==
* [[Legacy:Trigger Systems|Trigger Systems]]
* [[Legacy:Dynamics|Dynamics]]
* [[Legacy:Event|Event]] and [[Legacy:Tag|Tag]]
* [[Legacy:Dynamic Array|Dynamic Array]]
* [[Legacy:Third-Party Components|Third-Party Components]]

UE2:TeamVehicleFactory

2008-05-09T18:50:38Z

Haarg: updated due to changes to class infobox

__TOC__
This custom actor really duplicates much of the functionality of the ONSVehicleFactory subclasses, but the big feature is that nearly any vehicle class can be spawned. Although this actor cannot display the selected vehicle class in the editor, it does offer added controls that mappers for VCTF or other vehicle gametypes might want.

==Features==
* The ability to spawn random vehicles from a list of vehicle classes
* The ability to spawn nearly any vehicle class in gametypes that allow vehicles
* The ability to trigger PreSpawn and (Post)Spawn events
* The option to allow the vehicle to spawn over and crush other actors
* The option to use this as either a triggerable or an automatic (timed) vehicle factory.
* Greater control over spawn timing

==Notes==
* If you use a TeamVehicleFactory "as is" in your custom map, please credit me in the readme file of the map. ('''SuperApe''')
* You have to supply spawning effects and sounds, via [[Legacy:ScriptedTrigger|ScriptedTrigger]], [[Legacy:Emitter|Emitter]] and the like. This is meant to allow flexibilty in the ways you want vehicles to spawn. An example VCTF map posted on [http://unrealplayground.com/forums/showthread.php?t=23515 this UP Forum thread] gives my suggestion for spawning particles and sound. (It appears similar to pickup spawning.)
* With bAutoSpawn on and without a PreSpawnTime of around 2 seconds, you run the risk of spawning a vehicle before headlights can be properly spawned at map start. Subsequent vehicles after map start will spawn headlights normally.
* Turrets that are spawned automatically get an AIController. They are auto turrets; firing at enemies, or if set to neutral (team 255), firing at any non-neutral controlled pawn it detects.
* The AS Spacefighters are spawned with a minimum velocity that makes them impractical to use. However, a custom launcher for these is easy to make with a TryToDrive() function.
* This has a slightly larger bBlocked check radius than ONSVehicleFactory. ( 1.33 : 1.25 )

==Properties==

===Main===
; int TeamNum : Team Number to be set on spawn. 0= red, 1= blue, 255= neutral / none
; bool bPlayerControl : Only player instigators can trigger.
; bool bAutoSpawn : Will spawn at regular intervals. The triggering ability is disabled.
; int RespawnTime : Interval to wait before AutoSpawning.

; name PreSpawnEvent : Event to trigger before spawn.
; int PreSpawnTime : Time before spawn to trigger event. Will begin event this many seconds before the factory is set to AutoSpawn.
; name SpawnEvent : Event to trigger after spawn. A post spawn event.
; bool bCrushable : Allow spawning over colliding actors. Note: Turrets will normally spawn in collision with other actors, spawned vehicles will generally move out of the way.
; int RetrySpawnTime : Interval to wait if bBlocked.
; bool bRandomFlip : Neutral vehicles may face backwards.
; bool bRandomSpawn : Will spawn random vehicle class.
; struct class<[[Legacy:Vehicle|Vehicle]]> SpawnedVehicle : Selected random vehicle class.
; array<SpawnedVehicle> RandomVehicles : List for random vehicle spawn.

===Hidden===
; bool bWaiting : Waiting to spawn.
; int FactoryTime : Time last spawn. (in Level.TimeSeconds)
; bool bPreSpawn : Should trigger PreSpawnEvent next.

==Code==
{{Infobox class
| class = TeamVehicleFactory
| custom = yes
| parent1 = SVehicleFactory
| parent2 = Actor
}}
<uscript>
//==================================================================================
// TeamVehicleFactory.
// Spawn any Vehicle or Turret, set Team, pre & post spawn Events, timing, and more.
// Glenn 'SuperApe' Storm -- June 2004 -- Updated: July 2005
//==================================================================================
class TeamVehicleFactory extends SVehicleFactory
placeable;

var() int TeamNum; // 0= red, 1= blue, 255= neutral / none
var() bool bPlayerControl; // Only player instigators can trigger

var() bool bAutoSpawn; // Will spawn at regular intervals
var() int RespawnTime; // Interval to wait before AutoSpawning

var bool bWaiting; // About to spawn
var int FactoryTime; // Time last spawn

var() name PreSpawnEvent; // Event to trigger before spawn
var() int PreSpawnTime; // Time before spawn to trigger event
var bool bPreSpawn; // Should trigger PreSpawnEvent next
var() name SpawnEvent; // Event to trigger after spawn

var() bool bCrushable; // Allow spawning over colliding actors
var() int RetrySpawnTime; // Interval to wait if bBlocked

var() bool bRandomFlip; // Neutral vehicles may face backwards

var() bool bRandomSpawn; // Spawn random vehicle class

struct SpawnedVehicle
{
var() class<Vehicle> SpawnVehicle; // Selected random vehicle class
};
var() array<SpawnedVehicle> RandomVehicles; // List for random vehicle spawn

simulated function PostBeginPlay()
{
Super.PostBeginPlay();

if ( bAutoSpawn )
bWaiting = true;
bPreSpawn = true;
if ( RespawnTime > 0 )
FactoryTime = Level.TimeSeconds - RespawnTime + PreSpawnTime;
else
FactoryTime = Level.TimeSeconds - PreSpawnTime;
}

simulated event Trigger( Actor Other, Pawn EventInstigator )
{
if ( bAutoSpawn )
// bAutoSpawn overrides Trigger
return;

if ( !EventInstigator.IsA('UnrealPawn') && bPlayerControl )
return;

if ( VehicleCount >= MaxVehicleCount )
return;

if ( VehicleClass == None || ( bRandomSpawn && RandomVehicles.length > 0 ) )
{
Log("TeamVehicleFactory:"@self@"has no VehicleClass");
return;
}

bWaiting = true;
bPreSpawn = true;
if ( RespawnTime > 0 )
FactoryTime = Level.TimeSeconds - RespawnTime + PreSpawnTime;
else
FactoryTime = Level.TimeSeconds - PreSpawnTime;
}

simulated function SpawnItNow()
{
local Vehicle CreatedVehicle;
local bool bBlocked;
local Pawn P;
local float SV;

bBlocked = false;

if ( VehicleClass != None || ( bRandomSpawn && RandomVehicles.length > 0 ) )
{
if ( bRandomSpawn && RandomVehicles.length > 0 )
VehicleClass = RandomVehicles[ int( FRand() * RandomVehicles.length ) ].SpawnVehicle;
foreach CollidingActors(class'Pawn', P, VehicleClass.default.CollisionRadius * 1.33)
bBlocked = true;
}
else
{
Log("TeamVehicleFactory:"@self@"has no VehicleClass");
return;
}

if ( bBlocked && !bCrushable )
{
bWaiting = true;
bPreSpawn = true;
if ( RespawnTime > 0 )
FactoryTime = Level.TimeSeconds - RespawnTime + RetrySpawnTime + PreSpawnTime;
else
FactoryTime = Level.TimeSeconds - RetrySpawnTime + PreSpawnTime;
return;
}
else
{
if ( TeamNum == 255 )
{
if ( bRandomFlip && Rand(2) == 1 )
CreatedVehicle = spawn(VehicleClass, , , Location, Rotation + rot(0,32768,0));
else
CreatedVehicle = spawn(VehicleClass, , , Location, Rotation);

// Unlock neutral vehicles
CreatedVehicle.bTeamLocked = false;
}
else
CreatedVehicle = spawn(VehicleClass, , , Location, Rotation);

if ( CreatedVehicle != None )
{
VehicleCount++;
CreatedVehicle.Event = Tag;
CreatedVehicle.ParentFactory = self;
CreatedVehicle.SetTeamNum(TeamNum);
TriggerEvent(SpawnEvent, self, None);
}
}
}

event VehicleDestroyed(Vehicle V)
{
Super.VehicleDestroyed(V);

if ( bAutoSpawn )
{
bWaiting = true;
bPreSpawn = true;
FactoryTime = Level.TimeSeconds;
}
}

simulated function Tick(float DeltaTime)
{
if ( bWaiting )
{
if ( Level.TimeSeconds - FactoryTime < RespawnTime - PreSpawnTime )
return;

if ( VehicleCount < MaxVehicleCount )
if ( !bPreSpawn )
{
if ( Level.TimeSeconds - FactoryTime >= RespawnTime )
{
bWaiting = false;
FactoryTime = Level.TimeSeconds;
SpawnItNow();
}
}
else
{
bPreSpawn = false;
TriggerEvent(PreSpawnEvent, self, None);
}
}
}

simulated function Reset()
{
local Vehicle V;

if ( VehicleCount > 0 )
forEach AllActors ( class 'Vehicle', V )
if ( V.ParentFactory == self )
V.Destroy();
Super.Reset();
}
</uscript>

==External Links==
* [http://forums.unrealplayground.com/showthread.php?t=23515 Mapping for VCTF] – A thread on UnrealPlayground that includes a test map using this actor and suggested spawn EFX.

==Related Topics==
* [[Legacy:Third-Party Components|Third-Party Components]]
* [[Legacy:Mapping For AS (UT2004)|Mapping for AS (UT2004)]]
* [[Legacy:Mapping For ONS|Mapping for ONS]]
* [[Legacy:Mapping For VCTF|Mapping for VCTF]]
* [[User:SuperApe/Mapping For OSM Adventure|Mapping for OSM Adventure]] ''(Note: A version of TeamVehicleFactory is included in OSMT)''
* [[Legacy:Pathing For Vehicles|Pathing For Vehicles]]
* [[Legacy:Pathing 2k4 Flying Vehicles|Pathing 2k4 Flying Vehicles]]
* [[Legacy:Vehicles|Vehicles]] – Hub for all vehicle topics
** [[Legacy:Vehicle|Vehicle]] – UT2004 parent class for all vehicles and turrets
** [[Legacy:Vehicle Gameplay|Vehicle Gameplay]] – Placing VehicleFactories for strong [[Legacy:Map Flow|Map Flow]]

UE2:DMRosterBeatTeam (UT2004)

2008-05-09T18:50:10Z

Haarg: updated due to changes to class infobox

{{infobox class
| package = XGame
| parent1 = xDMRoster
| parent2 = DMRoster
| parent3 = UnrealTeamInfo
| parent4 = TeamInfo
| parent5 = ReplicationInfo
| parent6 = Info
| parent7 = Actor
}}
This special roster subclass is used to populate an enemy team with the player's selected teammates.

==Instance functions==
====Initialize====
function '''Initialize''' ([[int]] '''TeamBots''')
{| class="list"
|-
! Overrides:
| [[{{samegame|xDMRoster}}#Initialize|xDMRoster.Initialize]]
|}
Called immediately after spawning the roster class.

'''Parameters:'''
* ''TeamBots'' - Number of bots to add.

UE2:AnotherPawn

2008-05-09T18:49:08Z

Haarg: updated due to changes to class infobox

__TOC__

A generic pawn that can be spawned by a [[UE2:PawnFactory|PawnFactory]]. It holds a variable of the factory that created the pawn.

==Properties==
===Visible===
; [[UE2:PawnFactory|PawnFactory]] ParentFactory : The factory that created the pawn.

==Functions==
; Destroyed() (simulated) : Responsible for telling the pawns factory that is has been destroyed.

==Code==
{{Infobox class
| class = AnotherPawn
| custom = yes
| parent1 = xPawn
| parent2 = UnrealPawn
| parent3 = Pawn
| parent4 = Actor
}}
<uscript>
// ============================================================================
// AnotherPawn
// Copyright (c) 2006 by Andrew Fyfe <andrew@neptune-one.net>
// This program is free software; you can redistribute and/or modify
// it under the terms of the Lesser Open Unreal Mod License version 1.1.
//
// A generic pawn that can be spawned by a PawnFactory.
// ============================================================================

class AnotherPawn extends xPawn
abstract;

// ============================================================================
// Properties
// ============================================================================

var PawnFactory ParentFactory; // The factory that created the pawn.

// ============================================================================
// Destroyed
// ============================================================================

simulated function Destroyed()
{
// If we were made in a factory, tell them we're dead :(
if ( ParentFactory != None )
ParentFactory.PawnDestroyed( self );

super.Destroyed();
}

// ============================================================================
// Defaults
// ============================================================================

DefaultProperties
{
}
</uscript>

==Related Topics==
*[[UE2:PawnFactory|PawnFactory]]

UE1:Authorizer

2008-05-09T18:48:32Z

Haarg: updated due to changes to class infobox

__TOC__

==About==
This is very old script I've created to Skaarj Evasion TC (RIP). As a base was used KeyMover tutorial from [http://chimeric.beyondunreal.com/tutorials/tut11.html Chimeric].

==Properties==
===Visible===
; class<inventory> KeyClass : key class to search in players inventory
; bool bDestroyKey : should key be deleted from inventory
; bool bCheckKeyOnceOnly : if true and key was found, this class starts acting like standard trigger
; bool bShowSuccessMessage : if true will show message when key was found
; bool bShowFailtureMessage : if true will show message when key can not be found
; localized String SuccessMessage : message visible when player has a key
; localized String FailtureMessage : message visible when player don't have a key

===Hidden===
; bool bWasOpened : true if key was found and bCheckKeyOnceOnly is set to true

==Source Code==
{{Infobox class
| class = Authorizer
| custom = yes
| parent1 = Triggers
| parent2 = Actor
}}
<uscript>
//=================================================
// Authorizer: This Trigger can replace
// KeyMover (as base I use KeyMover avidible
// form http://chimeric.beyondunreal.com/tutorials/tut11.html).
//=================================================
// by Raven
// http://turniej.unreal.pl/rp
// for The Chosen One SP mod
//=================================================
class Authorizer extends Trigger;

var() class<inventory> KeyClass;
var() bool bDestroyKey;
var() bool bCheckKeyOnceOnly;
var() bool bShowSuccessMessage;
var() bool bShowFailtureMessage;
var() localized String SuccessMessage;
var() localized String FailtureMessage;
var bool bWasOpened;

replication
{
// Variables the server should send to the client.
reliable if( Role==ROLE_Authority )
bWasOpened;
}

function Touch( actor Other )
{
local Inventory key;
local actor A;

if (Other.IsA('Pawn') && KeyClass != none && !bWasOpened)
{
key = Pawn(Other).FindInventoryType(KeyClass);

if (key != none && Event != '' && !bCheckKeyOnceOnly)
foreach AllActors( class 'Actor', A, Event )
A.Trigger( Other, Other.Instigator );

if(bDestroyKey)
if(!bWasOpened) Pawn(Other).DeleteInventory(key);
if(bCheckKeyOnceOnly)
bWasOpened=true;
}
if(bWasOpened && Event != '')
foreach AllActors( class 'Actor', A, Event )
A.Trigger( Other, Other.Instigator );
if(bShowSuccessMessage && PlayerPawn(Other) != none)
PlayerPawn(Other).ClientMessage(SuccessMessage);
if(bShowFailtureMessage && !bWasOpened)
PlayerPawn(Other).ClientMessage(FailtureMessage);
}

defaultproperties
{
bShowFailtureMessage=True
SuccessMessage="Access granded."
FailtureMessage="You need a key to open this door."
}

</uscript>

UE1 talk:Authorizer

2008-05-03T20:54:21Z

Haarg: New page: Can this be moved out of Legacy and to UE1:Authorizer? ~~~~

Can this be moved out of Legacy and to [[UE1:Authorizer]]? – [[User:Haarg|Haarg]] 20:54, 3 May 2008 (UTC)

Legacy:Hellkeeper

2008-05-01T15:34:31Z

Haarg: Redirecting to User:Hellkeeper

#REDIRECT [[User:Hellkeeper]]

Legacy talk:Fyfe/PawnFactory

2008-04-29T17:24:29Z

Haarg: New page: TeamVehicleFactory bears absolutely no connection to Fyfe's Pawn Factory. What were you intending here, Haarg? -- SuperApe 09:26 (PST) 29 April 2008. Whoops. Copy/past...

TeamVehicleFactory bears absolutely no connection to Fyfe's Pawn Factory. What were you intending here, Haarg? -- [[User:SuperApe|SuperApe]] 09:26 (PST) 29 April 2008.

Whoops. Copy/paste error when resolving the double redirects. – [[User:Haarg|Haarg]] 17:24, 29 April 2008 (UTC)

Legacy:Fyfe/PawnFactory

2008-04-29T17:23:15Z

Haarg: Redirecting to UE2:PawnFactory

#REDIRECT [[UE2:PawnFactory]]

Legacy:OlympusMons

2008-04-29T15:29:37Z

Haarg: Redirecting to User:OlympusMons

#REDIRECT [[User:OlympusMons]]

Legacy talk:OlympusMons

2008-04-29T15:28:40Z

Haarg: New page: To suggest a page for deletion, use the {{delete}} template. In this case, I'm going to redirect the page. ~~~~

To suggest a page for deletion, use the {{[[Template:delete|delete]]}} template. In this case, I'm going to redirect the page. – [[User:Haarg|Haarg]] 15:28, 29 April 2008 (UTC)

UE2 talk:UT2k4Mod.ini

2008-04-29T09:51:41Z

Haarg:

Oh shi... Meant to have a lowercase I on the UT2k4Mod.ini :\ -[[User:OlympusMons|OlympusMons]] 03:20, 29 April 2008 (UTC)

Yeah I wasnt sure if I should move it again since that would be a double redirect from [[legacy:UT2k4Mod.Ini|UT2k4Mod.Ini]], but its done now now anyways :p -[[User:OlympusMons|OlympusMons]] 04:49, 29 April 2008 (UTC)

It's easy enough to fix double redirects. They are listed on [[Special:DoubleRedirects]]. I went through and cleared all the existing ones. – [[User:Haarg|Haarg]] 09:39, 29 April 2008 (UTC)

Yups saw that, good stuff. Didnt realize there was anymore. Actually while Im here, is there a way to remove chat pages like this one since its not really needed anymore? Is it just a category delete thingo? -[[User:OlympusMons|OlympusMons]] 09:48, 29 April 2008 (UTC)
: Sometimes it's fine to just clear the contents of the page. At some point, I'll probably try to set up some templates for archiving These pages like is done on Wikipedia. – [[User:Haarg|Haarg]] 09:51, 29 April 2008 (UTC)

UE2 talk:UT2k4Mod.ini

2008-04-29T09:39:46Z

Haarg:

Category:Custom UE1-specific classes

2008-04-29T09:12:46Z

Haarg: New page: {{category game classes|UE1|Unreal Engine 1|custom=yes}}

Legacy:UT2k4Mod.Ini

2008-04-29T09:06:45Z

Haarg: removing double redirect

#REDIRECT [[UE2:UT2k4Mod.ini]]

Legacy:Scratchpad

2008-04-29T09:06:24Z

Haarg: removing double redirect

#REDIRECT [[Project:Scratchpad]]

Legacy:El Muerte TDS

2008-04-29T09:05:56Z

Haarg: removing double redirect

#REDIRECT [[User:ElMuerte]]

Legacy:El Muerte

2008-04-29T09:05:30Z

Haarg: removing double redirect

#REDIRECT [[User:ElMuerte]]

Legacy:TeamVehicleFactory

2008-04-29T09:05:13Z

Haarg: removing double redirect

#REDIRECT [[UE2:TeamVehicleFactory]]

Legacy:Fyfe/PawnFactory

2008-04-29T09:04:49Z

Haarg: Redirecting to UE2:TeamVehicleFactory

#REDIRECT [[UE2:TeamVehicleFactory]]

Legacy:Fyfe/AnotherPawn

2008-04-29T09:04:31Z

Haarg: removing double redirect

#REDIRECT [[UE2:AnotherPawn]]

UE2 talk:UT2004 Default.ini

2008-04-29T09:03:10Z

Haarg:

I'd think this page should be [[UE2:Default.ini (UT2004)]] instead. – [[User:Haarg|Haarg]] 09:03, 29 April 2008 (UTC)

UE2:UT2k4Mod.ini

2008-04-29T09:01:07Z

Haarg:

The '''UT2k4Mod.ini file''' is used when creating a mod using the inbuilt mod system included with [[UT2004]]. It contains descriptions and links to your mod, a logo, and even your mod's url.

When running with the '''-mod=''' command line switch, [[UT2004]] will look for this file in your C:\UT2004\'''YourMod'''; if found it will load the custom '''ini''' file.

{{ambox|type=notice|text= In truth, the content of this file is only referenced by the "User Mods" tab of the community menu. Think of it as the "definition" file for you mod. It contains the the various text and options needed to fill out that menu. – UDN
}}

==General Information on the UT2k4Mod.ini==
;[Mod] : This is the section header and it *MUST* be the first item of your UT2K4MOD.ini file. Without it your mod will not display.
;ModTitle : This is the title of the mod and will be displayed in the select list of the "User Mods" tab.
;ModLogo : This is the full name (ie: Package.texture) of the image to be displayed on the "User Mods" tab of the community menu when someone selects your mod. The texture should be 512x128.
;ModDesc : This options sets the description that will show in the box on the "User Mods"tab. You can use the pipe character "|" to add line breaks to the display.
;ModCmdLine : This is the command line that will be used to launch your mod. You do not need to include the "–mod=" as it will be auto-appended.
;ModURL : This is a hyperlink to a web site for your mod.

Template

<source lang=ini>

[Mod]

ModTitle=

ModLogo=

ModDesc=

ModCmdLine=

ModURL=
</source>

==Related Topics==
* [[Legacy:Set Up Package Folders|Set Up Package Folders]]
* [[Legacy:Game Ini File|Game Ini File]]
**[[Legacy:UT2004.Ini|UT2004.ini]]
***UT2k4Mod.ini
***[[UE2:UT2004 Default.ini|UT2004 Default.ini]] – Used for generating UT2004.ini's
***[[Legacy:UT2k4 DefaultUser.Ini|UT2k4 DefaultUser.ini]] – Used for generating User.ini's<br><br>

==External Links==
:*[[udn2:ImprovedModSupport|Improved Mod Support]]

UE2 talk:Using the UT2004 mod system

2008-04-28T00:18:21Z

Haarg:

Hey, OlympusMons. Hold up a minute. This is the Legacy page. As far as any plan has been discussed for the new wiki structure, these pages are not supposed to be edited more than minor, minor spelling and corrections. This is not supposed to be changed to fit the new pages. As I understand it (and please, someone / anyone correct me if I'm wrong here), if you want Legacy content on the new pages, copy the content, do not permanently change the Legacy. If I am understanding the intentended methodology, Legacy content will be retained *largely unchanged* to maintain external links and the overall Legacy structure. If you begin to change Legacy pages in the way I see you doing, very soon that Legacy structure will be lost forever. Even if flawed, it's the only working wiki we have atm. The new pages can be whatever you want, but changing the Legacy pages in this way will disrupt that methology. We should revert these changes here and start proper new pages based on this content, yeah? -- [[User:SuperApe|SuperApe]] 07:04 (PST) 26 April 2008.

Correct, these pages should not be modified to fit the new structure. A better thing to do would be to create a Using the Mod System under the UT2004 namespace. [[UT2004:Using the Mod System]]. --[[User:Sir Brizz|Sir Brizz]] 14:32, 26 April 2008 (UTC)

:Actually the page name would be something like [[UE2:Using the UT2004 mod system]]. There's no "UT2004" namespace, only a UE2 one. "UT2004:..." would simply be a page in the main article space. -[[User:Wormbo|Wormbo]] 17:54, 26 April 2008 (UTC)

: ah, thanks :) --[[User:Sir Brizz|Sir Brizz]] 18:35, 26 April 2008 (UTC)

Ahh thanks for the reply, well the main reason Im editing the legacy one is cause Im the original author anyways and the old version didnt correspond to the legacy license. Like it has source materials from other sites on there directly copied and pasted which as far as I know goes against what the old license says, so now its more my own words and has a better structure. I am planning to bring it out of the legacy namespace once I know its all okay to do so, which is about now it seems but I would still like to get some thoughts on the new structure of the page etc to see if it conforms to what we are looking to do now. Either way I think the page needed to be brought up to scratch and has been on my todo list so since I havent found anything better to do to help out, I just went ahead and started editing, to note this page can always be reverted once it comes out of the legacy namespace or perhaps I can edit the links in the legacy stuff to link to it under the new namespace. This article/tutorial is some what specific to UT2004 and UE2.5, Im not sure how many other games allow the use of the '''-mod=''' commandline switch. So Im not sure if you are looking to duplicate the material for both legacy and the new namespace structure or not, also this page links to alot of legacy stuff which I could help to bring out of that namespace to the new structure also -[[User:OlympusMons|OlympusMons]] 14:41, 27 April 2008 (UTC)
:If you are the original author and would like to relicense the page, it should be moved out of the Legacy namespace as soon as possible. Then others can help with updating it. If you use the move function on the page, it will automatically set up a redirect to the new page. – [[User:Haarg|Haarg]] 23:13, 27 April 2008 (UTC)
::Well I certainly want to move it out of the legacy namespace as soon as I can I was just alittle iffy cause this way now people can discuss the layout of the page instead of just going ahead and editing it as they see fit. It doesnt bother me if people want to fix some stuff but I would just prefer to get some dialog going first as the new layouts are largely up in the air atm. Like for eg, something I would like to see is breaks before a Green section so there is a whole line break in there instead of having everything bunched together, another thing I used here was indenting directly after a green heading so paragraphing will look alittle neater. Stuff like that I would like to see done instead of just having walls of text, it just goes to readability I think. Cool -[[User:OlympusMons|OlympusMons]] 23:41, 27 April 2008 (UTC)
Actually now I think about it... What new structure? Did someone do something and I missed it? Thats the whole reason Im not doing more to help out at this stage is I have no clue what this new stucture is. Oh btw copy and pasting from the legacy content would be a nono unless you are the original author correct? Speaking from a pure wiki code standpoint the old wiki code wasnt displaying the page correctly anyways, there was a glitch with the old light blue box thingos, take a look for yourselves [[http://wiki.beyondunreal.com/Legacy:Using_The_Mod_System_In_UT2004?diff=prev&oldid=9055]] -[[User:OlympusMons|OlympusMons]] 18:55, 27 April 2008 (UTC)
:For individual pages, the wiki's overall structure doesn't really matter. As long as you are using the right namespace and have an appropriate name, it is fine. As Wormbo said, a name like [[UE2:Using the UT2004 mod system]] would be appropriate for this page. I'm not sure what exactly the page was supposed to look like before, but there were likely some bugs with the conversion of the content. – [[User:Haarg|Haarg]] 23:20, 27 April 2008 (UTC)
::Yeah I figured there would be a few bugs but this specifically is what Im talking about:
{{innerbox|C:\ut2004\ut2004.exe -mod='''your mod'''

C:\ut2004\ucc.exe -mod='''your mod'''

C:\ut2004\unrealed.exe -mod='''your mod'''
}}
::Doesnt work so well it seems lolz -[[User:OlympusMons|OlympusMons]] 23:50, 27 April 2008 (UTC)
::I see. If you see that elsewhere, a quick fix would be to add 1= after innerbox| :
{{innerbox|1=C:\ut2004\ut2004.exe -mod='''your mod'''

C:\ut2004\ucc.exe -mod='''your mod'''

C:\ut2004\unrealed.exe -mod='''your mod'''
}}
::– [[User:Haarg|Haarg]] 00:18, 28 April 2008 (UTC)

Talk:Main Page

2008-04-27T23:30:44Z

Haarg:

== General layout ==

I've tried to come up with a compact initial layout and topic list. Suggestions for improvements are welcome. [[User:Wormbo|Wormbo]] 06:31, 13 March 2008 (EDT)

Actually, we need to come up with an easy-to-browse structure for overview pages of the various parts of Unreal modding. The problem here will be that either this kind of page tends to get too long or there are too many pages to click through before reaching actual content. We need to find a good mix between an sophisticated structure and quick access. The topic pages can be accompanied by [[Project:categories|categories]], navigation/info boxes (an example can be found e.g. on [[Literals]]) and disambiguation links/pages for when a user uses the Go button of the search box in the sidebar. I hope this will give you an overview of the new tools we can use to structure the Unreal Wiki. -[[User:Wormbo|Wormbo]] 07:58, 16 April 2008 (UTC)

I think we can now all agree this should have been discussed openly and decided much earlier, before the switch to MediaWiki and the subsequent disconnect with Legacy content. This discussion will likely last a while and not get the input of the entire wiki community. Seeing as I was an instrumental contributor of the old organization (which has been widely criticized as poor or no organization), I will step back, keep an eye on the progress and wait for the dust to settle. Good luck. -[[User:SuperApe|SuperApe]] 08:57 PST, 16 April 2008

Under the UnrealScript Reference topics, seeing 'Programming tutorials' seems a little out of place. Since most if not all the programming tutorials we have here will deal with UnrealScript, why not change it and the category to UnrealScript Tutorials? -[[User:DalinSeivewright|DalinSeivewright]] 15:14, 17 April 2008 (UTC)

These category things are working arnt they? Ive been around the site acouple of times now and I dont think Ive seen anything in any of the expanded tree's. Just wondering anyways, perhaps we could get some templates in there with correct names for the time being. -[[User:OlympusMons|OlympusMons]] 22:49, 17 April 2008 (UTC)

Those tree widgets only show subcategories, not pages or media. Just imagine [[:Category:UT2004-specific classes]] displaying all old UT2004 classes when you expand its subcategory [[:Category:Legacy Class (UT2004)]]! If you mean the actual categories, don't worry. I'll import the wikified class pages for UT, UT2003/4, UT3 and UE2Runtime some time this week. -[[User:Wormbo|Wormbo]] 08:35, 21 April 2008 (UTC)

Yeah I noticed that an hour or so after making that comment, I thought classes were meant to be shown in the category class tree's but they arnt, it seems to function more like a search criterea. Yeah hope things are going well on the new wikifier, should save alot of time. :)
Actually on the Topic of class tree's since Im there, whats going to happen in that respect now? Are we going to have a class tree page anymore? I imagine alot can be done with tree views now so Id wonder if it is possible to have a class tree which is actually expandable/collapsable now, since the categories dont show the classes right under their package or superclass etc -[[User:OlympusMons|OlympusMons]] 23:29, 21 April 2008 (UTC)

:Double post looolz, anyways to expand on class tree's I had a play over here: [[Unreal_Wiki:Sandbox|Sandbox]] but I think it'll need its own template or something and Im not well versed on this new wiki stuff just yet. This category list shows the pages though under the categories they fall but I couldnt get the parent class showing as a category which is why I thought it'd need a template. -[[User:OlympusMons|OlympusMons]] 16:51, 27 April 2008 (UTC)

== New wiki software / Organization ==
Various people have had questions, comments, or criticisms of this move to MediaWiki. This seems as good a place as any to discuss it, so feel free to add anything here. – [[User:Haarg|Haarg]] 21:32, 3 April 2008 (UTC)

:Well I guess my biggest concern is the wealth of existing information (namely the tutorials and class hierarchy pages) that we can't simply move over. Most if not all the pages have had at least one contributor to the page that has done at least a minor edit. Then there's the problem of not having a complete history of the older pages so while it may appear that only one individual has worked on a given page, the truth could be that at least two have worked on it but the history of the page has been lost. Then theres the problem of what we can do with new content for the older engines as we cannot add new content to these legacy pages. IMO, the class hierarchy at least could be moved over as most of the pages are simply descriptions of what the class does (which really, Copyrights should have no hold over because there's only so many ways you can describe what a class is responsible for) and have listings for each method and variable and what they're used for.

:If that really is not an option then we could go through class by class and (re-) create a class page for each of them by source. So we could have a category for each game and have a hierarchy of classes from each package. It '''would''' take a fair bit of time to complete and a decent format would need to be made up. I personally didn't like how the old formats were set up. It seemed like too much information was being thrown at you for classes such as Actor, where there are a lot of variables and methods to go through. I guess we'd have to look at how much more information we could add in the end. I'm not sure how 'definitive' our class pages were, but I'm positive we didn't have many pages for certain classes.

:On the topic of tutorials, is there any reason why we can't re-write them? If a tutorial explains how to make a new weapon based on the shock rifle (which has been over done already) we could just reinvent the wheel. The other more advanced tutorials (such as the RPG Class tutorials) could be re-written with a similar basis.

:In the end, I think keeping the older content up-to-date and easy to find/navigate through is important as many level designers and modders most likely have not moved over to UE3 and UE2 still has plenty of life left in it.

:-[[User:DalinSeivewright|DalinSeivewright]] 12:03, 4 April 2008 (UTC)
::Most of the class hierarchy could be moved over or recreated pretty simply. As for tutorials, rewriting them is probably the best solution. While that may seem like wasted effort, I don't see a better solution given the licensing issues. – [[User:Haarg|Haarg]] 17:17, 5 April 2008 (UTC)
:wow. Unreal Wiki had a makeover... This will be confusing for a while...--[[User:JeffMOD|JeffMOD]] 14:56, 5 April 2008 (UTC)
:A comment on user accounts: It probably could have been explained better, but the user accounts from the old wiki weren't converted to the new software. First, I somewhat doubt it would have been possibly technically But mainly, there was barely any information attached to the old accounts that have been worth keeping. So everyone has to create new user accounts. Additionally, anonymous edits are turned off. I would be interested in feedback on that as well. – [[User:Haarg|Haarg]] 17:17, 5 April 2008 (UTC)
::I think its a great idea. Its a good anti-spam addition that works well for the most part, although it could end up generating a lot of accounts that would only be used once (as I've found a lot of people often to go to a site where they need to sign up to contribute and only ever change one thing they've found). Also, spam bots have been known to sign up a lot so perhaps you could add CAPTCHA to the account creation process. -[[User:DalinSeivewright|DalinSeivewright]] 02:30, 6 April 2008 (UTC)
:::I don't think we need to add a captcha at this point, but that could be revisited if spam becomes a problem. – [[User:Haarg|Haarg]] 02:36, 6 April 2008 (UTC)

Two things. Having the Legacy article show up in the search kind of makes it look incredibly messy, unorganized and hard to follow. I understand that its important to stress that Users probably shouldn't do major edits to Legacy pages but somehow hiding the Legacy part of the article name would help things considerably.

Secondly I was comparing the Actor class of UT2003 with that of UT2004 and there are several differences in each. I think we should have at least one Actor page for each generation but what about games within the same generation? Should we have seperate Actor pages for UT2003 and UT2004 within the UE2 namespace or UT2003/UT2004 namespaces or should we have one full page for UT2004 and have a seperate page for the Actor class in UT2003 that just sites the major differences? -[[User:DalinSeivewright|DalinSeivewright]] 01:32, 15 April 2008 (UTC)
:Well on the topic of UE2 Id think the best option might be to have a seperate section relating to UE2.5 since its an upgrade on the engine. Both UT2003 and UT2004 are UE2 though but other engines picked up support at UE2.5 where some are based on UE2. I do know there was alittle bit of a hastle with the class tree pages because it contained info from both UE2-2.5 so each difference had to be tagged. I guess it wasnt so bad since some classes are identical between the two, the last idea sounds good to me to do full page on UT2004's Actor and a differences page for UT2003. - [[User:OlympusMons|OlympusMons]]

:::I actually change my mind. I think we should have an actor page for each version of the engine/game. This would be considerably more work (unless Wormbo finishes his class wikifier?) but it would be much 'cleaner' and dare I say sexier. Plus users won't be too confused on whether or not their on the right page if the page just sites the differences. -[[User:DalinSeivewright|DalinSeivewright]] 00:11, 17 April 2008 (UTC)

::::Might be the go hey since there are sometimes differences between builds as well so it might get very confusing later, duplicating material isnt too good but I dont think it can be helped much since of the nature of UE. -[[User:OlympusMons|OlympusMons]] 22:51, 17 April 2008 (UTC)

:::I agree with Dalin here. Each "game" (including UE2Runtime) gets its own set of class pages and corresponding categories. If the classes really have exactly the same content, we can take advantage of the template features and simply include the newest game's version of the page on all older games' versions of the same page. I already demonstrated this on [[UE2:DMRosterBeatTeam (UT2003)]], which only includes the content from [[UE2:DMRosterBeatTeam (UT2004)]]. The templates [[Template:Infobox class]] (and [[Template:Infobox class part]]) and [[Template:samegame]] used there automatically set up links to point to pages of the same game.<br/>On a semi-related note: Do we want to document defaultproperties, possibly including subobjects, on the class pages? -[[User:Wormbo|Wormbo]] 08:35, 21 April 2008 (UTC)

::::I'm in favor of having any documentation of the default properties in where the variables are documented (if at all). It would seem reasonable to have the 'default' or accepted values for a given variable where we've explained what the variable is for. I think subobjects should be included too, just as long as we can have a seperate page for that sub-object if it is really important. For example, the KPhysics object in xPawn. Without it, your Pawn fails. -[[User:DalinSeivewright|DalinSeivewright]] 05:49, 22 April 2008 (UTC)

::::Please have a look at [[UE3:UIObject (UT3)]], I've updated it with the basic default value and subobject output of the wikifier. I still need to add special parsing for struct values to link any enums or subobjects used there. Suggestions about the output are welcome. -[[User:Wormbo|Wormbo]] 09:23, 27 April 2008 (UTC)

== Mod ideas ==

I dont know where to add mod ideas...

The mod ideas section didn't really work out on the old wiki, IMHO. Would it really make sense to revive that? -[[User:Wormbo|Wormbo]] 05:54, 25 April 2008 (UTC)
:I was actually thinking the same thing and wasn't going to add it to the main page, but then I thought I'd add it anyways and see what anyone else thought. The old Mod ideas was an okay source for ideas but it ended up being a list of abandoned pages with half being discussions on the Mod idea itself and the other half being discussions on the progress of the mod, as if it was no longer an open source idea but being worked on. I'm fine with not reviving the page, but where would these mod ideas go now? -[[User:DalinSeivewright|DalinSeivewright]] 06:26, 25 April 2008 (UTC)
::Better leave mod ideas to ppl's own wiki pages -[[User:0 Kelvin|0 Kelvin]]
:::That's a pretty good idea actually. There could be a category like [[:Category:Mod ideas]] or something similar, and it could go over what to have in mind of you are proposing a mod idea. Ideas could then be posted as sub-pages of user pages. If an idea actually took off, it could be moved into a different namespace easily. – [[User:Haarg|Haarg]] 15:47, 25 April 2008 (UTC)
::::Lets go with that then :) What about Licensing issues though? Will the 'concept' of Mod Ideas have to be reworked? If a user has a great concept and someone came and used that idea down to the exact details would there be any problems/need to cite references etc. ? I'm pretty sure copyright doesn't have a hold over 'ideas', although I could be wrong. -[[User:DalinSeivewright|DalinSeivewright]] 16:09, 25 April 2008 (UTC)
::::Isn't the entire point of posting mod ideas that ''others'' should pick them up? -[[User:Wormbo|Wormbo]] 16:59, 25 April 2008 (UTC)
:::::Yes of course, but since its under the Wiki license I'm simply wondering if there should be a seperate license for the idea pages, or if there would even be a need for that. I'm guessing by your comment, there should be no problem with the licensing then? :) -[[User:DalinSeivewright|DalinSeivewright]] 18:23, 25 April 2008 (UTC)

==Category link description==
Do the Wiki Categories currently support descriptions for each page associated to the category? What I mean is, is there currently a way to associate a description of a page within a category and have that description appear in the list of pages for said category? For example:
<pre>
A
[[Apple]] - This page describes what an apple is.
O
[[Orange]] - This page describes what an orange is.
</pre>
These descriptions would be added on the page with perhaps a little tag? I'm just curious and don't really feel they're neccesary... at least at the moment. -[[User:DalinSeivewright|DalinSeivewright]] 16:23, 25 April 2008 (UTC)

No, that's not supported. This type of description needs to go in the page text, either of the category page or a more suitable topic page. -[[User:Wormbo|Wormbo]] 16:54, 25 April 2008 (UTC)

Some form of this could be done using a DPL report:<dpl>
category = Custom UE2-specific classes
include={Infobox class}:parent1
includematch=/./
secseparators= \n- Subclass of ,
</dpl>
But that would be built as a specific list, and not part of the general category page. – [[User:Haarg|Haarg]] 17:49, 25 April 2008 (UTC)

== 3rd Party / open source scripts ==

Where do they go? (O Kelvin)

: As a page with the the appropriate namespace and page name. [[UE1:RJumpPad]] for example. With a class infobox, it will be added to the appropriate categories. – [[User:Haarg|Haarg]] 23:30, 27 April 2008 (UTC)

UE2 talk:Using the UT2004 mod system

2008-04-27T23:20:59Z

Haarg:

Hey, OlympusMons. Hold up a minute. This is the Legacy page. As far as any plan has been discussed for the new wiki structure, these pages are not supposed to be edited more than minor, minor spelling and corrections. This is not supposed to be changed to fit the new pages. As I understand it (and please, someone / anyone correct me if I'm wrong here), if you want Legacy content on the new pages, copy the content, do not permanently change the Legacy. If I am understanding the intentended methodology, Legacy content will be retained *largely unchanged* to maintain external links and the overall Legacy structure. If you begin to change Legacy pages in the way I see you doing, very soon that Legacy structure will be lost forever. Even if flawed, it's the only working wiki we have atm. The new pages can be whatever you want, but changing the Legacy pages in this way will disrupt that methology. We should revert these changes here and start proper new pages based on this content, yeah? -- [[User:SuperApe|SuperApe]] 07:04 (PST) 26 April 2008.

Correct, these pages should not be modified to fit the new structure. A better thing to do would be to create a Using the Mod System under the UT2004 namespace. [[UT2004:Using the Mod System]]. --[[User:Sir Brizz|Sir Brizz]] 14:32, 26 April 2008 (UTC)

:Actually the page name would be something like [[UE2:Using the UT2004 mod system]]. There's no "UT2004" namespace, only a UE2 one. "UT2004:..." would simply be a page in the main article space. -[[User:Wormbo|Wormbo]] 17:54, 26 April 2008 (UTC)

: ah, thanks :) --[[User:Sir Brizz|Sir Brizz]] 18:35, 26 April 2008 (UTC)

Ahh thanks for the reply, well the main reason Im editing the legacy one is cause Im the original author anyways and the old version didnt correspond to the legacy license. Like it has source materials from other sites on there directly copied and pasted which as far as I know goes against what the old license says, so now its more my own words and has a better structure. I am planning to bring it out of the legacy namespace once I know its all okay to do so, which is about now it seems but I would still like to get some thoughts on the new structure of the page etc to see if it conforms to what we are looking to do now. Either way I think the page needed to be brought up to scratch and has been on my todo list so since I havent found anything better to do to help out, I just went ahead and started editing, to note this page can always be reverted once it comes out of the legacy namespace or perhaps I can edit the links in the legacy stuff to link to it under the new namespace. This article/tutorial is some what specific to UT2004 and UE2.5, Im not sure how many other games allow the use of the '''-mod=''' commandline switch. So Im not sure if you are looking to duplicate the material for both legacy and the new namespace structure or not, also this page links to alot of legacy stuff which I could help to bring out of that namespace to the new structure also -[[User:OlympusMons|OlympusMons]] 14:41, 27 April 2008 (UTC)
:If you are the original author and would like to relicense the page, it should be moved out of the Legacy namespace as soon as possible. Then others can help with updating it. If you use the move function on the page, it will automatically set up a redirect to the new page. – [[User:Haarg|Haarg]] 23:13, 27 April 2008 (UTC)
Actually now I think about it... What new structure? Did someone do something and I missed it? Thats the whole reason Im not doing more to help out at this stage is I have no clue what this new stucture is. Oh btw copy and pasting from the legacy content would be a nono unless you are the original author correct? Speaking from a pure wiki code standpoint the old wiki code wasnt displaying the page correctly anyways, there was a glitch with the old light blue box thingos, take a look for yourselves [[http://wiki.beyondunreal.com/Legacy:Using_The_Mod_System_In_UT2004?diff=prev&oldid=9055]] -[[User:OlympusMons|OlympusMons]] 18:55, 27 April 2008 (UTC)
:For individual pages, the wiki's overall structure doesn't really matter. As long as you are using the right namespace and have an appropriate name, it is fine. As Wormbo said, a name like [[UE2:Using the UT2004 mod system]] would be appropriate for this page. I'm not sure what exactly the page was supposed to look like before, but there were likely some bugs with the conversion of the content. – [[User:Haarg|Haarg]] 23:20, 27 April 2008 (UTC)

UE2 talk:Using the UT2004 mod system

2008-04-27T23:13:14Z

Haarg:

Talk:Main Page

2008-04-25T17:49:48Z

Haarg: /* Category link description */

== General layout ==

I've tried to come up with a compact initial layout and topic list. Suggestions for improvements are welcome. [[User:Wormbo|Wormbo]] 06:31, 13 March 2008 (EDT)

Actually, we need to come up with an easy-to-browse structure for overview pages of the various parts of Unreal modding. The problem here will be that either this kind of page tends to get too long or there are too many pages to click through before reaching actual content. We need to find a good mix between an sophisticated structure and quick access. The topic pages can be accompanied by [[Project:categories|categories]], navigation/info boxes (an example can be found e.g. on [[Literals]]) and disambiguation links/pages for when a user uses the Go button of the search box in the sidebar. I hope this will give you an overview of the new tools we can use to structure the Unreal Wiki. -[[User:Wormbo|Wormbo]] 07:58, 16 April 2008 (UTC)

I think we can now all agree this should have been discussed openly and decided much earlier, before the switch to MediaWiki and the subsequent disconnect with Legacy content. This discussion will likely last a while and not get the input of the entire wiki community. Seeing as I was an instrumental contributor of the old organization (which has been widely criticized as poor or no organization), I will step back, keep an eye on the progress and wait for the dust to settle. Good luck. -[[User:SuperApe|SuperApe]] 08:57 PST, 16 April 2008

Under the UnrealScript Reference topics, seeing 'Programming tutorials' seems a little out of place. Since most if not all the programming tutorials we have here will deal with UnrealScript, why not change it and the category to UnrealScript Tutorials? -[[User:DalinSeivewright|DalinSeivewright]] 15:14, 17 April 2008 (UTC)

These category things are working arnt they? Ive been around the site acouple of times now and I dont think Ive seen anything in any of the expanded tree's. Just wondering anyways, perhaps we could get some templates in there with correct names for the time being. -[[User:OlympusMons|OlympusMons]] 22:49, 17 April 2008 (UTC)

Those tree widgets only show subcategories, not pages or media. Just imagine [[:Category:UT2004-specific classes]] displaying all old UT2004 classes when you expand its subcategory [[:Category:Legacy Class (UT2004)]]! If you mean the actual categories, don't worry. I'll import the wikified class pages for UT, UT2003/4, UT3 and UE2Runtime some time this week. -[[User:Wormbo|Wormbo]] 08:35, 21 April 2008 (UTC)

Yeah I noticed that an hour or so after making that comment, I thought classes were meant to be shown in the category class tree's but they arnt, it seems to function more like a search criterea. Yeah hope things are going well on the new wikifier, should save alot of time. :)
Actually on the Topic of class tree's since Im there, whats going to happen in that respect now? Are we going to have a class tree page anymore? I imagine alot can be done with tree views now so Id wonder if it is possible to have a class tree which is actually expandable/collapsable now, since the categories dont show the classes right under their package or superclass etc -[[User:OlympusMons|OlympusMons]] 23:29, 21 April 2008 (UTC)

== New wiki software / Organization ==
Various people have had questions, comments, or criticisms of this move to MediaWiki. This seems as good a place as any to discuss it, so feel free to add anything here. – [[User:Haarg|Haarg]] 21:32, 3 April 2008 (UTC)

:Well I guess my biggest concern is the wealth of existing information (namely the tutorials and class hierarchy pages) that we can't simply move over. Most if not all the pages have had at least one contributor to the page that has done at least a minor edit. Then there's the problem of not having a complete history of the older pages so while it may appear that only one individual has worked on a given page, the truth could be that at least two have worked on it but the history of the page has been lost. Then theres the problem of what we can do with new content for the older engines as we cannot add new content to these legacy pages. IMO, the class hierarchy at least could be moved over as most of the pages are simply descriptions of what the class does (which really, Copyrights should have no hold over because there's only so many ways you can describe what a class is responsible for) and have listings for each method and variable and what they're used for.

:If that really is not an option then we could go through class by class and (re-) create a class page for each of them by source. So we could have a category for each game and have a hierarchy of classes from each package. It '''would''' take a fair bit of time to complete and a decent format would need to be made up. I personally didn't like how the old formats were set up. It seemed like too much information was being thrown at you for classes such as Actor, where there are a lot of variables and methods to go through. I guess we'd have to look at how much more information we could add in the end. I'm not sure how 'definitive' our class pages were, but I'm positive we didn't have many pages for certain classes.

:On the topic of tutorials, is there any reason why we can't re-write them? If a tutorial explains how to make a new weapon based on the shock rifle (which has been over done already) we could just reinvent the wheel. The other more advanced tutorials (such as the RPG Class tutorials) could be re-written with a similar basis.

:In the end, I think keeping the older content up-to-date and easy to find/navigate through is important as many level designers and modders most likely have not moved over to UE3 and UE2 still has plenty of life left in it.

:-[[User:DalinSeivewright|DalinSeivewright]] 12:03, 4 April 2008 (UTC)
::Most of the class hierarchy could be moved over or recreated pretty simply. As for tutorials, rewriting them is probably the best solution. While that may seem like wasted effort, I don't see a better solution given the licensing issues. – [[User:Haarg|Haarg]] 17:17, 5 April 2008 (UTC)
:wow. Unreal Wiki had a makeover... This will be confusing for a while...--[[User:JeffMOD|JeffMOD]] 14:56, 5 April 2008 (UTC)
:A comment on user accounts: It probably could have been explained better, but the user accounts from the old wiki weren't converted to the new software. First, I somewhat doubt it would have been possibly technically But mainly, there was barely any information attached to the old accounts that have been worth keeping. So everyone has to create new user accounts. Additionally, anonymous edits are turned off. I would be interested in feedback on that as well. – [[User:Haarg|Haarg]] 17:17, 5 April 2008 (UTC)
::I think its a great idea. Its a good anti-spam addition that works well for the most part, although it could end up generating a lot of accounts that would only be used once (as I've found a lot of people often to go to a site where they need to sign up to contribute and only ever change one thing they've found). Also, spam bots have been known to sign up a lot so perhaps you could add CAPTCHA to the account creation process. -[[User:DalinSeivewright|DalinSeivewright]] 02:30, 6 April 2008 (UTC)
:::I don't think we need to add a captcha at this point, but that could be revisited if spam becomes a problem. – [[User:Haarg|Haarg]] 02:36, 6 April 2008 (UTC)

Two things. Having the Legacy article show up in the search kind of makes it look incredibly messy, unorganized and hard to follow. I understand that its important to stress that Users probably shouldn't do major edits to Legacy pages but somehow hiding the Legacy part of the article name would help things considerably.

Secondly I was comparing the Actor class of UT2003 with that of UT2004 and there are several differences in each. I think we should have at least one Actor page for each generation but what about games within the same generation? Should we have seperate Actor pages for UT2003 and UT2004 within the UE2 namespace or UT2003/UT2004 namespaces or should we have one full page for UT2004 and have a seperate page for the Actor class in UT2003 that just sites the major differences? -[[User:DalinSeivewright|DalinSeivewright]] 01:32, 15 April 2008 (UTC)
:Well on the topic of UE2 Id think the best option might be to have a seperate section relating to UE2.5 since its an upgrade on the engine. Both UT2003 and UT2004 are UE2 though but other engines picked up support at UE2.5 where some are based on UE2. I do know there was alittle bit of a hastle with the class tree pages because it contained info from both UE2-2.5 so each difference had to be tagged. I guess it wasnt so bad since some classes are identical between the two, the last idea sounds good to me to do full page on UT2004's Actor and a differences page for UT2003. - [[User:OlympusMons|OlympusMons]]

:::I actually change my mind. I think we should have an actor page for each version of the engine/game. This would be considerably more work (unless Wormbo finishes his class wikifier?) but it would be much 'cleaner' and dare I say sexier. Plus users won't be too confused on whether or not their on the right page if the page just sites the differences. -[[User:DalinSeivewright|DalinSeivewright]] 00:11, 17 April 2008 (UTC)

::::Might be the go hey since there are sometimes differences between builds as well so it might get very confusing later, duplicating material isnt too good but I dont think it can be helped much since of the nature of UE. -[[User:OlympusMons|OlympusMons]] 22:51, 17 April 2008 (UTC)

:::I agree with Dalin here. Each "game" (including UE2Runtime) gets its own set of class pages and corresponding categories. If the classes really have exactly the same content, we can take advantage of the template features and simply include the newest game's version of the page on all older games' versions of the same page. I already demonstrated this on [[UE2:DMRosterBeatTeam (UT2003)]], which only includes the content from [[UE2:DMRosterBeatTeam (UT2004)]]. The templates [[Template:Infobox class]] (and [[Template:Infobox class part]]) and [[Template:samegame]] used there automatically set up links to point to pages of the same game.<br/>On a semi-related note: Do we want to document defaultproperties, possibly including subobjects, on the class pages? -[[User:Wormbo|Wormbo]] 08:35, 21 April 2008 (UTC)

::::I'm in favor of having any documentation of the default properties in where the variables are documented (if at all). It would seem reasonable to have the 'default' or accepted values for a given variable where we've explained what the variable is for. I think subobjects should be included too, just as long as we can have a seperate page for that sub-object if it is really important. For example, the KPhysics object in xPawn. Without it, your Pawn fails. -[[User:DalinSeivewright|DalinSeivewright]] 05:49, 22 April 2008 (UTC)

== Mod ideas ==

I dont know where to add mod ideas...

The mod ideas section didn't really work out on the old wiki, IMHO. Would it really make sense to revive that? -[[User:Wormbo|Wormbo]] 05:54, 25 April 2008 (UTC)
:I was actually thinking the same thing and wasn't going to add it to the main page, but then I thought I'd add it anyways and see what anyone else thought. The old Mod ideas was an okay source for ideas but it ended up being a list of abandoned pages with half being discussions on the Mod idea itself and the other half being discussions on the progress of the mod, as if it was no longer an open source idea but being worked on. I'm fine with not reviving the page, but where would these mod ideas go now? -[[User:DalinSeivewright|DalinSeivewright]] 06:26, 25 April 2008 (UTC)
::Better leave mod ideas to ppl's own wiki pages -[[User:0 Kelvin|0 Kelvin]]
:::That's a pretty good idea actually. There could be a category like [[:Category:Mod ideas]] or something similar, and it could go over what to have in mind of you are proposing a mod idea. Ideas could then be posted as sub-pages of user pages. If an idea actually took off, it could be moved into a different namespace easily. – [[User:Haarg|Haarg]] 15:47, 25 April 2008 (UTC)
::::Lets go with that then :) What about Licensing issues though? Will the 'concept' of Mod Ideas have to be reworked? If a user has a great concept and someone came and used that idea down to the exact details would there be any problems/need to cite references etc. ? I'm pretty sure copyright doesn't have a hold over 'ideas', although I could be wrong. -[[User:DalinSeivewright|DalinSeivewright]] 16:09, 25 April 2008 (UTC)
::::Isn't the entire point of posting mod ideas that ''others'' should pick them up? -[[User:Wormbo|Wormbo]] 16:59, 25 April 2008 (UTC)

==Category link description==
Do the Wiki Categories currently support descriptions for each page associated to the category? What I mean is, is there currently a way to associate a description of a page within a category and have that description appear in the list of pages for said category? For example:
<pre>
A
[[Apple]] - This page describes what an apple is.
O
[[Orange]] - This page describes what an orange is.
</pre>
These descriptions would be added on the page with perhaps a little tag? I'm just curious and don't really feel they're neccesary... at least at the moment. -[[User:DalinSeivewright|DalinSeivewright]] 16:23, 25 April 2008 (UTC)

No, that's not supported. This type of description needs to go in the page text, either of the category page or a more suitable topic page. -[[User:Wormbo|Wormbo]] 16:54, 25 April 2008 (UTC)

Some form of this could be done using a DPL report:<dpl>
category = Custom UE2-specific classes
include={Infobox class}:parent1
includematch=/./
secseparators= \n- Subclass of ,
</dpl>
But that would be built as a specific list, and not part of the general category page. – [[User:Haarg|Haarg]] 17:49, 25 April 2008 (UTC)