I think I’d prefer some sort of link made under the hood to just update PARAM1 to PARAM2 if the parameter is moved down, it’s easier to type out PARAMX without having to look at the names of each parameter or to consider creation order, and it’s an added bonus if you have lots of similar functions that you can easily copy paste the descriptions over and only change a descriptive word or two instead of redoing the whole description. Otherwise I find the current implementation to be pretty good
This sounds like a good middle ground.
This actually bothers me a lot, I really don’t like typing _PARAMX_. I made a feature request a few months ago for some easier way, like buttons, dropdown menu etc.
What am I seeing here? Zero diving into GDevelop’s extensions?
Is this some kind of fake news?..
Anyway, I’m all for it if it’s about simplifying things.
However, I really don’t want to end up having to rework all the actions I’ve already added to my project.
also the Eldarduil guy above said something cool about tags
papu zero was diving into that forest long time ago
I just made camp fire in 1 spot and was sitting there for a while so i did not dive to deep
But due some stuff i needed to make (or more likely math i realized is possible) i needed to explore extensions a little bit more
Try reading autotile guide
You will love it (NOT)
But functionality alone you will like
BTW my request WOULD NOT force any1 to modify anything
It would only add ability to do something in a different way
Imagine right now we only have action to change sprite animation by number
And i just requested to add action to change animation of sprite by animation name
NOTHING was removed/replaced
Only some ability was added
I tried an implementation of the auto-remapping on move:
Implement parameter remapping after moving parameter(s) by AnseloOriginal · Pull Request #8989 · 4ian/GDevelop
If Gdevelop maintainers accept the changes, there might be a feasible path to implement what @ZeroX4’s requested but only a patch work and not a real C++ rewrite.
It can be that:
PARAMX are automatically converted back and forth between the objects names.
When a user wrties the name as PARAMNAME it converts it back to PARAMX in the background before passing it to the C++ side. Then when we display it to the user we convert it back to the name PARAMNAME. As I said its sounds alot like something that can easily break or go out of sync but its all really staying as PARAMX but we are converting it back to the object name to display to the user. It should also be able to be switched off in preferences, so it by default be turned off.
So it remains PARAMX on the project side and OBJECTNAME when it is actually being displayed.
@Silver-Streak I would love to hear opinion on this idea.