EloiStree / HelloUnityPackage

Exporation of how we can use Git and UnityPackage to create toolbox
https://eloistree.page.link/toolbox
Other
0 stars 1 forks source link

Post-Mortem: First workshop "Magic Doors" #30

Open EloiStree opened 4 years ago

EloiStree commented 4 years ago

For three weeks, we did a workshop with the Belgian students of Technocité call Magic Doors.

The workshop was a success, I am planning to re-iterate the experiment. This post is a postmortem to make a review of how it happens. And how to improve the next workshop.

EloiStree commented 4 years ago

What is Magic Door ?

https://youtu.be/KD47s4uWAIw (Not the last version)

EloiStree commented 4 years ago

What was produced at the end ?

Room of the project
https://youtu.be/K0l-NOrVU0c Downlaod the game:
https://eloistree.itch.io/magicdooratelierdegroupetechnocite

Video

Youtube Video Youtube Video Youtube Video

EloiStree commented 4 years ago

What went well ?

EloiStree commented 4 years ago

What when wrong ?

Sample scene

Licensing

Some participants did not understand that they could create dependency to paying asset on the store. Leading them to put some asset in the package that was public for the project. (We deleted the package immediately).

EloiStree commented 4 years ago

What do I tip you to avoid?

What do I tip you to do?

EloiStree commented 4 years ago

What I learned ?

Always evolving

You need plenty of tools

To reduce the time lost when you do the package or when you use the package, you need plenty fo tools. And that request a learning curved and some tools that don't bug. Else you start losing a lot lot lot of time.

80% Package 10% Project 10% Bridge Script

More you use the package, more you start truning your project in a link of package that are linked to the small part that is creating your project.

But the weak point of that is that you start to transform everything you do as a package. Lot's of bad stuffs happens with that (Explain later). Main weakness of that is that when you want to update a small part of the game. It takes 2-4x more time that your team need you to do it.

Pierre Gueran gave a good tips & trick about that: "Don't do a package directly in the project. Start by doing the code for your team. Next project you required the package. Start to schedule to package it."

Fork

How and why you should use the power of Fork in the project.

Correction

During the weekend, the participant are not available. So if you want to change the code, you have only one option.

Risk of rage quit.

During the end of the project. I know it would not happens, but I was sitting on a new dilemma. "What would happen, if a student in the future set it project in private, move it, or remote it from the server ?" As soon as you update your project, you have error that would appear, the time you understand what is happening, you will probably lose the copy of the local code of the user and your project is screw...

So what do you do in this case ?

  1. Try to understand it soon enough and copy the package in the temp folder.
  2. Try to make a fork of the project and update it regularly just in case.
  3. When you are sure that you won't update it in the future. Just stop using it as a package and import it as a tool in your asset folder.

I suppose there are other solution. But for the moment it is all I have in head.

EloiStree commented 4 years ago

Experiment

Google Sheet to synchronize the team work.

Group workspace: Google Sheet To be able to synchronized the group, we used a google sheet where people can comment the link of their assets. The project leader check some time to update the google sheet and refresh the page with comments.

EloiStree commented 4 years ago

The workshop

Before we start, the workshop scheduling was not to teach only the package manager but the virtual reality to participant that don't own virtual reality.

You can find in the following part, the scheduling given to participant durant the workshop. In future version, more space should be given to design and coder. And the workshop should be shuffle and not split as we did if we want to have a game and not a portfolio application. ;). That my bad. The workshop what not plan as a workshop group work at it before COVID construction.

Google Sheet: List >

Art

Day 1 - Day 2 - Day 3 - Day 4 - Day 5 - Day 6

Code

Day 1 - Day 2 - Day 3 - Day 4