Topic: [Gui] Button lock

[Yona-TYT]

I need to block some buttons that can break the tutorial scenario.

These are the highest priority:

Remove and Remove Now: If the vehicle is sold, it will no longer be possible to recover it.

Go to depot: If you advance step / chapter and a vehicle is sent to the warehouse, you will not be able to start it again.


Trying to solve these problems would complicate things much more, that is why blocking the buttons is the best solution.

[prissi]

I do not like the idea to block buttons. Scripting the UI will open a new cans of worms. Moreover, the tutoial should present the real UI. And if the user click on these, you can easily find out the convoi is missing. I mean a tutorial has not to be too much restricting.

[Yona-TYT]

@Prissi
My biggest concern is that the tutorial can stagnate in one step / chapter. 

During the whole tutorial, player can do stuff unrelated to the tutorial and is likely to break the tutorial at any point (nobody knows how a beginner thinks :p ). Would it be possible to implement things so that a player can only do the expected action ? I mean, instead of forbiding any other actions we can think of, forbid anything that is not a precise action ? That would make coding the scenario much easier and the scenario itself will be much more resistant to bugs.

[IgorEliezer]

My biggest concern is that the tutorial can stagnate in one step / chapter. 

During the whole tutorial, player can do stuff unrelated to the tutorial and is likely to break the tutorial at any point (nobody knows how a beginner thinks :p ).

Can the player simply resume the tutorial back to the point where he got "distracted"? (Feature request?)

I usually like to explore and test things while I'm learning something. For me it's part of the learning process. We should rather help players follow the learning track (guidance) than restrain curiosity.

[Yona-TYT]

So far the only thing that can damage the scenario are the vehicles (as far as I can see).

I was thinking, do the vehicles have a unique id on the map? ... if this is true then I can use this to determine which vehicle was deleted / sold. 

[Dwachs]

What do you want to achieve? You could continuously loop through all convoys of the player to check whether they succeeded.

The list of convoys can be accessed with world.get_convoy_list().

You could also save the convoy_x instances and check them later:

Code: [Select]

// cnv - convoy_x instance saved somewhat earlier
try {
     cnv.get_pos() // will fail if cnv is no longer existent
     // do your checks
}
catch(ev) {
     // we are here if cnv is not longer available
}


[Yona-TYT]

Can the player simply resume the tutorial back to the point where he got "distracted"? (Feature request?)

You gave me an idea, I'll try something similar.

[Yona-TYT]

What do you want to achieve? You could continuously loop through all convoys of the player to check whether they succeeded.

The list of convoys can be accessed with world.get_convoy_list().

You could also save the convoy_x instances and check them later:

Code: [Select]

// cnv - convoy_x instance saved somewhat earlier
try {
     cnv.get_pos() // will fail if cnv is no longer existent
     // do your checks
}
catch(ev) {
     // we are here if cnv is not longer available
}


At the moment it is very complicated to exclude the vehicles inside the depot, I need to count only the vehicles in circulation. 

[Dwachs]

There is convoy_x::is_in_depot in r8235