Esta é uma versão antiga. A versão atual é 5.6.285. GDevelop 5.6.285 · Lançamento:
Arquivos de instalação 5.6.278
| Arquitetura | Tipo | Escopo | Tamanho do arquivo | Baixar | SHA256 |
|---|---|---|---|---|---|
| 64 bits | EXE (NSIS) | Usuário atual | — | github.com | VirusTotal |
| 64 bits | EXE (NSIS) | Todos os usuários | — | github.com | VirusTotal |
O link e o SHA256 vêm do manifesto comunitário do Gerenciador de Pacotes do Windows. Compare o hash do arquivo baixado antes de executá-lo.
Notas da versão
🗺️ New experimental "navmesh-based" pathfinding behavior for 2D and 3D
This pathfinding works in 2D and 3D is more flexible than the "grid-based" existing pathfinding. Use the "Pathfinding character" behaviors on the object that must move and add the "Floor/obstacle for pathfinding" behavior to all objects where characters must be able to walk or consider as obstacles (or for 2D: only on obstacles). Read more about it in this documentation page.
- For 3D models, you can optionally choose, like for 3D physics, to follow the exact mesh of the 3D model for pathfinding - allowing characters and objects to move on or around the 3D model naturally.
- It handles "crowds" of characters, which can all go to a destination avoiding each others:
https://github.com/user-attachments/assets/977cd96a-b1c4-463d-b070-4247cbe68cbd
🏃♂️ [Advanced] Add experimental gameplay tests
A gameplay test plays a game: it presses keys, moves the mouse, touches the screen, then checks that what should happen actually happens. For example, if the coin is collected, the score goes up, the enemy hurts the player... Tests run in a preview of the game, usually much faster than real time. Read more about them on this page.
These tests are helpful for:
- Catching regressions: after changing events or objects, re-run your tests to make sure the basics are still working.
- Reproducing difficult bugs: use the test to set up your game to reproduce then fix a bug.
- Checking performance: measure how long frames take with many objects on screen and catch slowdowns early.
ℹ️ Gameplay tests are an advanced concept and are created using code to be as close as possible to the engine running the game.
- If you're a beginner, it's a good idea to start asking the GDevelop AI to build a simple gameplay test for your game or learn from examples in the docs.
- Whether your game is simple or complex, it's recommended to begin by making a very simple gameplay test to get started. You can then progressively create gameplay tests whenever you fix a bug or want to ensure something works in the game. Game studios or advanced users can also run the gameplay tests directly from the command-line.
💝 Improvements
- Add preview of color parameters in the event sheets (thanks @Bouh!)
🕹 Examples
- Add basic gameplay tests to starters
🕹 Premium Game Templates
- New game template: Wordheme, a Wordle-like game by @Bouh
