Skip to content

Commit 5962c74

Browse files
committed
reorganise information in lazer-related articles
1 parent db2aadd commit 5962c74

File tree

6 files changed

+101
-176
lines changed

6 files changed

+101
-176
lines changed
Lines changed: 53 additions & 153 deletions
Original file line numberDiff line numberDiff line change
@@ -1,61 +1,12 @@
1-
# osu!(lazer) feature comparison
2-
3-
*For a more condensed list of features, see [Help centre/Upgrading to lazer § Feature comparison](/wiki/Help_centre/Upgrading_to_lazer#feature-comparison)*
4-
5-
This page documents all new and missing features compared to osu!(stable), as well as differences affecting gameplay.
6-
7-
## New features
8-
9-
- Cross-platform support
10-
- Native Windows 8.1+, macOS, Linux, iOS, and Android support,
11-
- Mobile input methods for all game modes
12-
- Input
13-
- Built-in tablet driver
14-
- Midi controller support
15-
- Gamepad support
16-
- Redesigned interface
17-
- First-run setup wizard
18-
- Storyboards in the main menu
19-
- Rewind F2
20-
- Hiding difficulties
21-
- Soft deletion
22-
- More screen scaling options
23-
- Settings can be changed everywhere and they'll take effect immediately
24-
- New statistics in the results and song select screens
25-
- Website integration for leaderboards, news, wiki, changelog, beatmap listing, beatmap info, and profile pages
26-
- Lots of new mods
27-
- Mod customisation options
28-
- New multiplayer features
29-
- New "playlist" feature
30-
- Unlimited lobby sizes
31-
- Automatic beatmap queues
32-
- New editor features
33-
- Per-segment curve types for sliders
34-
- Slider splitting and merging
35-
- New "verify" tab
36-
- Support for custom game modes
37-
- Gameplay
38-
- Two new built-in skins
39-
- Replay seeking
40-
- Beatmap (local) offset auto-calibration
41-
- Built-in skin editor with customisable skinning components
42-
- Song density graph
43-
- Performance points counter
44-
- Unstable rate counter
45-
- Longest combo counter
46-
- Custom text components, beatmap information displays
47-
- Custom static sprites
48-
- Judgement counter
49-
- Clicks per second counter
50-
- Snaking out sliders in the osu! mode
51-
- No black bar behind the playfield in osu!taiko
52-
- Timing-based note colouring in osu!mania
53-
54-
## Gameplay differences
55-
56-
### General
57-
58-
#### Song playback ramps up and down when pausing and unpausing
1+
# Gameplay differences in osu!(lazer)
2+
3+
*For a comparative list of features between lazer and stable, see [Help centre/Upgrading to lazer § Feature comparison](/wiki/Help_centre/Upgrading_to_lazer#feature-comparison)*
4+
5+
This page documents differences affecting gameplay in osu!(lazer).
6+
7+
## General
8+
9+
### Song playback ramps up and down when pausing and unpausing
5910

6011
This makes it harder to continue from a pause in the middle of active gameplay, preventing abuse of pausing to some extent.
6112

@@ -66,9 +17,9 @@ This makes it harder to continue from a pause in the middle of active gameplay,
6617
| Intentionally changed | Yes |
6718
| Needs further consideration | Yes |
6819

69-
#### The Easy mod no longer pauses gameplay when recovering from failure
20+
### The Easy mod no longer pauses gameplay when recovering from failure
7021

71-
<!-- paragraph? -->
22+
Instead of pausing gameplay while filling up the health bar, health is restored immediately.
7223

7324
| | |
7425
| :-- | :-: |
@@ -77,7 +28,7 @@ This makes it harder to continue from a pause in the middle of active gameplay,
7728
| Intentionally changed | No |
7829
| Needs further consideration | Yes |
7930

80-
#### The health system is different
31+
### The health system is different
8132

8233
This is mostly due to changes to the judgement system. For example, Geki and Katu judgements do not exist in lazer, which affected health on stable.
8334

@@ -88,7 +39,7 @@ This is mostly due to changes to the judgement system. For example, Geki and Kat
8839
| Intentionally changed | Yes |
8940
| Needs further consideration | Yes |
9041

91-
#### All game modes use the same grading system
42+
### All game modes use the same grading system
9243

9344
All game modes use a grading system similar to the one in osu!mania on stable (c.f. [Grade](/wiki/Gameplay/Grade)).
9445

@@ -108,7 +59,7 @@ All game modes use a grading system similar to the one in osu!mania on stable (c
10859
| Intentionally changed | Yes |
10960
| Needs further consideration | Yes |
11061

111-
#### Hit window edge calculations do not match stable
62+
### Hit window edge calculations do not match stable
11263

11364
When a hit lands right at the edge of the hit window, a different judgement may be given depending on the client version.
11465

@@ -125,9 +76,24 @@ When a hit lands right at the edge of the hit window, a different judgement may
12576
| Intentionally changed | Yes |
12677
| Needs further consideration | Yes |
12778

128-
### osu!
79+
### Differences in scoring
80+
81+
Scoring in lazer will use a system similar to ScoreV2, with all ScoreV1 scores converted into the new system.
82+
83+
There are two interchangeable display modes for scores: *standardised* and *classic*. Standardised scoring limits score to a maximum of 1,000,000 points + bonus and score multipliers (similarly to ScoreV2), while classic scoring is the same as standardised, but scaled quadratically with the amount of hit objects in a beatmap (similar to ScoreV1). These can be selected from the settings, with all places were score is displayed in-game changing accordingly.
84+
85+
There are also some differences in how much score each hit object and each judgement is responsible for relative to each other.
86+
87+
| | |
88+
| :-- | :-: |
89+
| Breaks backwards compatibility | Yes |
90+
| Classic mod revert support | No |
91+
| Intentionally changed | Yes |
92+
| Needs further consideration | Yes |
93+
94+
## osu!
12995

130-
#### Notelock has been adjusted to be more lenient
96+
### Notelock has been adjusted to be more lenient
13197

13298
![](img/notelock.gif)
13399

@@ -140,7 +106,7 @@ Recovering from a miss in dense patterns has been made easier.
140106
| Intentionally changed | Yes |
141107
| Needs further consideration | No |
142108

143-
#### Slider head circles require accuracy when hitting
109+
### Slider head circles require accuracy when hitting
144110

145111
![](img/slideracc.gif)
146112

@@ -153,7 +119,7 @@ Until lazer, sliders have only required the accuracy of a 50/MEH judgement to re
153119
| Intentionally changed | Yes |
154120
| Needs further consideration | No |
155121

156-
#### Slider head circle follows track snaking when not hit
122+
### Slider head circle follows track snaking when not hit
157123

158124
![](img/moving-slider-head.gif)
159125

@@ -170,7 +136,7 @@ The rationale behind this change is simple: without it, having `Snaking out slid
170136
| Intentionally changed | Yes |
171137
| Needs further consideration | Yes |
172138

173-
#### Slider ends do not contribute to combo nor cause misses
139+
### Slider ends do not contribute to combo nor cause misses
174140

175141
Slider ends used to have the quirk of not breaking combo (and not causing a MISS judgement) if missed. This meant that an S play, which among other things requires zero MISS judgements, would look like a full combo even if some slider ends were missed. Various debates over whether such a play should be called an FC ensued.
176142

@@ -183,7 +149,7 @@ From now on slider ends will only affect score and accuracy, but have no effect
183149
| Intentionally changed | Yes |
184150
| Needs further consideration | Yes |
185151

186-
#### Missing a slider head causes a miss
152+
### Missing a slider head causes a miss
187153

188154
Missing a slider head (either by not hitting it or hitting it during its miss window) would previously break combo but not cause a MISS judgement, and a judgement could still be received for the missed slider by completing the rest of it. This allowed players to receive the S grade while having a low max combo.
189155

@@ -196,7 +162,7 @@ In lazer, not hitting the slider head will give a MISS judgement for the whole s
196162
| Intentionally changed | Yes |
197163
| Needs further consideration | No |
198164

199-
#### Slider ends do not cause hitsounds when not hit
165+
### Slider ends do not cause hitsounds when not hit
200166

201167
In stable, slider ends would play their hitsounds even if they were missed, as long as any part of the slider was hit. This has been changed such that hitsounds match inputs 1:1.
202168

@@ -207,7 +173,7 @@ In stable, slider ends would play their hitsounds even if they were missed, as l
207173
| Intentionally changed | Yes |
208174
| Needs further consideration | No |
209175

210-
#### The spinner spin speed cap of 477 RPM has been removed
176+
### The spinner spin speed cap of 477 RPM has been removed
211177

212178
Instead of a speed cap, spinners now have a score cap. This was done as a simple initial implementation which may be revised in the future.
213179

@@ -218,7 +184,7 @@ Instead of a speed cap, spinners now have a score cap. This was done as a simple
218184
| Intentionally changed | Yes |
219185
| Needs further consideration | Yes |
220186

221-
#### Aspire-like glitched sliders are not supported
187+
### Aspire-like glitched sliders are not supported
222188

223189
![](img/aspire-slider.gif)
224190

@@ -233,9 +199,9 @@ More discussion and consideration will be needed for how much of Aspire beatmaps
233199
| Intentionally changed | No |
234200
| Needs further consideration | Yes |
235201

236-
### osu!taiko
202+
## osu!taiko
237203

238-
#### Notes that overlap swells cannot be hit
204+
### Notes that overlap swells cannot be hit
239205

240206
Some gimmick maps make use of notes that overlap swells.
241207

@@ -246,7 +212,7 @@ Some gimmick maps make use of notes that overlap swells.
246212
| Intentionally changed | No |
247213
| Needs further consideration | Yes |
248214

249-
#### Drumrolls do not prevent mashing
215+
### Drumrolls do not prevent mashing
250216

251217
In stable, drumrolls could not be hit too quickly or too slowly. This restriction has been lifted, just like in ScoreV2.
252218

@@ -257,7 +223,7 @@ In stable, drumrolls could not be hit too quickly or too slowly. This restrictio
257223
| Intentionally changed | Yes |
258224
| Needs further consideration | Yes |
259225

260-
#### The Flashlight centre is aligned with the hit receptor
226+
### The Flashlight centre is aligned with the hit receptor
261227

262228
<!-- TODO: comparison image -->
263229

@@ -270,9 +236,9 @@ In stable, the Flashlight centre is offset a bit down and to the right, making m
270236
| Intentionally changed | No |
271237
| Needs further consideration | Yes |
272238

273-
### osu!catch
239+
## osu!catch
274240

275-
#### Hyperdash generation can be different in some cases
241+
### Hyperdash generation can be different in some cases
276242

277243
This may lead to inaccurate judgements in replays and increased difficulty.
278244

@@ -283,7 +249,7 @@ This may lead to inaccurate judgements in replays and increased difficulty.
283249
| Intentionally changed | No |
284250
| Needs further consideration | Yes |
285251

286-
#### Juice stream generation can be different in some cases
252+
### Juice stream generation can be different in some cases
287253

288254
This may lead to inaccurate judgements in replays.
289255

@@ -294,9 +260,9 @@ This may lead to inaccurate judgements in replays.
294260
| Intentionally changed | No |
295261
| Needs further consideration | Yes |
296262

297-
### osu!mania
263+
## osu!mania
298264

299-
#### Hold note heads and tails give judgements
265+
### Hold note heads and tails give judgements
300266

301267
This functions similarly to ScoreV2 in stable.
302268

@@ -307,7 +273,7 @@ This functions similarly to ScoreV2 in stable.
307273
| Intentionally changed | Yes |
308274
| Needs further consideration | No |
309275

310-
#### Hold note ticks give score and are responsible for combo breaks
276+
### Hold note ticks give score and are responsible for combo breaks
311277

312278
In stable, releasing during a hold note body would break combo immediately, but now it only breaks when missing a hold note tick.
313279

@@ -320,7 +286,7 @@ This does allow for cheesing (a.k.a. "manipulating") by allowing wrist-jacking w
320286
| Intentionally changed | Yes |
321287
| Needs further consideration | Yes |
322288

323-
#### Extreme scroll speeds are limited
289+
### Extreme scroll speeds are limited
324290

325291
<!-- TODO: how exactly -->
326292

@@ -333,7 +299,7 @@ Some beatmaps with SV gimmicks like teleports or stops do not look as intended,
333299
| Intentionally changed | Yes |
334300
| Needs further consideration | Yes |
335301

336-
#### The PERFECT judgement hit window scales with OD
302+
### The PERFECT judgement hit window scales with OD
337303

338304
This used to be a constant ±16 ms regardless of overall difficulty.
339305

@@ -344,7 +310,7 @@ This used to be a constant ±16 ms regardless of overall difficulty.
344310
| Intentionally changed | Yes |
345311
| Needs further consideration | No? |
346312

347-
#### Converts no longer have different hit windows
313+
### Converts no longer have different hit windows
348314

349315
Beatmaps converted from the osu! game mode into osu!mania had a set of hit windows that were not affected by OD.
350316

@@ -355,7 +321,7 @@ Beatmaps converted from the osu! game mode into osu!mania had a set of hit windo
355321
| Intentionally changed | Yes |
356322
| Needs further consideration | No? |
357323

358-
#### Audio rate adjustments affect hit windows in osu!mania
324+
### Audio rate adjustments affect hit windows in osu!mania
359325

360326
In stable, osu!mania reverts changes to hit windows resulting from applications of DT/HT.
361327

@@ -366,7 +332,7 @@ In stable, osu!mania reverts changes to hit windows resulting from applications
366332
| Intentionally changed | No |
367333
| Needs further consideration | Yes |
368334

369-
#### The Flashlight mod does not have a gradient
335+
### The Flashlight mod does not have a gradient
370336

371337
<!-- TODO: comparison image -->
372338

@@ -376,69 +342,3 @@ In stable, osu!mania reverts changes to hit windows resulting from applications
376342
| Classic mod revert support | No |
377343
| Intentionally changed | No |
378344
| Needs further consideration | Yes |
379-
380-
### Scoring, performance points and leaderboards
381-
382-
Scoring in lazer has been simplified with the main benefit of not requiring a replay to recompute. Two interchangeable systems have been added: *standardised* and *classic*. Standardised scoring limits score to a maximum of 1,000,000 points + bonus and score multipliers, while classic scoring is similar to standardised, but scaled quadratically with the amount of hit objects in a beatmap. These can be selected from the settings, with all places were score is displayed in-game changing accordingly.
383-
384-
There are also some differences in how much score each hit object and each judgement is responsible for relative to each other.
385-
386-
Features that depend on score such as [score ranking](/wiki/Ranking#score-ranking) and [levels](/wiki/Gameplay/Score/Total_score#level) need further discussion for how they will be affected.
387-
388-
Medals do not get awarded. This is a feature that will be enabled after anti-cheat measures have been implemented, and will need further consideration regarding the change in difficulty of some medals due to other gameplay changes.
389-
390-
Performance points are not integrated into global or beatmap-specific leaderboards, but are instead integrated in a separate version of the website for now: <https://lazer.ppy.sh/>.
391-
392-
### Multiplayer
393-
394-
#### TAG co-op mode is not implemented
395-
396-
This is planned, but no work has been started on this yet.
397-
398-
### Storyboarding
399-
400-
#### The storyboard editor is not implemented
401-
402-
There are [designs](https://www.figma.com/file/ytnnne2TH8Z956Jxhiypqq/Beatmap-Editor-2) for an upcoming built-in storyboard editor similar to the one in stable, but no work on this has started yet.
403-
404-
#### The trigger system is not implemented
405-
406-
![](img/sb-triggers.gif)
407-
408-
#### Beatmap backgrounds do not have the correct fill mode for 4:3 storyboards
409-
410-
![](img/sb-bg-fill-mode.jpg)
411-
412-
In stable, beatmap backgrounds and storyboards fill the height of the screen. In lazer, backgrounds fill the width of the screen, while storyboards still fill the height.
413-
414-
This discrepancy causes inconsistent fill modes when a storyboard is overlayed on top of an already existing beatmap background.
415-
416-
#### 4:3-only storyboards are not cropped to the intended aspect ratio
417-
418-
![](img/sb-crop.jpg)
419-
420-
Some storyboards are not designed to support anything other than a 4:3 aspect ratio, but storyboards in lazer always render at 16:9.
421-
422-
## Some cosmetic features are missing
423-
424-
These are features that are planned to come back at some point, but have not due to low priority.
425-
426-
- [Niconico](https://en.wikipedia.org/wiki/Niconico)-style scrolling replay comments
427-
- Combo bursts and their associated sounds
428-
- Countdowns
429-
- Cursor ripples
430-
- Non-skinnable components
431-
- Gameplay leaderboard
432-
- Cutscene skip button
433-
- Section fail/pass
434-
- Results screen
435-
- Song select
436-
- Pause menu
437-
438-
## Technical differences
439-
440-
- Open source
441-
- New user file storage structure
442-
- `Unlimited` refresh rate setting is renamed to `Basically unlimited` and is limited to 1000 Hz
443-
- The mouse cursor is always confined in fullscreen mode
444-
- Support for wider range of aspect ratios
Binary file not shown.
Binary file not shown.
Binary file not shown.

0 commit comments

Comments
 (0)