recursal/Fanatic-Fandom huggingface dataset:
I

I

La **i** (en mayúscula **I**, nombre *i*)​ es la décima letra del alfabetoob y su tercera vocal.

## Letras y caracteres relacionados

* i : Superíndice de i minúscula, que se usa para gráficos de terminales de computadora
* Ꞽ ꞽ : I Glotal, usado para yod egiptológico
* Ɪ ɪ : I Capital Pequeña
* ꟾ : I larga
* ꟷ : I de lado
* J j: la letra latina J
* IE: ligadura latinan't *IE*

## Evolución

Yodh
I
Iota

## Pronunciación

**/i/ :** Suena como I en T**i**po

**/j/ :** Suena como Y en A**y**er

## Otros

H
I
E
I
O
Maritime Ship Class Format

```
This format is to be used on all pages about maritime ship classes. The format is show below.

```

## Class Overview

### Operators

Operators of ship(former) is to be put after former operators

### Preceded By

Ship class replaced by this class (N/A if none)

### Succeeded By

Ship class which replaces this class (N/A if none}

## Specifications

### Armaments

Armaments of shipTo be listed as:

9 x 406mm 50 caliber guns
20 x 127mm 38 caliber guns

### Aircraft Carried

Aircraft carried by ship

The **[Maritime Ship class]** is [introductory paragraph about the ship class here, such as operators, builders, notable aspects about the class, etc.]

## Development [Heading]

### **Specific Stage of Development/Construction [Bold, Sub-heading 1]**

The development section of the page should include who ordered the ship class, the designers of the class, the requirements for the designs along with the construction of the class, which would be under a separate bold sub-heading 1. Any modernization projects that occur after the class has been commissioned can also be included in the development section, however under its own bold sub-heading.

## Design and Armaments [Heading]

### **Design [Bold, Sub-heading 1]**

This section of the page should feature descriptions of the ship's design, such as the hull shape, locations of the crew quarters, aircraft, the ship's power source, propulsion mechanism, etc. Any modernizations the class may have had should be under separate sub-headings, each based on the the specific modernization. Include what was changed about the ship's design.

### **Armaments [Bold, Sub-heading 1]**

The armaments section of the page should feature the armaments the ship has, for example VLS cells, CIWS, cannons, etc. Just like the design section, if the ship receives changes to its armaments, you will have to list the original armaments and modernized armaments separately. Modernized armaments are to be under their own sub-heading 1.

## Service History [Heading]

### **Nation the ship class served [Bold, Sub-heading 1]**

A brief description of how the class served the nation should be here. Ship classes can serve multiple nations, therefore there can be multiple sub-heading 1s with service to different nations detailed under them.

#### **Specific Conflict or other Event [Bold, Sub-heading 2]**

A description of how the ship class served in this conflict or event should be here. A further bold, sub heading 3 can also be inserted under the sub-heading 2 for an important battle or other event.
Character Format

```
This format should be used for all pages about characters. The format is shown below. As opposed to the Player Format page, character pages are considered in-universe pages.

```

## Physical Description

### Eye Color

Character's eye color

**[Character]** is [introductory paragraph of the character here, such as if they are the leader of a nation, company or other entity, their nationality, species, etc.]

## History [Heading]

### **Specific Stage in the Character's History [Bold, Sub-heading 1]**

The history section of the page should include aspects about the character's life, such as their early life, rise to power, death (if they are deceased), etc. Each specific stage should be under their own bolded sub-heading 1.

## Personality [Heading]

This section of the page should include elements of the character's personality, which should include how the character acted towards other people, how they ruled their nation or other entity, as well as other things related to their personality.
Professional

* Overview
* Professional
* Pro Athletes
* Virtual
* Augmented Reality
* Extreme
* Sports Entertainment

By this time, all the pro teams are completely Corp owned. This is useful because the Corps have pretty much limitless money to support their teams, so the teams have better stadiums/facilities, uniforms, promo give-aways, etc. The quality of players is higher also.

This situation works well for the Corps, because owning a team fosters Corp spirit and provides an outlet for competitiveness between Corps without any actual risk to business interests. Real fans of a team wear the team jersey (plastered, of course, with the appropriate Corp logo, know the team cheers and songs, follow team and player stats obsessively, and know perfectly well that the fans of the other team SUCK.

Things have sometimes become intense enough at pro sport games/matches that there's now a (computer) game out called Stadium Riot. In Stadium Riot you choose (for a price) the number of fans and their dedication/intensity level (measured in terms of jerseys, pennants, hats, level of intoxication, etc.--all of which cost something.). Then you fight it out with someone else's fans. A small number of rabid fans may or may not win out over a large number of lackadaisical fans. But when you get the perfect balance of numbers and dedication/intensity, then your fans beat the shit out of your opponent's fans and you win the game.
The Divided World Wiki

**Welcome to the The Divided World Wiki!**
The Divided World (TDW) is an alternate history, Discord-based roleplay revolving around an alt-Cold War scenario in which a different world emerges out of the ashes of World War II compared to our timeline.

We're a collaborative community website about The Divided World that anyone, including you, can build and expand. Wikis like this one depend on readers getting involved and adding content. Click the "ADD NEW PAGE" or "EDIT" button at the top of any page to get started!

When writing, please follow the specific format guides that can be found here. Any page that does not follow the formats will be re-edited. If you are writing a page that does not fit with any of the formats provided, contact Retribution-class Battleship#6470.

(For the best viewing experience, update zoom settings for TDW (ctrl + "-" or "+") to 80%.)

## Important articles

PlaceholderA page about your topicPlaceholderA Main CharacterPlaceholderThe First EpisodePlaceholderAn Important LocationPlaceholderA Key EventPlaceholderA Crucial Item

*Need help building out this community?*

* Rules of this wiki
* Getting Started
* How to Contribute
* Managing your new community
* Guides
* All Help articles

You can also be part of the larger Fandom family of communities. Visit Fandom's Community Central!

*Community Founders*: Write a good and paragraph-length description for your welcome section about your topic. Let your readers know what your topic is about and add some general information about it. Then you should visit the admin dashboard for more tips.
MPGameInfobox

```
{{MPGameInfobox
}}

```

# Example

**Note: This infobox is designed for using two or more pictures. For the infobox designed for using only one picture, view this infobox instead.**

Other notes: Use the operator <br> in source mode to add linebreaks within the table. Sections left blank will not be displayed. The title that appears at the top of the infobox will be the same as the name of the page it is on. Note that the picture field requires the extension (.jpg, .jpeg, .png) to be present, and requires that the File: or Image: part of the link *not* be present.

Using the following:

```
{{MPGameInfobox
<div style="font-weight:bold;line-height:1.6;">Original</div>
<div class="mw-collapsible-content">ESRB: E<br>PEGI: 3+</div><div class="mw-collapsible mw-collapsed">
<div style="font-weight:bold;line-height:1.6;">''Rehydrated''</div>
<div class="mw-collapsible-content">ESRB: E10+<br>PEGI: 7</div>
<div style="font-weight:bold;line-height:1.6;">Original</div>
<div class="mw-collapsible-content">[[Game Boy Advance]]<br>[[Microsoft Windows]]<br>[[Nintendo GameCube]]<br>[[PlayStation 2]]<br>[[Xbox]]</div><div class="mw-collapsible mw-collapsed">
<div style="font-weight:bold;line-height:1.6;">''Rehydrated''</div>
<div class="mw-collapsible-content">Microsoft Windows<br>[[Nintendo Switch]]<br>[[PlayStation 4]]<br>[[Xbox One]]<br>[[mh:crappygames:Stadia]]<br>Android<br>iOS</div>
<div style="font-weight:bold;line-height:1.6;">Original</div>
<div class="mw-collapsible-content"><small>NA: October 31, 2003<br>EU: November 28, 2003<br>AU: 2003 <small>(PS2)</small></small></div><div class="mw-collapsible mw-collapsed">
<div style="font-weight:bold;line-height:1.6;">''Rehydrated''</div>
<div class="mw-collapsible-content"><small>WW: June 23, 2020<br>WW: December 8, 2020 <small>(Stadia)</small></small><br><small>WW: January 21, 2021 <small>(Android/iOS)</small></small></div>
}}

```

Results in the following (normally aligned on the right of the screen):
Battle Format

```
This format is to be used for all pages about battles. The format is shown below.

```

Note: The Battle Template infobox works differently than the other ones, copy the code found in Template:Battle Template and paste it into your page to create the infobox.

### Result

Outcome of the battle

Units Involved| Units involved to be listed as:Ex:* 4th Army
* 10th Armored Division
* 9th Army

Casualties| Casualties of side 1 to be listed as:Ex:* 50,000 troops
* 800 armored vehicles
* 600 armored vehicles

### Civilian Casualties

Civilian casualties (if any)

**[Battle Name]** is [introductory paragraph about the battle here, such as if it was a major or minor battle, what nations or other entities were involved, when the battle took place, and the outcome of the battle.]

## Background [Heading]

The background section of the page should include events leading up to the battle, such as rising tensions, troop mobilizations, and other events that could lead to a battle. The causes of the battle should also be included here.

## The Battle [Heading]

### **Specific Stage in the Battle [Bold, Sub-heading 1]**

This section should include specific stages in the battle, like the beginning of the battle, important events that happened in the battle, and the end of the battle. Important events that happen during battle can include turning points, major defeats/victories, etc.

## Casualties [Heading]

### **[Combatant] Losses [Bold, Sub-heading-1]**

The casualties section of the page should include what the casualties for the nations involved in the battle, each under their own bolded sub-heading 1 for each nation. Casualties should include personnel losses as well as vehicle losses.

## Aftermath [Heading]

The aftermath section of the battle should include events that happened directly after the battle has ended, such as troop withdrawals, capitulation, and a number of other post-battle events that could occur.
The Void Armada Wiki

This Wiki is the official lore and information resource for The Void Armada, A Star Trek Online community. Founded in 2019, the mission of The Void is to mentor new players, to promote fellowship and unity among long-time players, and to have fun with our favorite game!

The Void Fleet

If you're interested in joining our STO community, please watch the video below for Armada rules and other important things you need to know!
(Be sure to click "full screen" so you don't miss anything!)
Ч

Ч

La **ч** (en mayúscula **Ч**, nombre che) es una letra del alfabeto cirílico. Es la vigésimo quinta en el alfabeto ruso y tercera en el alfabetoob

## Letras y caracteres relacionados

* 4 : 4 - Número que se parece mucho al Che, especialmente en forma digital o abierta
* C c : letra latina C - el mismo sonido en malayo, indonesio, italiano
* Č č : letra latina C con caron
* Ç ç : Letra C Cedilla
* Ĉ ĉ : letra latina C con acento circunflejo , utilizada en el idioma esperanto
* Ch : Dígrafo Ch
* Cs : Dígrafo Cs
* Cz : Dígrafo Cz
* Ҷ ҷ : letra cirílica Che con descendiente
* Ӵ ӵ : Letra cirílica Che con diéresis
* Ҹ ҹ : letra cirílica Che con trazo vertical
* Ꚇ ꚇ : letra cirílica Cche
* Ɥ ɥ : letra latina H volteada
* Վ վ : letra armenia Vev
* Կ կ : letra armenia Ken

## Uso

En todas las lenguas eslavas que utilizan el alfabeto cirílico, excepto el ruso, Che representa la africada postalveolar sorda /tʃ/ .

En ruso, Che generalmente representa la africada alveolo-palatal sorda / t͡ɕ / , como la pronunciación mandarín de **j** en pinyin . Sin embargo, en pocas palabras, se pronuncia como /tʃ/ , como en ruso : лучше .

En ruso, en pocas palabras, representa /ʂ/ (como el inglés ⟨sh⟩ /ʃ/ en " shape "): Ruso : что, **чтобы** , нарочно .

## Otros

B
Ч
B
Ч
Ç
Firearm Format

```
This format is to be used in all pages about firearms. The format is shown below.

```

## Service History

### Users

Users of firearm(former) is to be put after former users

## Specifications

### Muzzle Velocity

Muzzle velocity of firearm

**[Firearm]** is a [introductory paragraph about the firearm here, which should include the type of firearm, caliber, designers, users, etc.]

## History [Heading]

### **Specific Stage of Firearm's History [Bold, Sub-heading 1]**

The history section of the page should include the development of the firearm, which includes who ordered the firearm, the designers of the firearm, the requirements for the design. Any improvement projects the design has experienced should also be included under the development section, under its own sub-heading 2. The beginning of production, which should be under its own sub-heading 1, should also be included. As well as this, a record of the firearm's service history should be included, such as the nations they served, conflicts they served in, as well as when they were replaced, if they were.

## Design [Heading]

The design section of the page should include aspects of the firearm's design, such as caliber, recoil, the barrel, action, accuracy, reliability, etc. Differences between the variants or derivatives, if it has any, should also be included here.

## Variants and Derivatives [Heading]

### **Variant or Derivative [Bold, Sub-heading 1]**

Different variants or derivatives should have their own bold, sub-heading 1s. Information about the variants or derivatives should include if it is a variant or derivative, the differences in design from the original model, etc. The first production model should be the first variant listed here. Images should also be provided when possible.
Armed Forces Format

```
This format is to be used on all pages about armed forces of nations. The format is shown below.

```

## Industry

### International Suppliers

Suppliers of the armed forces from other nations

**[Armed Forces Name]** is the [introductory paragraph about the armed forces here, such as what nation they serve, what service branches are under it, date of founding, etc.]

## History

### **Stage in the Armed Forces' History [Bold, Sub-heading 1]**

The history section of the page should include important event's in the armed forces' history, such as founding, military expansion, addition of new branches, dissolution (if it is dissolved), etc. Each major event should have its own sub-heading 1 and if any less major events fall under the major event, sub-heading 2s and sub-heading 3s can be used if needed.

## Service History [Heading]

### **Conflict/Other Major Event [Bold, Sub-heading 1]**

Each conflict or major event should have its own bold sub-heading 1. Under the sub-heading should be a detailed explanation of how the armed forces served in the conflict or event. Images should also be included when possible. Sub-heading 2s can be included for major battles or other events under a conflict, and a sub-heading 3 can be inserted under that if necessary.

## Service Branches [Heading]

### **[Military Branch] [Bold, Sub-heading 1]**

In the service branches section of the page, there should be a detailed explanation about the specific military branch under its sub-heading, such as its role, size, date of founding, etc. Images should also be included if possible. Since most armed forces have multiple branches, there can be multiple sub-heading 1s for each branch.
Nation Format

```
This format should be used for all nation pages. The format is shown below.

```

Flag of [Nation]

**[Nation]** is [add info about nation here, such as if it is Mars or Earth-based, if it is still active, etc.]

## History [Heading]

### **Important Era [Bold, Sub-heading 1]**

This section of the page should detail a specific important era in the nation's history, such as when it was founded, any territorial expansion, or about when it was dissolved, if it was.

## Conflicts [Heading]

### **Conflict [Bold, Sub-heading 1]**

The conflicts section of the page should include details about the conflicts that the nation has fought, if any. Specific conflicts should be under their own bolded sub-heading 1s.

## Politics

### **Government [Bold, Sub-heading 1]**

This section should include details about the nation's government, such as what type it is, who its leader(s) is, how it operates, etc.

### **Military [Bold. Sub-heading 1]**

#### **Armed Forces Branch [Bold, Sub-heading 2]**

This should have a short explanation of the specific armed forces branch and its role.

### **Foreign Relations [Bold, Sub-heading 1]**

There should be a short explanation of what is to be listed below; allies is to be listed first.

For example:

"The United States of America has established alliances with the following nations:"

Bulleted list of allies below

After this ally list should be a list of nations that aren't in formal alliances with your nation but have good relations.

For example:

"The United States of America has friendly relations, though not official alliances, with the following nations."

Bulleted list of said nations below.
Individual Ship Format

```
This format is to be used on all individual maritime ship pages. The format is shown below.

```

## Specifications

### Armament

Armament of ship to be listed as:Ex:

9 x 406mm 50 caliber guns
20 x 127mm 38 caliber guns

### Aircraft Carried

Aircraft carried by ship to be listed as:Ex:

2 x Utility Helicopters

***[Ship Name]*** is [introductory paragraph about the ship here, such as the ship's class, operator, nation of origin, etc.]

## Description [Heading]

### **Design [Bold, Sub-heading 1]**

The design portion of the page should feature elements of the ship class's design. It should feature dimensions of the ship, the ship's power plant, propulsion system, radar systems, crew quarters locations, etc. If the ship has any differences or modifications from other ships of the class, they should be included here.

### **Armaments [Bold, Sub-heading 1]**

The armaments section of the page should feature all the weaponry the ship has, such as VLS, cannons, defensive armament, etc. If the ship has any armaments which are different from other ships of the class, those should be included here.

## History [Heading]

### **Event in the Ship's History (year) [Bold, Sub-heading 1]**

Each specific event, such as construction or other events, should have their own bolded sub-heading 1. Provide the year the event happened as well as a description of the event. Provide images when possible

## Combat History [Heading]

### **Nation the Ship Served [Bold, Sub-heading 1]**

A description of how the ship served the nation should be here. Due to the fact that some ships can serve multiple nations throughout their service life, there can be multiple sub-heading 1s for different nations.

#### **Conflict or Other Major Event [Bold, Sub-heading 2]**

A description of how the ship served in this conflict or major event should be here. Include images when possible.
War Format

```
This format is to be used on all pages about wars. The format is shown below.

```

Note: The War Template infobox works differently than the other ones, copy the code found in Template:War Template and paste it into your page to create the infobox.

### Result

Result of the war

Commanders and Leaders| **Major Leaders*** Leader of country

Casualties and Losses| **Military Dead*** Number of total military personnel killed

**Civilian Dead*** Number of total civilians killed (if any)

**Total Dead*** Total number of deaths (civilian and military)

**Civilian Dead*** Number of total civilians killed (if any)

**Total Dead*** Total number of deaths (civilian and military)

**[War]** is/was a [introductory paragraph about the war here, such as the the combating nations, locations of the war, the date of the war, the outcome of the war, etc.]

## Background [Heading]

### **Region of Tension [Bold, Sub-heading 1]**

The background section of the page should include details about the tension between nations involved in specific regions that were involved in the war. For example, the regions of tension and later war in the AT-USSAS War would be the Americas and the Pacific.

## Pre-War Events [Heading]

### **Event [Bold, Sub-heading 1]**

This should include major events that would eventually build up to the war, such as rising tensions, incidents concerning military assets encroaching on another nation's territory, increased militarization, etc.

## War [Heading]

### **Stage of War [Bold, Sub-heading 1]**

This part of the page should include the war itself, separated into different stages of the war, such as the beginning, any turning points, and the end. Any other major events, such as the opening of a new theater of war, can be included under a bolded sub-heading 2.

## Aftermath and Impact [Heading]

The aftermath section of the page should include what happened directly after the war ended, such as if new nations formed, new alliances, etc.

### **Consequence [Bold, Sub-heading 1]**

There should be multiple of these "consequence" sub-headings if needed, each detailing a specific consequence of the war, such as casualties, occupation, advances in technology, war crimes and what was done with the war criminals, etc.
Ground Vehicle Format

```
This format is to be used on all pages about specific ground vehicles. The format is shown below.

```

## Ground Vehicle Name

A [Ground Vehicle] of the [Armed Forces of Nation]

## Service History

### Operators

Operators of vehicle (former) is to be put after former operators

## Specifications

### Armaments

Armaments of vehicleTo be listed as:

1 x 120mm smoothbore cannon
2 x .50 caliber machine guns

### Speed

Speed of vehicle

The **[Ground Vehicle]** is [introductory information about the vehicle here, such as operators, designers, etc.]

## Development [Heading]

### **Specific Stage of Development/Production [Bold, Sub-heading 1]**

I.E. **Early Development**

The development section of the page should include who ordered the vehicle, the vehicle's designers, the requirements for the designs as well as the beginning of production of the vehicles, which should be included under a separate bold heading-1. Any modernization projects the design may have undergone should also be included under the development heading, under its own bold heading-1.

## Design and Weaponry [Heading]

### **Design [Bold, Sub-heading 1]**

The design section of the page should include elements of the vehicle's design, such as armor, crew locations, the vehicle's engine or power source, etc. Differences between the design of variants of the vehicle, if it has any, will also be included here.

### **Weaponry [Bold, Sub-heading 1]**

The weaponry section of the page should include all the armaments the vehicle has, such as main armament, any secondary weapons it may have, and any countermeasures to enemy weapons it has. Differences between the weaponry of variants of the vehicle can also be included here.

## Variants [Heading]

### **Ground Vehicle Variant** **[Bold, Sub-heading 1]**

Any variants of the vehicle, including the original production model, are to be explained here in as much detail as possible. include aspects of the design and weaponry that are specific to that model, as well as the year they were introduced, etc. Provide images of the specific variant if possible.

## Service History [Heading]

### **Nation the Vehicle Served [Bold, Sub-heading 1]**

A description of how the vehicle served this nation should be here. Due to the possibility of a vehicle being used by multiple nations, there can be other sub-headings for other nations.

#### **Specific Conflict or other Event [Bold, Sub-heading 2]**

A description of how the vehicle served in this specific conflict or other event is to be included here. A bold, sub-heading 3 can be inserted under this if necessary for any major battles or other event.
M'Uus

Commander M'Uus in 2410

M'Uus is a Caitian male, a native of Cait born in the late 24th Century. He is the chief engineer of the USS *John Adams*, and participates in many Green Wing activities on behalf of the Void Fleet and the Federation.

## Biography

### Early Life

M'Uus was born in early 2380, the eldest of a litter of 12 to his parents L'Ana and R'Uss. Growing up in T'Ruvna Province, M'Uus had quite a few friends, who spent time in the forests around his parent's home playing "Earthers and Romulans" and other such games. He gained a renown for building some of the best play forts for his team from found materials such as tree limbs and rocks.

### Starfleet Career

M'Uus showed a superior aptitude for engineering and warp sciences throughout his schooling, graduating near the top of his class in 2398. Wishing to further his studies, he enrolled in the engineering track of Starfleet Academy, graduating in 2403.

In 2404, M'Uus was made an ensign and assigned to the USS *Ganymede* (NCC-80107). His work and courage during the battles for the Hromi Cluster in 2405 so impressed his superiors that he was field-commissioned Lieutenant, Junior Grade. He was gazetted a full Lieutenant later that year.

In 2406, M'Uus was transferred to the engineering department of the USS *Shirgat* (NCC-91413), where it participated in many battles during the Klingon invasion of the Archanis Sector. He was promoted to Lt. Commander by 2409 and second in command of the engineering department.

By 2410 and the end of the war, M'Uus was promoted to Commander and made chief engineer of the USS *John Adams* (NCC-93359), part of Admiral Bowerman's Green Wing. As Wing operations requires the usage of different vessels depending on the assignment, M'Uus often acts in the same capacity on different vessels.

### Personal Life

M'Uus met and fell in love with fellow Caitian cadet Rawana during his third year and her second. They were married after his graduation and before assignment to the *Ganymede* in 2404. She was assigned to the security department of the USS *Crazy Horse* (NCC-95789) upon her graduation in 2405 and killed during an engagement with Klingon Defense Forces and a Planet Killer within the Imaga System in 2409.
Charles Guiteau State Prison

The **Charles Guiteau State Prison** is a prison featured in *Crime of Your Life*, located in the New Lincoln River in the Northern Idaho County area.

## Description

It is governed by the Idaho State Prison Authority. The prison is located in the New Lincoln River (the New Lincoln County section), just off Charles Guiteau Avenue. The shape of the prison is in the shape of a hexagon. Guards from the Idaho State Prison Authority can be seen both outside of the prison and inside of the prison. The prison is based on Alcatraz Prison. Inmates can be seen inside the prison either working, standing around or playing games.

## Known Inmates

* Horatio Raymond Jr. (Formerly; Released)
* Horatio Raymond (Formerly; Released)

## Mission Appearances

### Crime of Your Life

* Alabama
* The Calm Before The Storm
* This Land Is My Land
* Mesmo Assim

### Crime of Your Life: Deltaworks

* A Keeper
* The Rockstars
* Death Lord

### Crime of Your Life Online

* Death Party
* Peering Pressure

### Crime of Your Life: New Lincoln Adventures

* Roman and Julio
* The New Lincoln Connection
* The Judge Has Been Judged
* Communist Revolution

### Crime of Your Life: Tales from The Visual Novel

* True News
* An Old Friend

## Trivia

* The name of the prison is named after Charles Guiteau, who notably assassinated U.S. President James A. Garfield.
Fictional Characters Fanon Wiki

**Welcome to the Fictional Characters Fanon Wiki!**
A wiki based on the Fictional Characters Wiki, but with only fanon info on these characters.

We're a collaborative community website about Fictional Characters Fanon that anyone, including you, can build and expand. Wikis like this one depend on readers getting involved and adding content. Click the "ADD NEW PAGE" or "EDIT" button at the top of any page to get started!

*Need help building out this community?*

* Rules of this wiki
* Getting Started
* How to Contribute
* Managing your new community
* Guides
* All Help articles

You can also be part of the larger Fandom family of communities. Visit Fandom's Community Central!

*Community Founders*: Write a good and paragraph-length description for your welcome section about your topic. Let your readers know what your topic is about and add some general information about it. Then you should visit the admin dashboard for more tips.
LootMMO Rkade Wiki

## **Welcome**

A wiki about an edition of LootMMO created by xRae, VileShinobi, and Jeis. Featuring additional mechanics and Zones, namely Shiverwind Valley, for players to explore.

* Pages
* Categories

## Site Management

We're a collaborative community website about LootMMO\_Rkade that anyone, including you, can build and expand. Wikis like this one depend on readers getting involved and adding content. Click the "ADD NEW PAGE" or "EDIT" button at the top of any page to get started!

*Need help building out this community?*

* Rules of this wiki
* Getting Started
* How to Contribute
* Managing your new community
* Guides
* All Help articles

You can also be part of the larger Fandom family of communities. Visit Fandom's Community Central!
Shiverwind Valley

Shiverwind Valley is an icy tundra that is home to faction of Shiverwind Village and dungeon named The Lich's Tower

Players can get to Shiverwind Valley via Zeppelins or the Travel Map. If players take the Zeppelin by the Tavern Exterior they can talk to a Questgiver named Ronk who will start the quest Supplies for Shiverwind
USS John Adams (NCC-93359)

The **USS *John Adams*** (NCC-93359) is a Federation starship, a *Miranda*-class cruiser in Starfleet service in the 24th and 25th Centuries.

## History

With the tensions arising between the Federation and the Klingon Empire and the eventual invasion of the Gorn Hegemony by the Klingons later that year, Starfleet found itself in the position of preparing for the possibility of open conflict with the Empire. Seeing the need for proven designs for supply and transport missions, plans to finally retire the venerable *Miranda* class of ships was placed on temporary hold. As such, the USS *John Adams* was constructed at the Antares Shipyards and launched in late 2399.

   Under the command of Captain Vos Ruhlas, the *John Adams* was assigned to patrol and supply duties at outposts and colonies along the Klingon Neutral Zone. Most notably, the ship was involved in the defense of Sherman's Planet and Station K-7 in 2405. In 2408, the ship struck a mine in the Cestus System while on a mission to supply colonists attempting to repel the Gorn invasion. The ship was towed to Earth and underwent extensive repair.

The ship was re-launched in 2409 under the command of then-Commander Keith Bowerman and assigned to Klingon Neutral Zone patrol missions.

## Green Wing

At the close of the Iconian War in late 2410 and Bowerman's promotion to the admiralty, he established the Green Wing, a division of the Void Fleet, with the *John Adams* as his personal flagship. With the upgrades to the vessel making it more than capable in combat as compared to sister ships of the class, the *John Adams* is primarily used in diplomatic and escort missions.

## Naming

The vessel was named for John Adams (1735-1826), first Vice-President and second President of the United States of America.
TurboGrafx-CD

Template:ConsoleInfobox
The **TurboGrafx-CD** (also commonly known as the **Turbo CD** and known as the **PC Engine CD** outside North America) is a console add-on for the PC Engine/TurboGrafx-16, allowing the console to play games in CD format as well as its standard games. This makes it the first CD add-on, and makes the TurboGrafx-16 the first system ever to play CD-based games. In Japan, it was sold in two models, the CD-ROM ROM, (Yes, that's how you pronounce it.) and a revised model which integrated the Super System Card. There was also a combo unit called the PC Engine Duo, which was sold in North America as the TurboDuo. The Duo itself in Japan would get two revisions, the Duo R, which had better build quality and also gave it a white casing, and the Duo-RX, which was also the last revision for the console itself. It changed the controller to a 6 button controller but was largely the same otherwise.

Although it was a hit in Japan, due to a number of factors (including the release of the Sega Genesis and eventually its CD based add-on) the TurboGrafx-CD would never pick up in sales in North America, and eventually be history.

## Why It Rocks

1. It was the first CD-based console produced. Without this, we couldn't have consoles like the famous Sony PlayStation!
2. It's the only CD add-on that doesn't require a separate power supply to power.
3. There are many games that are worth owning and playing on the TurboGrafx-CD, which includes *Castlevania: Rondo of Blood*, *Gate of Thunder*, *Lords of Thunder*, *Lemmings*, *Star Parodia (Parodier)*, the *Tengai Makyou* series, the *Ys* series, and others as well.
4. It is region-free unlike the Hucard part of the PC-Engine/TurboGrafx-16.
5. Unlike most CD consoles at the period. It had games that were actually games and not as much FMV focused games.
6. The design of the console is cute.
7. Like the Sega CD, can listen to your own Music audio CD's on the Turbo CD.

## Bad Qualities

1. Despite being a decent add on, it was a flop in North America, therefore, it has enough bad qualities to be on the Crappy Games Wiki.
Neo Geo

Template:ConsoleInfobox
The ***Neo Geo*** was a console made by SNK which was never very popular, but did hold the record for the longest-lived console. It is often characterized by it’s mammoth sized cartridges.

## Why It Rocks

1. Three words: **Arcade. Perfect. Ports.** This is because the hardware is basically an arcade machine crammed into a console box.
2. Crystal-clear voice samples and music.
3. Lots of arcade-style games like fighters and racers and beat 'em ups.
4. Games are region-free, and when any foreign game is played on an American Neo Geo, the text will be in English.
5. Dedicated homebrew community.
6. Had giant arcade-style joystick controllers for added authenticity.
7. Has some of the best *Fatal Fury*, *King of Fighters* and *Metal Slug* games out there, so if you're a fan, it's recommended to pick one up.

## Bad Qualities

Despite its good qualities, the Neo-Geo was a commercial failure. Click here to see why.

## Gallery

Neo-Geo-CD-TopLoader-wController-FL.jpgNeo-geo-console.pngNeogeo1.jpg
PC Engine/TurboGrafx-16

Template:MPConsoleInfobox
The **PC Engine**, known as the **TurboGrafx-16** in North America, is a console released by NEC in 1987. It competed with the Super Nintendo Entertainment System and the Sega Genesis.

## Why It Rocks

1. Although it's still powered by an 8-bit CPU, it is the very first 16-bit console to be released on the market, as it has a 16-bit GPU capable of displaying an impressive 512 simultaneous colors.
2. The games are stored on cards, which are minimalistic and do not take up too much space.
3. Called "The Holy Grail of Shooter Games" for a reason, and that is that much of the console's library comprises of shoot 'em up games.
4. It has a better sound chip than the Genesis, as well as a slightly more powerful processor so its games rarely exhibit much slowdown.
5. It marked innovation by including a CD-ROM add-on, which allowed for an even more enhanced color palette and crystal clear voices.
6. The controllers have built-in turbo switches.
7. Its CD addon was the first ever CD-based home video game system ever to be produced.
8. As said by the Angry Video Game Nerd, its library of games isn't as big, so it isn't as tainted, it doesn't have a lot of really bad games.
9. Sleek design, especially the later Duo models. The original PC Engine is also known as one of the smallest consoles in the world.
10. Usually, when you buy it on eBay, it comes with the five-port multitap. The system only has one controller port, so it's nice that the purchases available usually come with it.

## Bad Qualities

1. Its library of games isn't as big as its competitors', Nintendo and Sega.
2. The cables of the controllers are pretty short.
3. Its add-on, the mh:crappygames:TurboGrafx-CD, flopped, at least in North America.
4. It library includes a few bad games, for example, *Darkwing Duck*.

## Reception

The console was extremely popular in Japan and it even outsold Sega's Mega Drive there. However it failed to catch on in North America due to the Sega vs. Nintendo war, and it never even got a PAL release outside of France.

If you are considering buying it, you might want to take a look at here first.
Alliance Format

```
This format is to be used on all pages about alliances. The format is shown below.

```

### Type

Type of alliance (military alliance, trade alliance, etc)

### Membership

A list of member nations in alphabetical order with their flags in front, if possible.Example:

 United States
 South Korea

**[Alliance Name]** is/was [introductory paragraph about the alliance here, such as its purpose of founding, what nation/entity it was founded by, what nations/entities were part of it, etc.]

## History [Heading]

### **Stage in the Alliance's History [Bold, Sub-heading 1]**

The history section should include details about the alliance's history, such as its founding, growth, dissolution, etc. These specific stages should be included under their own bolded sub-heading 1s.

## Military Operations [Heading]

### **Conflict [Bold, Sub-heading 1]**

Each conflict that the alliance was involved in should be included under its own bold, sub-heading 1, with a detailed explanation of the alliance's actions during that conflict. Images should also be provided if possible.

## Membership [Heading]

The membership section should begin with something along the lines of "[Alliance] consisted of the nations that are listed below." Next, there should be a bulleted list of the nations in alphabetical order.
Г

Г

La **г** (en mayúscula **Г**, nombre che) es una letra del alfabeto cirílico. Es la cuarta en el alfabeto ruso y octava en el alfabetoob

## Letras y caracteres relacionados

* Γ γ: letra griega Gamma
* G g: letra latina G
* H h: letra latina H , romanizada como en bielorruso, ucraniano y ruso
* Z z: letra latina Z , forma alternativa de cirílico en cursiva Г (ge)
* Ґ ґ: letra cirílica Ghe con Alza , ahora solo llamada ***ghe*** (o ***ge*** ) en ucraniano
* Ѓ ѓ: letra cirílica Gje
* Ғ ғ: letra cirílica Ghayn
* ₴: grivna ucraniana (signo de moneda)

## Uso

Representa la oclusiva velar sonora /g/ o la fricativa glotal sonora /ɦ/ en distintos idiomas.

En serbio, búlgaro y macedonio estándar Г representa siempre el sonido /g/. En el ruso estándar también representa el sonido /g/ excepto si es la última letra de la palabra o está al final de sílaba antes de una consonante sorda, dónde suena [k], y antes de una vocal palatizada, dónde suena [gʲ]. Además, en algunos sufijos masculinos de los casos genitivo y acusativo representa /v/ cuando se encuentra entre dos vocales.

En ucraniano y bielorruso representa el sonido /ɦ/.

## Otros

F
Г
F
Г
H
Game Boy Color

Template:ConsoleInfobox
The **Game Boy Color** (**GBC** for short) is a revision of the original Game Boy produced by Nintendo. It was released worldwide in 1998 and discontinued on September 25, 2003, following the release of the Game Boy Advance in spring 2001. It shares the similar design with Game Boy Light, but slightly thicker.

## Why It Still Plays With Portable Power

1. It is the first Nintendo system and handheld system to have backwards compatibility, allowing gamers to play all original Game Boy games on it. It even adds basic color to original Game Boy games by adding a special palette to the game, which can be altered on boot up by pressing a D-Pad button by itself or in conjunction with the A or B button.
2. The screen is fully colored allowing games to render up to 56 out of 32,768 colors without draining the batteries quickly, unlike the previous handhelds with colored screens like the Game Gear. A few games switched the color palette midway through the rendering of the screen to add more than 56 colors on the screen.
3. The screen is now an active matrix LCD, reducing ghosting effects in older games.
4. Higher clock speed CPU than the original Game Boy allowing for more advanced gameplay and graphics. Some games even managed to get full screen FMVs, such as *Cannon Fodder* (and on top of that music and voiced lyrics in its intro), running on the system.
5. The system came in many different colors which fits the name. This is great for collectors who want to focus on collecting the different variants of the console, rather than the console itself. As a matter of fact, some game collectors own many different colored Game Boy Color systems.
6. Over 470 titles were made for the system, such as *Pokémon Gold, Silver and Crystal*, *The Legend of Zelda: Oracle of Ages*, *The Legend of Zelda: Oracle of Seasons*, *Super Mario Bros. Deluxe* among others.
7. Only requires two AA batteries and still has a long battery life.
8. No region locking like the original Game Boy.
9. It had a cool series of commercials with a talking pair of lips similar to the lips in the old Dairy Queen commercials.

## Bad Qualities

1. Just like its predecessor, the screen has no light and is also rather small. Thankfully, you could get the worm light for the Game Boy Color or mod it to easily fix that problem.
2. Also like its predecessor, the screen will decay if reflected by the sun for too long.
3. A lot of shovelware and bootleg games made it to the system.

## Reception

Combined, both the original *Game Boy* and *Game Boy Color* sold 118.69 million units worldwide.

## Trivia

* Depending on who you ask, some may consider the Game Boy Color as a revision of the Game Boy itself instead of a successor due to the fact that many of its games work on the Game Boy normally.
GameInfobox

```
{{GameInfobox
}}

```

# Example

Notes: Use the operator <br> in source mode to add linebreaks within the table. Sections left blank will not be displayed. The title that appears at the top of the infobox will be the same as the name of the page it is on. Note that the picture field requires the extension (.jpg, .jpeg, .png) to be present, and requires that the File: or Image: part of the link *not* be present.

Using the following:

```
{{GameInfobox
}}

```

Results in the following (normally aligned on the right of the screen):

GameInfobox
Cleanup

## Usage

Add this to pages that need cleanup to meet our rules and guidelines.

**Note: If a page is very short, has generic and/or short reasons or is blatantly unfinished, mark it for deletion instead.**

## TemplateData

Tag a page for cleanup.

Note: If a page is very short, has generic and/or short reasons or is blatantly unfinished, mark it for deletion instead.

Template parameters
FC Twin

Template:ConsoleInfobox
The **FC Twin** (also known as **FC X2**) is a Famiclone console released in 2006. It was made by Qi Sheng Long and Yobo Gameware. The best feature of the console is that it can play both NES and SNES cartridges and it also has two processors: an 8-bit processor for the NES games and a 16-bit processor for the SNES games.

## Why It Rocks

1. It uses the same hardware with the NES and SNES, making it compatible with most of the games of them.
2. It's **very** cheap (selling at around $60), a factor that makes it a good choice for people who don't have enough money to buy both a NES and a SNES.
3. Despite having some issues with the compatibility, newer models solved this problem.
4. It's also compatible with actual SNES controllers.
5. It has a processor switch, making it easy to switch between 8-bit and 16-bit games.
6. It's very easy to find, commonly on mh:rottenwebsites:eBay and mh:freshwebsites:Amazon for smaller prices.
7. The design of the console is slim, and the console is even smaller than both the NES and SNES consoles.
8. It comes in different colors.
9. The console is yet **still** being produced to this day since 2006.

## The Only Bad Quality

1. Some games are not compatible on the console. Thankfully, it was resolved in later models.

## Reception

The console sold more than a million units and was praised for its compatibility with the majority of the Nintendo games and for using the same hardware with these consoles.
Virtual Reality

File:OculusRift.jpg
***Virtual Reality*** (*VR* For short) is a term that's used for games and devices that involves interactions between a human and a virtual world in some way. Nowadays, people mostly think about Virtual Reality Headsets (like *Oculus Rift* or *PlayStation VR*) when they hear the term.

Most VR Headsets can be used when they are connected to a Computer or Game Console.

## Why It Rocks

1. Lots of VR Headsets to choose from, made by Oculus, HTC, and even Valve!
2. SteamVR supports most of the headsets, and makes it easy to configure them.
3. Lots of great titles, such as *Half-Life: Alyx*, *Job Simulator*, *VRChat* and *Beat Saber*.
4. You can interact with anything (depends on the game) only using 2 wireless controllers (or gloves) acting as your virtual hands.
	* Modern controllers or gloves can detect your finger's movement too.
5. It is in stereoscopic 3D!
6. The PlayStation VR is a nice cheap alternative, and only requires a PlayStation 4 to play. You can even use Move controllers, which was a nice touch from Sony.
	* You can also connect it to a Computer if you really want to.
7. John Carmack (id Software's genius programmer) also worked on Oculus Rift headsets.
8. The Oculus Quest is a portable VR Headset, and thanks to the portability, you can play VR Games anywhere.
	* It can also do Hand tracking without the use of controllers.
9. You don't need a whole room to walk around, you can also play in a standing or sitting position (depends on the game).
10. If you are close to a wall or border, the VR Headset will show the outlines.
11. It's not only used for video games, but also used for medical and military simulations.

## Bad Qualities

1. Very early VR Headsets were really primitive.
2. Google Cardboard can be very lackluster at first.
3. They still cost a lot of money, that's not even counting the consoles or PCs you'll need for them.
4. A lot of shovelware titles from the early days.
5. Requires a powerful computer to plays the games smoothly.
6. Setting up one can be a pain.
7. Most VR games can be really short.
8. For certain people it can cause headaches and eye strain.
	* The best way to get used to VR games is to only use them for small times, like 5 minutes first, then 10 minutes, then 20 minutes, and so on, until you get used to it.