v.0.5.1
Improvements While in spectator-mode, flying through walls is now possible While in spectator-mode, pressing the left mouse button speeds up movement
Rico-Jump
- Released
- Jan 24, 2021
- Platforms
- Last updated
Technical data
Improvements While in spectator-mode, flying through walls is now possible While in spectator-mode, pressing the left mouse button speeds up movement
Feature Spectator-Mode (press 'v' while playing)
Fix: Replay character's hat not being removed when character is removed Prevent switching levels when replay data is still being uploaded Improvements: Added information about global illumination (high GPU utilization)
Fixed shortcut on 1-9
Rico-Jump is back! With this update, a new mechanic is introduced: Replays! For any entry in the global leaderboard you can now replay their run and see for yourself, how they achieved their times! Simply right-click on the leaderboard to show your mouse and then click the 'R'-ic
With this update you are now able to upload custom models in the Map Editor. Please see the respective Guide on how to do it. Further additions: - minor fixes for the map editor - added a help-message to the map editor - added multiple movement-arrows to the map editor for differ
Fixes: - The new wall now loads as intended in the map editor - The wallrunnable-option in the map editor is now saved and loaded when loading a map
Bug fixes: The death-trigger (or Z-kill zone) from custom levels was adjusted to be equal to that in the map editor Players no face the correct way when respawning Fixed a bug where checkpoints in custom levels might not have particles Additions: You can now make walls wallrunnab
- Fixed a bug where the tutorial would not start and you simply continue falling - First preview of new map editor functionality
The Discord-Link was changed to a permanent rather than a temporary one. This resulted in players getting kicked automatically from the Discord-Server after a while.
Bugfixes: (Hopefully) fixed the bug, where multiple global leaderboards appear in the Tab-View Achievement 3_4 now unlockes as intended
Additions: Level 3_4 is now available Achievement for level 3_4 added Finishing a Multiplayer-Run now indicates the time to all connected players in the upper left corner Added a button to the official Rico-Jump Discord-Channel Bugfixes: Multiplayer lag (rubberbanding) should be
Added Tier 3 to the leaderboard in the main menu
This is a smaller update to address the few reviews Rico-Jump got stating it might be a crypto-miner, which is utter nonesense. However, I can understand where this comes from, as the GPU-usage is always >90% while playing Rico-Jump. The reason for this is simple, I disabled V
Tier 3 is now available and introduces a new mechanic: Wallrunning! Use the walls to your advantage by running along them and increasing your speed by jumping from them. Three new levels await you in the new Tier 3 to practive and show off your wallrunning abilities. Further, new
Tier 2 is out now! New mechanic: Bunny-Hopping With version 0.2 of Rico-Jump a new mechanic is introduced: Bunny-Hopping . Alongside it, Tier 2 is now available with 4 brand-new levels. These new levels serve as a tutorial to introduce the new mechanic. Bunny-Hopping is a hard to
With this update you can now access the leaderboards for all levels (Singleplayer and Multiplayer) from the Main Menu. This includes an actual podest showing the players occupying the the first three places (*wow* *such cool*)! Additional minor improvements: - Arrows now do not b
- Level 1_9 now provides more information on the path to take - Changed controls in the options menu are now saved and do not reset after game exit - It is now possible to assign the mouse wheel in the controls option menu - Single player levels now show a "Next Level"-button upo
- Global scoreboard now correctly displays cyrillic text instead of question marks - The chat now scrolls all the way down if a longer text was send - The chat now does not send empty text messages
- The time displayed after finishing a singleplayer-level is now the time of the current run, instead of the fastest one, as it was intended to be (thanks @Igiava)