SPWiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Project IDs ======
===== What an ID means =====
<html>
<table style="width:100%;">
<tr>
<th colspan="2" style="text-align:center;"></html>
==== Project number ====
<html></th>
</tr>
<tr>
<td colspan="2">
&bull; The most important characters in a Spazplay PID.
</td>
</tr>
<tr>
<th style="width:30%;">Example:</th>
<td><span style="color:#006e00;">001</span><span style="color:#cecece;">w01O</span></td>
</tr>
</table>
</html>

The first three numbers at the beginning of a PID represent the order in which the project was registered into the Spazplay Development database. These digits of a PID are unique and will never be the same as another. If a project you see that begins with //009//, this means it is the **9th** project that Spazplay has ever been working on since [[spazplay:database|project databasing]] has started.


<html>
<table style="width:100%;">
<tr>
<th colspan="2" style="text-align:center;"></html>
==== Project type ====
<html></th>
</tr>
<tr>
<td colspan="2">
&bull; Website IDs would include the letter <strong><i>w</i></strong><br />
&bull; Game IDs would include the letter <strong><i>g</i></strong><br />
&bull; Script IDs would incude the letter <strong><i>s</i></strong><br />
&bull; Game Mod IDs would incude the letter <strong><i>m</i></strong><br />
&bull; These letters are always in lowercase
</td>
</tr>
<tr>
<th style="width:30%;">Example:</th>
<td><span style="color:#cecece;">001</span><span style="color:#006e00;">w</span><span style="color:#cecece;">01O</span></td>
</tr>
</table>
</html>

The first letter in a PID represents the type of project it is. These letters are not unique to projects and are repeatable through a variety of PIDs. There are only a few letters you would see in a PID.
==== Class verification ====
This set of numbers in a PID represents how many projects through a specific class the project is, and can occur only once per class. This means, regardless of the first three digits or first letter of a PID, this specific number is only in relation to the single uppercase letter to it's right.

  * <html><span style="color:#cecece;"><del>001w</del></span><span style="color:#006e00;">01</span><span style="color:#cecece;"><del>O</del></span></html>
==== Class status ====
The last letter in a PID represents the class status of the project. These letters, much like the [[#project-type|project type]] letters, can are not ID unique and can be repeated through multiple PIDs. Content status letters imply ownership/affiliated to the project.

  * These letters are always in uppercase
  * Official projects use the letter **//O//**
  * Affiliated projects use the letter **//A//**
  * Non-affiliated projects use the letter **//N//**
  * If there is no relation at all, projects use the letter **//P//**
    * <html><span style="color:#cecece;"><del>001w01</del></span><span style="color:#006e00;">O</span></html>
===== ID examples =====

  * What can be done:
    * 001w01O
    * 004g01A

  * What cannot be done:
    * 003s02P
    * 007w02P

This cannot be done because the //[[#class-verification|class number]]// is the same.

  * xxxx02x

====== Build Numbers ======
Build numbers represent which version the project is currently in. Typically, something like a website won't have one of these, but games and scripts likely would. A Spazplay build number would characterise details like the main version, updates, bug fixes/small modifications, year of the build, release type, and the total amount of releases of the project.

**Example:** 1.0.0-2023b0.01

1.0.0 -- version 1, 0 updates, 0 fixes\\
2023 -- year of latest version release\\
b0 -- "beta" (release type)\\
*"0" large releases after the main one\\
01 -- total releases, including small changes

When a small change is made or a bug is corrected then released, this would then make a change to the build number simply by replacing the **second** 0 with a 1, and also by changing the very **last** 1 into a 2.

**Example:**\\
1.0.0-2023b0.01\\
would become\\
1.0.**1**-2023b0.0**2**

If //1.0.1-2023b0.02// somehow upgrades to a brand new full release without going through several more changes/fixes or upgrades, the first number that we just changed into a 1 would reset back to **0** while changing the very **first** number (**1**) into a 2, and replacing the **last** number (**2**) with a 3.
The beta release number (**b0**) would then change as well to **b1** because it was a major update.

1.0.1-2023b0.02\\
would become\\
**2**.0.**0**-2023**b1**.0**3**

<html><span style="font-size:80%;"><< <a href="../">Back to main</a></span></html>