Gaulish Gaming Banquet: editor

mr.rubinshtein

either way my main concern was the UI/UX

pegperegogaucho

Yes, because you needed to explain many new concepts, like "Beacons" or "Squads"

pegperegogaucho

The same way you need to learn what a blueprint or an actor or an material is in UE

mr.rubinshtein

yes but my main problem with editor is its weird UI/UX which needs to be dealt with

mr.rubinshtein

i dont ask to change something technical

mr.rubinshtein

its just rearranging

mr.rubinshtein

which shouldnt be that hard cmon

pegperegogaucho

I think what should be done is the following: After Adrien is about to release his v0.2 version of the editor, we hand it over to some absolute noob (like failentin) and observe him use it in order to identify shortcomings.

mr.rubinshtein

reading my mind Spork

mr.rubinshtein

i had the same in my mind

mr.rubinshtein

choose several people and observe them

mr.rubinshtein

during stream

mr.rubinshtein

i have been telling this since the beginning

mr.rubinshtein

but the trick here is that we shouldnt explain them anything on how it works

mr.rubinshtein

like just let them wander around

pegperegogaucho

@adrientd What do you think about visualising events like this? As events get more complex, you lose sight over all of the scripting right now, but maybe it can be solved by displaying events using a graph?

mr.rubinshtein

did you just roughly sketch this?

mr.rubinshtein

because it looks comfortable

pegperegogaucho

Yes, I tried my best :LUL:

pegperegogaucho

Of course it would look better when implemented

#editor