Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Yop2D - No-Code Game Engine

The 100% No-Code game engine to design and export APKs without a PC. · By yop2d_dev

Hello everyone and welcome to the official Yop2D community board! Sticky

A topic by yop2d_dev created 53 days ago Views: 135 Replies: 4
Viewing posts 1 to 3
Developer

If you're here, you probably share my dream: creating 2D games directly from an Android tablet, without needing a PC or writing complex code. I built Yop2D entirely on my tablet because I couldn't find a free engine that fit my needs. Today, I'm thrilled to share it with you.

⚠️ Important Note: Yop2D is designed and highly optimized for Android tablets. Because of the complex visual scripting interface (Blueprints) and the scene editor, it does not work well on smartphones.

Yop2D is still actively in development. It's a passion project, and that's exactly why I opened this space. I want to build this engine with you.

How to use this board:

🐛 Bug Reports: Found a glitch? Let me know here so I can smash it.

💡 Feature Requests: What node or tool is missing for your dream game? Share your ideas!

🎮 Showcase: Post screenshots or APKs of the games you are building. I'd love to see what you create.

❓ Help & Questions: Stuck on a visual script? Ask the community!

To kick things off, don't be shy: reply to this post and introduce yourself! What kind of game are you planning to create on your tablet?

Happy game dev! 🚀

A Discord and Telegram channel are being prepared to share tutorials and tips. 

Developer (1 edit)

Roadmap

🔴 Phase 1: Fixes and Technical Debt Cleanup (High Priority)  

Fixing broken nodes: Repair defective nodes (e.g., NoeudActionClignotement and others) that were impacted by the "lost target" bug (__OBJET_IMPLIQUE__).  

Overhaul of hardcoded translations: Track down and replace all hardcoded strings in recent files so they all use Traducteur.get("key"), to facilitate internationalization without having to dig into the Java code.  

Camera display fix: In CanvasEditeur.java, move the drawing of the camera rectangle to the very end of the render loop so it always appears on top of the objects (essential for visually managing parallax).  

🟡 Phase 2: Touch Ergonomics Improvements (Editor Comfort)  

Blueprint Navigation (Pinch-to-Zoom): Implement the ScaleGestureDetector in CanvasBlueprint.java (as is already the case in CanvasEditeur.java) to zoom intuitively by pinching the screen.  

Floating tool window (Editing Popup): Create a small draggable floating panel in the scene editor, grouping quick actions (Move, Scale, Rotate) near the selected object, to avoid going back and forth with the top menu.  

Assets panel overhaul: Replace the current system of folder creation and separate display with a nested and visually more appealing tree view (TreeView), allowing the contents of subdirectories to be seen directly in the list.  

Snapping tool: Develop a system for perfect object alignment on a grid or relative to the edges of other assets to prevent unintentional overlapping when creating levels.  

🟢 Phase 3: New "Core" Features (Advanced Mechanics)  

The Instantiation Revolution (Scenes as Layers/Objects):  

Upgrade the rendering engine (VueJeu.java) to allow the superposition of multiple scenes on the fly (layer system).  

Create a "Prefabs" (Templates) system: be able to save a complete scene (an enemy with its logic, a complex object) and instantiate it in another scene just like a simple ObjetBase.  

Physics Engine Evolution: Enrich MoteurPhysique.java (which is currently very basic) to offer more dynamic physical behaviors (forces, masses, friction, advanced bounce types).  

Dialogue system improvement: Add advanced visual parameters (customizable background image, color, opacity/alpha level) to the text display system.  

Animation Editor Evolution: Enrich the small animation creation window by adding thumbnail previews and new transition settings.  

Separate Functions Editor (Global Accessibility): Allow independent Blueprint scripts (files stored in the functions folder) to have direct read/write access to the object list, tags, and global variables of the application from the node editor interface

Puedes mejorarlo para teléfonos 

Developer

Hi, yes I'm currently making changes to allow for a more pleasant experience with a phone. I have to change a lot of things, phase 1 is finished, phase 2 is progressing. I hope to finish quickly so I can get back to proposing more physical and object components. The progress bar is finished and functional. I've also modified the assets page. It's now also possible to listen to music and sounds in this window. 

Developer

Hi, have you tested the new version of yop2d on a phone? It usually works well, the user experience is good.Since yesterday, based on user feedback, I'm still making adjustments to make it as pleasant as possible on a phone. You can join us and share your experience, which will help us improve the engine faster. So if this adventure interests you, join us on Discord. You'll also be able to test new versions before everyone else.