Toggle to show/hide experimental extensions

This should not be hidden

IDK why it was hidden in such way but i see it as terrible decision
1st barrier is new users can think of it as something bad that can break their game
So they will avoid it and won’t find some extensions
That is already bad idea

2nd barrier is that its now hidden cause user won’t even be curious enough to click it

If by default it is not set to SHOW
Then i am asking for at least bring back it being visible toggle switch button with description it will show experimental extensions

At least this way it will give some chance to users to find extensions they are looking for

Prime example why current design is bad

3 Likes

What is your GDevelop 5 version? I have this button in the form of a toggle switch and it is clearly visible.

Have this function?

  • This is have.
  • This is not have.
0 voters

The 3D sprite extension is a good example:

  • It’s kind of bugged which is why it stays as experimental
  • When it will reach a good quality, it won’t be experimental any more and will always be visible

So, it’s expected that the experimental extensions toggling is hard to find.

This feature request is not about which are experimental or not
Its about hiding that “show experimental” button under these 3 dots

A LOT of ppl use tutorials/guides to create something
They see someone use some extensions and they look for them and they can’t find them

So at least let’s give them better chance of finding them
Even if they are not in perfect shape
They will at least be easier to find by making that button visible
And not hidden


He did understand what you meant, as he said this:

I disagree 100% though with this reasoning. Surely the big purple badge saying ‘Experimental extension’ is enough to warn people. Why should we have to be ‘saved’ twice? We get a warning so why do we need to have the toggle hidden from us as well?

I am well aware he knows cause Davy is one of the smartest person i meet here
And looking at your reply to Davy
And i see you get my point

Issue here is and i repeated it to Davy meany times
He is unable to think like someone who don’t know stuff
And he just looks at stuff as engine developer who knows everything
End user care to find something and use it otherwise it just make user frustrated
So it don’t help any1

That is what Davy fail to understand here and that is what im trying to point out

Choice to hide that button IS RIGHT
But outcome of that choice is NOT so good for end user
And that is what Davy needs to be pointed out

Doing right thing is not always better choice

I also see this in the people who write the wiki.

And to be fair in Davy case and wiki ppl case they are 100% right to be like that
Imagine making tutorial how to plug gfx card to your motherboard

“Take this thing with fans and put it into this thing that looks like long lego block with hole in it”
VS
“Take your gfx card and socket it in into graphic card slot on your motherboard”

Like 1st one would be easier to understand for someone who don’t know anything
Where 2nd one is more accurate
But does that make 2nd one automatically better?
At the same time does the fact 1st one is easier to understand for someone totally green
Automatically makes 2nd one worse?

And then last question and most important
For who is your tutorial?
For ppl totally green or for ppl who have some knowledge?
Cause depending on that answers to above questions will vary

I’m going to put forward an argument not in your favor.
I’m adding an experimental extension, and one time the extension messed up the whole project. I delete it, but it remains in the source code, but it is not visible in the editor. And the expansion keeps spoiling the game! And then you still have to go into the source code of the game to delete the extension manually, but as you said:

And I think it won’t be very easy for beginners to remove the extension through JSON.

I see more cons than pros from hiding that button