Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add F-G lettered article stubs from glossary #3827

Merged
merged 18 commits into from
Sep 2, 2020
Merged
Show file tree
Hide file tree
Changes from 14 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 18 additions & 1 deletion wiki/Beatmaps/Beatmapsets/Guest_difficulty/en.md
Original file line number Diff line number Diff line change
@@ -1,11 +1,28 @@
---
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/)*
Pennek marked this conversation as resolved.
Show resolved Hide resolved

A **guest difficulty** (***GD***) 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 mappers is also known as a [collaborative difficulty](/wiki/Beatmaps/Beatmap_collaborations).

There are many reasons for guest difficulties to exist:
MegaApplePi marked this conversation as resolved.
Show resolved Hide resolved

- Etiquette in the community can make it difficult for multiple creators to upload beatmaps of the same song around the same time.
MegaApplePi marked this conversation as resolved.
Show resolved Hide resolved
- The guest creator, interested in creating a beatmap for a song, may choose to contribute a difficulty to an existing beatmapset instead.
- The guest creator may also decide upon playing a beatmap that they want to create a difficulty for it.
- The guest creator did not want to put in the effort in creating the difficulties on their own, but would rather just create one and give it to another creator.

On the other hand, it may be the creator who wants a few guest difficulties:
MegaApplePi marked this conversation as resolved.
Show resolved Hide resolved

- To give the mapset a "community effort" feel.
MegaApplePi marked this conversation as resolved.
Show resolved Hide resolved
- The creator did not want to create the difficulties themselves

Some [modding queues](https://osu.ppy.sh/community/forums/60)<!-- TODO: should link to an article about queues, not the forum --> take requests for creating guest difficulties.
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

**Fail** may refer to:

- 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** (***FC***) 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, sliderbreaks<!-- TODO: link -->, 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, full combos will award the most [score](/wiki/Score) in the [osu!standard](/wiki/Game_Modes/osu!), [osu!taiko](/wiki/Game_Modes/osu!taiko), and [osu!catch](/wiki/Game_Modes/osu!catch) [game modes](/wiki/Game_Modes).
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.
12 changes: 12 additions & 0 deletions wiki/Geki/en.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
---
stub: true
tags:
- "300"
- perfect
---

# Geki

**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 which the [osu!standard](/wiki/Game_Modes/osu!) [game mode](/wiki/Game_Modes) is based on.
MegaApplePi marked this conversation as resolved.
Show resolved Hide resolved

<!-- 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) at 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, Flashlight, or Fade-in [game modifiers](/wiki/Game_Modifiers).

<!-- 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 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 on the right-hand side of the [beatmap editor](/wiki/Beatmap_Editor). Enabling it will force every [hit object](/wiki/Hit_object) that is interacted with to snap to the nearest position along the intersections of the grid.

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 align objects and patterns more easily.

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

<!-- TODO: Add links-->