Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't Find Level Index Action on Tilemap #4745

Open
akbarhlubis opened this issue Dec 26, 2022 · 6 comments
Open

Can't Find Level Index Action on Tilemap #4745

akbarhlubis opened this issue Dec 26, 2022 · 6 comments
Labels
✨ enhancement 👌good first issue Good issue if you want to start contributing to GDevelop

Comments

@akbarhlubis
Copy link

Describe the bug

I'm trying to add action event sheet for tilemap to change the Level Index based on variable but can't find it at all. actually i don't know is this on purpose or not but i think i need to report it.

To Reproduce

Steps to reproduce the behavior:

  1. Go to 'Scene Events'
  2. Click on 'Add Action'
  3. Scroll down to 'Tilemap Object'
  4. Can't Find 'Level Index'

Screenshots

  • Condition Events
    gambar

  • Action Events
    gambar

Other details

  • Gdevelop version 5.1.154
@Silver-Streak
Copy link
Collaborator

Not sure it's a bug so much as an action that may not exist.

@daiyam Any insight if this is intended to be there but isn't surfaced yet? (if not, can an action be added to update the parameter, since there's already a condition to check it?)

@daiyam
Copy link
Contributor

daiyam commented Dec 26, 2022

@Silver-Streak The action was removed upon the feedback of @D8H (#4575 (comment))

@Silver-Streak
Copy link
Collaborator

Silver-Streak commented Dec 26, 2022

@Silver-Streak The action was removed upon the feedback of @D8H (#4575 (comment))

Thanks for the detail.

@D8H was this broken, or was there another reason we wouldn't want an action to change an object paramater? We can currently change everything else about the tilemap, even change the tilemap file entirely, which is not really any less special use.

I could see a use case where someone uses a single map object multiple times but changes the instance of each one to be a different level via variables and events. (Likewise a parameter that could be changed on instances would be useful)

@D8H
Copy link
Collaborator

D8H commented Dec 26, 2022

@D8H was this broken, or was there another reason we wouldn't want an action to change an object paramater? We can currently change everything else about the tilemap, even change the tilemap file entirely, which is not really any less special use.

I could see a use case where someone uses a single map object multiple times but changes the instance of each one to be a different level via variables and events. (Likewise a parameter that could be changed on instances would be useful)

My guess is that a level or a level part usually comes with objects instances (mobs, collectables...). So, they would be set with the scene editor (maybe in external layouts) and the level would be set by property.
I tough this action would mislead users into thinking that this is the way to change the game level and conclude that GDevelop is not practical to use because they have to delete instances from previous level and add new one programmatically.

But, if you think there is a use case for it I'm not strongly against it. An explanation in the action description can do.

@Silver-Streak
Copy link
Collaborator

Silver-Streak commented Dec 26, 2022

I think you are correct as far as most usecases.

However, since we are not bringing in objects/LDTK entities (and couldn't unless we start adding a reference/entity object), I still think there is could be valid usecases for having multiple instances of a map and changing the level dynamically via events.

That said, if it isn't something to be added for events, it should probably be called out in the object UI that the level cannot be changed at runtime/via events (and the parameter should still be surfaced per instance on the instance properties panel like sprite animations are)

@4ian
Copy link
Owner

4ian commented Dec 26, 2022

Probably need an action for it, but with an alert explaining the limitation/inviting to use "change scene" if people want to navigate in GDevelop scenes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
✨ enhancement 👌good first issue Good issue if you want to start contributing to GDevelop
Projects
None yet
Development

No branches or pull requests

5 participants