Good morning all, I will be giving a bit breather time for myself and will then plan for July work schedule.
About the bug that literally kept me up till 03:00 am and then took some more time was this:
You have these instances based on scenes so in 2nd friendly game the flow should go in hierarchical or logical order right;
friendly01 set true in it’s scene and friendly02 set true so it will be ok.
So at the test window - quick test - when I see that friendly02 is followed by friendly01 scene I realized the error. So I immediately went to friendly02match scene and at the top
*set friendly01 false . Also realized that booleans are not good for multiple purpose tracking if you are not turning them of.
The last scene was literally turning back to the end of first game part so it was confusing and I was checking lines after lines of codes to see if mistakenly forgot something there.
Same issue was happening in my practice sub - I solved it much practically:
*comment *if return_to_scene = "morningm15"
*if calendar = 15
*goto_scene morningm15 endmorningmeeting
*comment *if return_to_scene = "after1stgame"
*if calendar = 20
*goto_scene after1stgame training_report
*comment set calender 20
*comment *if return_to_scene = "anewdawn"
*if calendar = 22
*goto_scene anewdawn training_complete
*comment set calendar 22
*comment *if return_to_scene = "path_phonebook"
*if calendar = 22.5
*goto_scene path_phonebook decision_making
*comment set calendar 22,5
I saw that : *if return_to_scene is not working smth a miss. So realized that best issue is giving numerical order since my game is following a timeline.
So instead of new booleans (which I prefer for path making not scene following right now) set a calendar variable . So it make it much practical to follow.
These two plus my error on this below made most scenes and paths unaccessible.
*if gender ="male" // should be "Male"
content
*if gender = "female" // should be "Female"
content
So after a short break I will be back to torture myself again 
