Skip to content

Commit

Permalink
Merge pull request #3827 from Pennek/glossary-f
Browse files Browse the repository at this point in the history
Add F-G lettered article stubs from glossary
  • Loading branch information
MegaApplePi authored Sep 2, 2020
2 parents 7b3ce31 + 04c7d02 commit bca2758
Show file tree
Hide file tree
Showing 10 changed files with 87 additions and 4 deletions.
7 changes: 6 additions & 1 deletion wiki/Beatmaps/Beatmapsets/Guest_difficulty/en.md
Original file line number Diff line number Diff line change
@@ -1,11 +1,16 @@
---
stub: true
tags:
- GD
- guest beatmap
- guest difficulties
- guest map
---

# Guest difficulty

A **guest difficulty** is a [beatmap](/wiki/Beatmaps) of a [beatmapset](/wiki/Beatmaps/Beatmapsets) that is not created by the [beatmapset host](/wiki/Beatmaps/Beatmapsets/Beatmapset_host). A beatmap featuring multiple mappers is also known as a [collaborative difficulty](/wiki/Beatmaps/Beatmap_collaborations).
*For regulations surrounding guest difficulties, see: [Ranking Criteria](/wiki/Ranking_Criteria)*

A **guest difficulty** (or *GD* for short) is a [beatmap](/wiki/Beatmaps) of a [beatmapset](/wiki/Beatmaps/Beatmapsets) that is not created by the [beatmapset host](/wiki/Beatmaps/Beatmapsets/Beatmapset_host). They can usually be identified by their difficulty name containing the guest creator's username. A beatmap featuring multiple creators is also known as a [collaborative difficulty](/wiki/Beatmaps/Beatmap_collaborations).

Many guest difficulties are often requested by private messages between creators. Although GDs can also be requested in [modding queues](https://osu.ppy.sh/community/forums/60)<!-- TODO: should link to an article about queues, not the forum -->.
6 changes: 6 additions & 0 deletions wiki/Disambiguation/Fail/en.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
# Fail (disambiguation)

**Fail** can have multiple meanings:

- Not passing a [beatmap](/wiki/Beatmaps)
- Being in the failed state<!-- TODO: link --> during a break<!-- TODO: link --> of a beatmap
1 change: 1 addition & 0 deletions wiki/Disambiguation/en.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,7 @@
- [Bancho](Bancho)
- [Easy](Easy)
- [EZ](EZ)
- [Fail](Fail)
- [Mod](Mod)
- [osu!](osu!)
- [Version](Version)
15 changes: 15 additions & 0 deletions wiki/Full_combo/en.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
---
stub: true
tags:
- FC
---

# Full combo

**Full combo** (or *FC* for short) is a term used to describe a player obtaining the maximum possible combo<!-- TODO: link --> on a [beatmap](/wiki/Beatmaps). Full combos are scored by passing a beatmap with no misses<!-- TODO: link -->, [sliderbreaks](/wiki/Gameplay/Sliderbreak), or dropped [slider ends](/wiki/Hit_object/Slidertail).

Scores that lost combo only via dropped slider ends are widely considered by the community to be full combos. This differs from the game client and website's display.

![Screenshot of full combo and broken combo scores](img/combo-comparison.png "The top score is a full combo, and the bottom score is a broken combo.")

Due to the [combo multiplier effect](/wiki/Glossary/Combo_multiplier_effect), full combos will award the most [score](/wiki/Score) in the [osu!standard](/wiki/Game_mode/osu!), [osu!taiko](/wiki/Game_mode/osu!taiko), and [osu!catch](/wiki/Game_mode/osu!catch) [game modes](/wiki/Game_mode).
Binary file added wiki/Full_combo/img/combo-comparison.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
14 changes: 14 additions & 0 deletions wiki/Geki/en.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
---
stub: true
tags:
- "300"
- perfect
---

# Geki

<!-- *See also: [Katu](/wiki/Katu)* -->

**Geki (激)**, or *Elite Beat!*, is a [scoring](/wiki/Score) term used when a player has completed a comboset with the highest possible [accuracy](/wiki/Gameplay/Accuracy) on every note. This idea originates from the Nintendo DS game Elite Beat Agents in which the [osu!standard](/wiki/Game_mode/osu!) [game mode](/wiki/Game_mode) is based on.

<!-- TODO: Add links-->
13 changes: 13 additions & 0 deletions wiki/Grade/en.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
---
stub: true
tags:
- rank
---

# Grade

**Grades**, in osu!, are a set of letters representing a player's performance on a given [beatmap](/wiki/Beatmaps). Grades accompany the total [score](/wiki/Score) on the result screen and appear in all lists alongside scores.

From lowest to highest, the possible grades are F, C, B, A, S, Silver S, SS, and Silver SS. Silver grades are only achievable when using the [Hidden](/wiki/Game_modifier/Hidden), [Flashlight](/wiki/Game_modifier/Flashlight), or [Fade In](/wiki/Game_modifier/Fade_In) [game modifiers](/wiki/Game_modifier).

<!-- TODO: Add links-->
13 changes: 13 additions & 0 deletions wiki/Graveyard/en.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
---
stub: true
tags:
- dead
---

# Graveyard

The **graveyard** is a subforum for [beatmapsets](/wiki/Beatmaps/Beatmapsets) that have been abandoned by their creator(s). Graveyarded maps do not count towards a user's total upload limit. The [beatmapset host](/wiki/Beatmaps/Beatmapsets/Beatmapset_host) may "revive" a beatmapset by updating it. This requires a free pending slot and sends it back to being a [Work in Progress](/wiki/Beatmaps#work-in-progress-and-pending) beatmapset.

Beatmaps that are not updated by their creator for **28 days** will automatically be sent to the Graveyard.

<!-- TODO: Add links-->
16 changes: 16 additions & 0 deletions wiki/Grid_snapping/en.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
---
stub: true
tags:
- grid lock
- lock
---

# Grid snapping

**Grid snapping** refers to the act of using the `Grid Snap` button functionality in the [beatmap editor](/wiki/Beatmap_Editor). Enabling it will force every [hit object](/wiki/Hit_object) that is interacted with by the creator to move to the nearest position along the intersections of the grid, or, in other words, "snapping." The `Grid Snap` button can be found on the right-hand side of the editor.

The base level of spacing between each sector of the grid can be adjusted by pressing `G`, or by navigating to `View` -> `Grid Level`. Grid snapping can help with aligning objects to each other and attempt to arrang them in neater patterns.

<!-- TODO: Add image of Grid Snap button location or the Grid Snap button itself -->

<!-- TODO: Add links-->
6 changes: 3 additions & 3 deletions wiki/redirect.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -84,6 +84,9 @@
"bancho": "Disambiguation/Bancho"
"easy": "Disambiguation/Easy"
"ez": "Disambiguation/EZ"
"fail": "Disambiguation/Fail"
"failed": "Disambiguation/Fail"
"failing": "Disambiguation/Fail"
"mods": "Disambiguation/Mod"
"mod": "Disambiguation/Mod"
"osu!": "Disambiguation/osu!"
Expand Down Expand Up @@ -268,9 +271,6 @@
"ds_games": "Glossary#ds-games"
"eba": "Glossary#eba"
"elite_beat_agents": "Glossary#eba"
"fail": "Glossary#fail"
"failed": "Glossary#fail"
"failing": "Glossary#fail"
"fc": "Glossary#fc"
"full_combo": "Glossary#fc"
"geki": "Glossary#geki"
Expand Down

0 comments on commit bca2758

Please sign in to comment.