add missing element types and auto-redirect to old wiki

Fernando-A-Rocha · Fernando-A-Rocha · commit f4be1f7870e8 · 2025-05-23T09:58:12.000+01:00
diff --git a/elements/General/blip.yaml b/elements/General/blip.yaml
@@ -2,7 +2,5 @@ name: 'blip'
 description: |
   The blip class represents small icons or blips that can be shown on a player's radar.
 
-  The element type of this class is **"blip"**.
-
   The list of blip icons are available on the [Radar Blips](/radar_blips) page. 
 
diff --git a/elements/General/building.yaml b/elements/General/building.yaml
@@ -2,8 +2,6 @@ name: 'building'
 description: |
   The building class represents static 3D models in the GTA world.
 
-  The element type of this class is **"building"**. 
-
 notes:
     - |
       There is a distinction in GTA: San Andreas between static and dynamic models (these use a separate streaming system). Examples of buildings include building models, roads, and terrain. Objects created as [Buildings](/building) can contain **glass** and **shadows**, unlike those created as [Objects](/building) (which are missing these features).
diff --git a/elements/General/camera.yaml b/elements/General/camera.yaml
@@ -2,5 +2,3 @@ name: 'camera'
 description: |
   The camera class represents the local player camera rendering the game to the screen.
 
-  The element type of this class is **"camera"**. 
-
diff --git a/elements/General/col.yaml b/elements/General/col.yaml
@@ -8,8 +8,6 @@ description: |
   To split a .col file into multiple files, you can use [CollEditor2](http://www.steve-m.com/downloads/tools/colleditor2/).
 
   Collision data can also be embedded in DFF files. At the moment, vehicle collision replacement works with DFF embedded collisions only. 
-
-  The element type of this class is **"col"**. 
 see_also:
   - 'functions:any:Engine'
   - 'events:any:Engine'
diff --git a/elements/General/colshape.yaml b/elements/General/colshape.yaml
@@ -1,8 +1,6 @@
-name: 'collision_shape'
+name: 'colshape'
 description: |
   The collision shape class represents invisible collision detection shapes that can be created in the GTA world. Collision shapes are typically used to detect physical entities moving through them and perform actions when they do.
-
-  The element type for this class is **"colshape"**. 
 see_also:
   - 'functions:any:ColShape'
   - 'events:any:ColShape'
diff --git a/elements/General/console.yaml b/elements/General/console.yaml
@@ -2,8 +2,6 @@ name: 'console'
 description: |
   The Server Console class represents the server console.
 
-  The element type of this class is **"console"**.
-
   In the server console you can use many different commands, affecting the players using the server. Please note that only console commands can be used, and that some commands can not be used through the in-game client console, only through the Server Console. 
 
   You can view all latest available server console commands by entering **"help"** into the server console window. 
diff --git a/elements/General/dff.yaml b/elements/General/dff.yaml
@@ -4,8 +4,6 @@ description: |
 
   Collision data can also be embedded in DFF files. At the moment, vehicle collision replacement works with DFF embedded collisions only. 
 
-  The element type of this class is **"dff"**. 
-
 see_also:
   - 'functions:any:Engine'
   - 'events:any:Engine'
diff --git a/elements/General/effect.yaml b/elements/General/effect.yaml
@@ -2,6 +2,4 @@ name: 'effect'
 description: |
   The Effect class represents custom effect elements in the game world such as smoke, sparks, fire etc.
 
-  The element type of this class is **"effect"**. 
-
   TODO all effects table
diff --git a/elements/General/light.yaml b/elements/General/light.yaml
@@ -1,5 +1,3 @@
 name: 'light'
 description: |
   The light class represents colored, 3D lights in the GTA world. There are a couple different types of lights, which are point lights, spot lights and dark lights.
-
-  The element type of this class is **"light"**. 
diff --git a/elements/General/marker.yaml b/elements/General/marker.yaml
@@ -2,5 +2,3 @@ name: 'marker'
 description: |
   The marker class represents colored, 3D shapes in the GTA world. There are several types of markers, including cylinders and checkpoints. In scripts, markers are often used to mark spots and trigger some sort of action when a player goes into them.
 
-  The element type of this class is **"marker"**. 
-
diff --git a/elements/General/object.yaml b/elements/General/object.yaml
@@ -2,8 +2,6 @@ name: 'object'
 description: |
   The object class represents dynamic and static 3D models placed in the GTA world.
 
-  The element type of this class is **"object"**. 
-
 notes:
     - |
       Objects only represent models **created by a script**, they do not represent objects that are part of GTA's default landscape (these belong to the "building pool").
diff --git a/elements/General/ped.yaml b/elements/General/ped.yaml
@@ -4,5 +4,3 @@ description: |
 
   The [createPed](/createPed) function specifically creates an NPC, but all other ped functions work on both players and NPC's as they're pretty much the same thing to San Andreas. 
 
-  The element type of a NPC is **"ped"**. 
-
diff --git a/elements/General/pickup.yaml b/elements/General/pickup.yaml
@@ -2,5 +2,3 @@ name: 'pickup'
 description: |
   The pickup class represents weapon, health, or armor pickups in the GTA world. Pickups can be picked up by players when they are walked over. Players will not be given health or armor pickups if their health or armor is already full.
 
-  The element type of this class is **"pickup"**. 
-
diff --git a/elements/General/player.yaml b/elements/General/player.yaml
@@ -2,5 +2,3 @@ name: 'player'
 description: |
   The player class represents pedestrians controlled by clients. A player element is created when a client connects to the server and destroyed when that client quits. Players cannot be created or destroyed otherwise.
 
-  The element type of this class is **"player"**. 
-
diff --git a/elements/General/projectile.yaml b/elements/General/projectile.yaml
@@ -2,8 +2,6 @@ name: 'projectile'
 description: |
   The projectile class represents the projectiles of certain weapons that are created when the weapon is fired. Alternatively these can be created using [createProjectile](/createProjectile).
 
-  The element type of this class is **"projectile"**. 
-
 notes:
     - |
       **16: Grenade**
diff --git a/elements/General/radararea.yaml b/elements/General/radararea.yaml
@@ -1,9 +1,7 @@
-name: 'radar_area'
+name: 'radararea'
 description: |
   The radar area class represents coloured areas that can be displayed on a player's radar.
 
-  The element type of this class is **"radararea"**. 
-
 
 see_also:
   - 'functions:any:RadarArea'
diff --git a/elements/General/searchlight.yaml b/elements/General/searchlight.yaml
@@ -2,5 +2,3 @@ name: 'searchlight'
 description: |
   The searchlight class represents special spotlights in the GTA world. They are different to common spotlights because their visual effects.
 
-  The element type of this class is **"searchlight"**. 
-
diff --git a/elements/General/sound.yaml b/elements/General/sound.yaml
@@ -6,8 +6,6 @@ description: |
 
   Sound elements can also be manipulated using the other [Client audio functions](/client_audio_functions). 
 
-  The element type of this class is **"sound"**. 
-
 
 see_also:
   - 'functions:any:Audio'
diff --git a/elements/General/team.yaml b/elements/General/team.yaml
@@ -4,5 +4,3 @@ description: |
 
   A common misconception is that players would be child elements of team elements. This is wrong. Being part of a team is merely a relational connection rather than a change in element hierarchy. To perform logic on all the players of a team you have to use the [getPlayersInTeam](/getPlayersInTeam) function. 
 
-  The element type of this class is **"team"**. 
-
diff --git a/elements/General/txd.yaml b/elements/General/txd.yaml
@@ -2,8 +2,6 @@ name: 'txd'
 description: |
   The TXD class represents a RenderWare Texture Dictionary (TXD) loaded by the client, which can be imported into a custom model to texture it.
 
-  The element type of this class is **"txd"**. 
-
 see_also:
   - 'functions:any:Engine'
   - 'events:any:Engine'
diff --git a/elements/General/vehicle.yaml b/elements/General/vehicle.yaml
@@ -2,5 +2,3 @@ name: 'vehicle'
 description: |
   The vehicle class represents vehicles in the GTA world. Vehicles can be occupied and controlled by players and peds.
 
-  The element type of this class is **"vehicle"**. 
-
diff --git a/elements/General/water.yaml b/elements/General/water.yaml
@@ -4,5 +4,3 @@ description: |
   
   A water element represents one such polygon. You can create water elements using [createWater](/createWater).
 
-  The element type of this class is **"water"**. 
-
diff --git a/elements/General/weapon.yaml b/elements/General/weapon.yaml
@@ -2,5 +2,3 @@ name: 'weapon'
 description: |
   The Weapon class represents a custom static weapon. Weapon elements created by [createWeapon](/createWeapon) can be manipulated with the following scripting functions.
 
-  The element type of this class is **"weapon"**. 
-
diff --git a/elements/Misc/account.yaml b/elements/Misc/account.yaml
@@ -0,0 +1,10 @@
+name: 'account'
+description: |
+  The **account** class represents a [player](/player)'s server account. You can get the **account** object associated to any client using [getPlayerAccount](/getPlayerAccount).
+
+  Accounts are unique to each client and can be used to store information that is persistent across map changes and user sessions. Clients that join without an account are given a temporary 'guest' account. This can store information like any other account, but isn't saved across sessions.
+
+  When a user logs in or out, the account object assigned to them will change. As such, you must not assume that the account attached to a client remains constant during their session.
+
+  PHP code to check password hashes from the MTA server database is [here](/Account_PHP). 
+
diff --git a/elements/Misc/acl.yaml b/elements/Misc/acl.yaml
@@ -0,0 +1,16 @@
+name: 'acl'
+description: |
+  ACL or Access Control List is a set of rights grouped together to create a list, they are defined in the [ACL.xml](/Access_Control_List) file as <acl> nodes. These ACLs can then be added to certain [ACL Groups](/aclgroup) to grant or deny these groups specified permissions or acces to server scripting functions defined in the ACL. Example of an ACL:
+
+  ```xml
+  <acl name="Example">
+    <right name="general.ModifyOtherObjects" access="true" />
+    <right name="function.startResource" access="true" />
+    <right name="function.stopResource" access="true" />
+    <right name="function.shutdown" access="false" />
+    <right name="command.shutdown" access="false" />
+  </acl>
+  ```
+
+  This creates ACL called *Example* and gives resources access to start/stop resources and modify other resources but denies access to shutting down the server. Players that are in group using this ACL will be denied access to `shutdown` command. 
+
diff --git a/elements/Misc/aclgroup.yaml b/elements/Misc/aclgroup.yaml
@@ -0,0 +1,75 @@
+name: 'aclgroup'
+description: |
+  ACL Groups are groups that holds objects such as accounts, and resources which allows them to do some things depending on the permission the group has/holds.
+
+  #### Default Groups
+
+  MTA has provided some default groups with increasing permissions. These groups are:
+
+  - **Everyone**
+  - **Moderator**
+  - **SuperModerator**
+  - **Admin**
+  - **Console** - This controls permissions of people who are using the console through `<object name="user.Console" />`
+  - **RPC** - Remote Procedure Call. Specifically grants access to callRemote only and disables commands of default resources. Check the function for details.
+
+  To explain further, I will use the Everyone group as an example. By default it looks like this: 
+
+  ```xml
+  <group name="Everyone">
+    <acl name="Default" />
+    <object name="user.*" />
+    <object name="resource.*" />
+  </group>
+  ```
+
+  You will first notice the acl name inside the group. It defines what permissions the group has. Users and resources in this group will have the permissions specified on the "Default" acl name list.
+  
+  **Note**: You will notice this group is special, in that it includes every user and resource by using a **wildcard (\*)** where the user or resource name would be.
+
+  Now, scroll further down the ACL and you will see the `<acl name="Default" />` listing. Note I have trimmed this list dramatically due to its length. 
+
+  ```xml
+  <acl name="Default">
+    <right name="command.start" access="false" />
+    <right name="command.stop" access="false" />
+    <right name="command.stopall" access="false" />
+    ...etc etc...
+    <right name="function.executeCommandHandler" access="false" />
+    <right name="function.setPlayerMuted" access="false" />
+    <right name="function.restartResource" access="false" />
+    ...etc etc...
+    <right name="general.adminpanel" access="false" />
+    <right name="general.tab_players" access="false" />
+    <right name="general.tab_resources" access="false" />
+    ...etc etc...
+    <right name="command.freeze" access="false" />
+    <right name="command.shout" access="false" />
+    <right name="command.spectate" access="false" />
+    ...etc etc...
+  </acl>
+  ```
+
+  - `Function` entries are MTA scripting functions. For example, if a resource needed to use restartResource and was only in the 'Everyone' group (with the 'Default' list), it would be denied access to restartResource and fail to work correctly.
+  - `Commands` are created when a resource uses addCommandHandler. An example would be typing /createvehicle [vehicle] in the chatbox for the freeroam resource. This controls whether users in the group using this ACL can use the command. Note: commands have no effect on resources within the group. Commands are only related to users.
+  - `General` is a custom right name group created by the admin resource but it works on the same principles. The script works with them by using hasObjectPermissionTo
+
+  You will notice some groups such as admin have multiple `<acl name="" />` nodes. An example is the admin group:
+
+  ```xml
+  <group name="Admin">
+    <acl name="Moderator" />
+    <acl name="SuperModerator" />
+    <acl name="Admin" />
+    <acl name="RPC" />
+    <object name="resource.admin" />
+    <object name="resource.webadmin" />
+    <object name="user.Ransom" />
+  </group>
+  ```
+
+  This gives all the permissions defined in each <acl name="" /> node in order of listing. So for example, the admin group makes sure all the permissions are given to admins by using all the lists. If there are any conflicts, the lowest entry wins. For example, pretend these 2 acls were in a group in the following order:
+
+  - `<acl name="Default">` sets `<right name="general.ModifyOtherObjects" access="false" />`
+  - `<acl name="Admin">` sets `<right name="general.ModifyOtherObjects" access="true" />`
+  - For all users and resources in group admin: `<right name="general.ModifyOtherObjects" access="true" />`
diff --git a/elements/Misc/ban.yaml b/elements/Misc/ban.yaml
@@ -0,0 +1,3 @@
+name: ban
+description: |
+  A **ban** is a pointer that represents a banned player arbitrarily. The following functions allow interaction with a ban.
diff --git a/elements/Misc/db-connection.yaml b/elements/Misc/db-connection.yaml
@@ -0,0 +1,2 @@
+name: db-connection
+description: 'The **db-connection** class represents a database connection.'
diff --git a/elements/Misc/resource.yaml b/elements/Misc/resource.yaml
@@ -0,0 +1,6 @@
+name: resource
+description: |
+  A resource object refers to a resource that is loaded in the server.
+
+  A name, state, root element, base directory path are associated to a resource, among other attributes.
+  
diff --git a/elements/Misc/textdisplay.yaml b/elements/Misc/textdisplay.yaml
@@ -0,0 +1,5 @@
+name: textdisplay
+description: |
+  A textdisplay object refers to a "canvas" that can contain many items of text ([textitems](/textitem)).
+
+  Each display can be seen by multiple observers ([players](/player)) and each observer can see multiple displays. For example, you could have a display that showed a score, and a display that showed information specific to one team, such as the location of a flag. Every player would be an observer of the first display and each team would have their own display that its players would be observers of.
diff --git a/elements/Misc/textitem.yaml b/elements/Misc/textitem.yaml
@@ -0,0 +1,5 @@
+name: textitem
+description: |
+  A textitem object represents a single area of text, much like a label does in standard GUI programing.
+
+  A text item can only be seen by players if it is added to a [textdisplay](/textdisplay) they are observers of using [textDisplayAddText](/textDisplayAddText).
diff --git a/elements/Misc/timer.yaml b/elements/Misc/timer.yaml
@@ -0,0 +1,5 @@
+name: timer
+description: |
+  A **timer** object refers to a timer set to execute a function a certain number of times with a specified delay.
+
+  Note that after a timer has completed all its iterations, it is destroyed and any stored pointers to it become invalid. Also timers are not under the resource hierarchy, because they are not elements, for instance, if you create a timer, it will not be destroyed when the resource in which it was created is stopped, so in this case you should kill the timer manually. 
diff --git a/elements/Misc/xmlnode.yaml b/elements/Misc/xmlnode.yaml
@@ -0,0 +1,2 @@
+name: xmlnode
+description: 'A xmlnode is an object that represents a node in a XML document tree.'
diff --git a/functions/Element/getElementPosition.yaml b/functions/Element/getElementPosition.yaml
@@ -13,9 +13,9 @@ shared: &shared
     - [object](/object)
     - [pickup](/pickup)
     - [marker](/marker)
-    - [collision shapes](/collision_shapes)
+    - [collision shapes](/colshape)
     - [blip](/blip)
-    - [radar areas](/radar_areas)
+    - [radar areas](/radararea)
   parameters:
     - name: 'theElement'
       type: 'element'
diff --git a/web/src/content.config.ts b/web/src/content.config.ts
@@ -5,13 +5,6 @@ import { glob } from 'astro/loaders';
 
 export const collections = {
 	docs: defineCollection({ loader: docsLoader(), schema: docsSchema() }),
-	elements: defineCollection({
-		loader: glob({
-			pattern: "**/*.yaml",
-			base: "../elements",
-			generateId: ({ entry }) => entry.replace(/\.yaml$/, '')
-		}),
-	}),
 	functions: defineCollection({
 		loader: glob({
 			pattern: "**/*.yaml",
@@ -32,6 +25,16 @@ export const collections = {
 			}
 		})
 	}),
+	elements: defineCollection({
+		loader: glob({
+			pattern: "**/*.yaml",
+			base: "../elements",
+			generateId: ({ entry }) => {
+				// Extract the file name without the folder
+				return ((entry.split('/') || []).pop() || '').replace(/\.yaml$/, '');
+			}
+		}),
+	}),
 	classes: defineCollection({
 		loader: glob({
 			pattern: "**/*.yaml",
diff --git a/web/src/content.constants.ts b/web/src/content.constants.ts
@@ -1,2 +1,4 @@
 export const SITE_TITLE = 'Multi Theft Auto: Wiki';
 export const SITE_URL = 'https://wiki.preview.multitheftauto.com';
+export const OLD_WIKI_URL = 'https://wiki.multitheftauto.com';
+export const OLD_WIKI_REDIRECT = true; // Set to false to disable redirecting to old wiki on 404
diff --git a/web/src/pages/404.astro b/web/src/pages/404.astro
diff --git a/web/src/pages/Element.astro b/web/src/pages/Element.astro
diff --git a/web/src/pages/[element].astro b/web/src/pages/[element].astro
diff --git a/web/src/utils/elements.ts b/web/src/utils/elements.ts
