Update elements page

Author: FileEX

elements/Entity/blip.yaml

@@ -2,5 +2,5 @@ name: 'blip'
 description: |
   The blip class represents small icons or blips that can be shown on a player's radar.
 
-  The list of blip icons are available on the [Radar Blips](/radar_blips) page. 
+  The list of blip icons are available on the [Radar Blips](/reference/ID_Lists/Blips) page. 
 

elements/Entity/building.yaml

@@ -2,16 +2,9 @@ name: 'building'
 description: |
   The building class represents static 3D models in the GTA world.
 
-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).
-    - |
-      Buildings can be created with dynamic object model IDs, but they won't have any physical interaction. For example, [object ID 1502 (Gen_doorINT04)](https://dev.prineside.com/en/gtasa_samp_model_id/model/1502-Gen_doorINT04/) is a door that can only be opened if created with [createObject](/createObject).
-    - |
-      Using buildings for mapping is more optimized than using objects. Gains in FPS can be noticed in areas where a lot of objects were replaced with buildings of this new system.
-    - |
-      Buildings can only be created inside regular GTA:SA Map Boundaries (X between -3000 and 3000; Y between -3000 and 3000). Use [createObject](/createObject) to spawn objects outside these normal limits. **This limitation is probably going to stop existing in the near future.**
-    - |
-      Created buildings can have **LOD models**. The procedure is as follows: spawn the LOD building using [createBuilding](/createBuilding), then use [setLowLODElement](/setLowLODElement) to associate it with the non-LOD building element you created beforehand. LOD model distance changed with [engineSetModelLODDistance](/engineSetModelLODDistance) works for buildings.
-    - |
-      Buildings cannot appear in certain a [dimension](/dimension), and not show in others. Function [setElementDimension](/setElementDimension) returns false on any building. A building is created in a specific [interior world](/interior) (such as 0, the main world), like the default GTA:SA landscape objects. **All buildings appear in EVERY DIMENSION.**
+  - 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](/reference/Building) can contain **glass** and **shadows**, unlike those created as [Objects](/reference/Object) (which are missing these features).
+  - Buildings can be created with dynamic object model IDs, but they won't have any physical interaction. For example, [object ID 1502 (Gen_doorINT04)](https://dev.prineside.com/en/gtasa_samp_model_id/model/1502-Gen_doorINT04/) is a door that can only be opened if created with [[createObject]].
+  - Using buildings for mapping is more optimized than using objects. Gains in FPS can be noticed in areas where a lot of objects were replaced with buildings of this new system.
+  - Buildings can only be created inside regular GTA:SA Map Boundaries (X between -3000 and 3000; Y between -3000 and 3000). Use [[createObject]] to spawn objects outside these normal limits. **This limitation is probably going to stop existing in the near future.**
+  - Created buildings can have **LOD models**. The procedure is as follows: spawn the LOD building using [[createBuilding]], then use [[setLowLODElement]] to associate it with the non-LOD building element you created beforehand. LOD model distance changed with [[engineSetModelLODDistance]] works for buildings.
+  - Buildings cannot appear in certain a [[Dimension]], and not show in others. Function [[setElementDimension]] returns **false** on any building. A building is created in a specific [[Interior]] (such as 0, the main world), like the default GTA:SA landscape objects. **All buildings appear in EVERY DIMENSION.**

elements/Entity/effect.yaml

@@ -2,4 +2,4 @@ name: 'effect'
 description: |
   The Effect class represents custom effect elements in the game world such as smoke, sparks, fire etc.
 
-  TODO all effects table
+  Effects listed in the [Effect Types](/reference/ID_Lists/Effects) page can be created using the [[createEffect]] function.

elements/Entity/object.yaml

@@ -2,10 +2,6 @@ name: 'object'
 description: |
   The object class represents dynamic and static 3D models placed in the GTA world.
 
-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").
-    - |
-      There is a distinction in GTA: San Andreas between static and dynamic models. The alternative [createBuilding](/createBuilding) function allows you to create objects that are non-dynamic, utilizing the GTA Building pool, which makes better use of memory.
-    - |
-      The [createObject](/createObject) function can also create non-dynamic objects, but for optimization reasons **it is recommended to spawn [Buildings](/building) when creating static objects that don't rely on the [Dimension](/dimension) system** (buildings don't use the same MTA object-streaming system).
+  - 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").
+  - There is a distinction in GTA: San Andreas between static and dynamic models. The alternative [[createBuilding]] function allows you to create objects that are non-dynamic, utilizing the GTA Building pool, which makes better use of memory.
+  - The [[createObject]] function can also create non-dynamic objects, but for optimization reasons **it is recommended to spawn [Buildings](/reference/building) when creating static objects that don't rely on the [[Dimension]] system** (buildings don't use the same MTA object-streaming system).

elements/Entity/ped.yaml

@@ -2,5 +2,5 @@ name: 'ped'
 description: |
   The word "ped" is short for "pedestrian" and describes any person in GTA, be it a player or an NPC character. (And even though "pedestrian" doesn't technically apply to people that drive, they still fall under this name) 
 
-  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 [[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. 
 

elements/Entity/projectile.yaml

@@ -1,21 +1,3 @@
 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).
-
-notes:
-    - |
-      **16: Grenade**
-    - |
-      **17: Tear Gas Grenade**
-    - |
-      **18: Molotov**
-    - |
-      **19: Rocket (simple)**
-    - |
-      **20: Rocket (heat seeking)**
-    - |
-      **21: Air Bomb**
-    - |
-      **39: Satchel Charge**
-    - |
-      **58: Flare from Hydra**
+  The projectile class represents the projectiles of certain weapons that are created when the weapon is fired. Alternatively these can be created using [[createProjectile]].

elements/Entity/radararea.yaml

@@ -1,9 +1,3 @@
 name: 'radararea'
 description: |
   The radar area class represents coloured areas that can be displayed on a player's radar.
-
-
-see_also:
-  - 'functions:any:RadarArea'
-  - 'events:any:RadarArea'
-

elements/Entity/water.yaml

@@ -2,5 +2,5 @@ name: 'water'
 description: |
   In San Andreas, the water in the game world (rivers, lakes, seas) is defined through a large number of water polygons, which can be quadrilateral or triangular.
   
-  A water element represents one such polygon. You can create water elements using [createWater](/createWater).
+  A water element represents one such polygon. You can create water elements using [[createWater]].
 

elements/Entity/weapon.yaml

@@ -1,4 +1,4 @@
 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 Weapon class represents a custom static weapon. Weapon elements created by [[createWeapon]] can be manipulated with the following scripting functions.