Hidden hints and errors that point
- changelog
Spoilers in chat
Wrap text in double pipes, like ||use a monotonic stack||, and it shows under a solid cover until someone clicks it (or focuses it and presses Enter or Space). It's a way to give a hint in a practice room without ruining the problem for everyone else. Emotes and @mentions still work inside a spoiler. Covered text can't be selected, copied or clicked until it's revealed.
Typing /spoiler <text> hides the whole message. It works in the desktop composer and in the mobile chat input.
Spoilers stay hidden in other places too. A mention notification's preview shows the cover, not the hidden text, and so do chat labels on the replay timeline. To type a literal pipe that should never open or close a spoiler, write \|.
Error lines in the editor
When a Run or Submit fails to compile or crashes, the editor now marks the line the error is about. The line gets a red tint and a bar down its left edge, a mark shows in the scrollbar, and you can hover the line to read the error message. Each mark clears as soon as you edit that line, and they all clear on the next run or when you switch language.
Compile errors are marked in every language. For runtime errors, the editor marks the deepest line of your own code in the stack trace, so a crash inside a library call points at the line where you called it. For a wrapped Java exception, that means the line from its root cause. C++ crashes don't report a location, so they don't mark anything. It works in practice mode and in study groups.
Emotes
- No colons needed. Typing a popular emote name on its own, like
Kappa,LUL,o7orPogChamp, now shows the emote. It needs the exact spelling and a space (or the start or end of the message) on both sides, soKappa!, links and @mentions stay as text. Emote names that are also ordinary words, likemerge,looporgg, still need colons. Older messages pick this up too. - New emotes. SeemsGood (by request) and PogChamp.
- New art. LUL, Kappa and 4Head now use their original art instead of look-alikes.
- No more squished emotes. Chat used to draw every emote in a square box, so wide ones like
o7,LULand the peepos looked squashed. Emotes now keep their shape.
Math in sample explanations
The explanation under a sample case used to support only code. It now takes the same inline formatting as the problem statement, including bold, italics and math like . Existing explanations look the same as before.
Community problems
When you submit a community problem, parameters and return values can now be double or double[]. Answers are compared with the same small tolerance the judge uses for decimals.
Fixes
- Reaction picker. After the reaction picker grew to 24 emoji, they could pile up on one spot instead of laying out in a grid. They're back in their 8-wide grid.