A very nice intro to finding and installing MOOSE - thanks! One question/comment. @ 17:41 you are showing how you downloaded a developer branch. As of today (21Nov22 - Moose ver 2.7.16), the underlying structure appears to have changed. You might want to comment on how a dev branch can often change parts of the base release which may confuse people. Also, can you briefly tell us why you choose to work with the dev branch instead of the current release (what features you wanted). Given how rapidly Moose is being updated, by the time we are watching, those feature(s) may have already been pulled into the master branch. Again - great job and thanks for doing these!
Hey Josh, thanks for the feedback. Dev branch is always a good starting place as it contains the next class groups and is backward compatible with your older scripts. Many of the basic classes demonstrated in this series can be replaced with the newer classes which create similar results but integrated into simple control like OPS Chief does. The last video in this series will be called “pulling it all together” -creating an immersive environment. This will have an introduction to the future of Moose.
Great video, can you do a video on the RAT script, I can not get some planes to spawn where they should, they won't take off from the airfield or land at mcCarren,
NTTR map has quite a few limits on runways and parking sizes for Ai unfortunately. Not to mention some terrain they can’t out climb. I wasn’t planning on doing RAT in the 10 lessons planned. However if people want more classes covered I will look to do additional ones. Most of the knowledge and techniques used in one class can be easily transferred when using another. As Basic Moose understanding grows you can start to do more complex things. Thanks for the feedback ✌️
@@VELCRO666 go to the moose discord in the Ops RAT channel and put your script file on there, I’ll take a look at it for you. Give me a couple of hours.
I've subbed and will watch these. But a question from someone with no scripting experience and builds missions in ME. What's the benefit of scripting to actual building the mission?
The main benefits of scripting, is it allows you to do more complex missions with way less triggers and overhead. If you watch the lesson on spawning you’ll see what I mean. The reason a trigger action in the ME is do script or do script file is to allow the mission designer to do more. Moose makes it easier to do. Thanks for the sub 👍
Thanks for the Videos! Question: You showed us how to download the sounds as well, what do we do with those? How do they get loaded into the mission? Do we have to setup something similar like the "load moose" trigger? Or do they get loaded when we run the mission with our own Moose Mission .lua containing Airboss for example? Does a dedicated server have to have the sounds downloaded and put into a certain directory too to have them work in the mission or do they get saved in the .miz file?
Could you do a tutorial on how to use the Moose documentation so we can add extra things to our scripts? The documentation often lacks examples of the code in an actual lua file, leaving newbies lost on syntax. It doesn't explain why there are multiple entries for the same function with slightly different naming (Airboss:SetDefaultPlayerSkill vs. Airboss.Difficulty.xxx). It doesn't explain which entries need "local" and which don't, etc. Whenever I ask on the Discord they say "read the documentation" which I already did and don't understand because it has so many information gaps.
Hi mate, what you are asking are really coding conventions. A global variable vs a local variable is simply what block of code it applies to. You could use a global variable and what you define will be used across the entire environment that is loaded in the mission, or by making it local it only apples to what follows in the block. The example :SetDefaultPlayerSkill vs. Airboss.Difficulty.xxx the first is a switch that is defined in the Moose script ie Set default. The second is an argument that you could call to then do something else if it is true e.g If player.Data = Airboss.Difficulty.EASY then , This is not designed so much for basic users of the Moose script but for those who are more advanced. It's sort of outside the basic nature of these lessons. The idea was to show people some basic cut and paste can have you using script in your missions without having to really understand lua. To really take advantage of all those functions in your script or get involved with developing the Moose script. I recommend this as a good reference guide www.lua.org/pil/contents.html#P1
Thanks for those!
Making scripting more accessible for newbies is important!
Coming from a master of DCS scripting I’m flattered. Cheers mate 👍
@@anytimebaby917 now I'm flattered from the title bestowed :)
Thank you - very helpful to finally fill the TARAWA with some Airboss Scripts !
Great video, can't get my volume loud enough though to hear you perfectly.
Fantastic video. Very helpful. looking forward to more in this series especially the Airboss example. Subbed !
Already done L2 putting together and Airboss script, th-cam.com/video/LWccyiuUiSE/w-d-xo.html
Thanks for the feedback 👍
A very nice intro to finding and installing MOOSE - thanks! One question/comment. @ 17:41 you are showing how you downloaded a developer branch. As of today (21Nov22 - Moose ver 2.7.16), the underlying structure appears to have changed. You might want to comment on how a dev branch can often change parts of the base release which may confuse people. Also, can you briefly tell us why you choose to work with the dev branch instead of the current release (what features you wanted). Given how rapidly Moose is being updated, by the time we are watching, those feature(s) may have already been pulled into the master branch. Again - great job and thanks for doing these!
Hey Josh, thanks for the feedback. Dev branch is always a good starting place as it contains the next class groups and is backward compatible with your older scripts. Many of the basic classes demonstrated in this series can be replaced with the newer classes which create similar results but integrated into simple control like OPS Chief does. The last video in this series will be called “pulling it all together” -creating an immersive environment. This will have an introduction to the future of Moose.
Thanks for your efforts!
Thanks a lot for the videos
Great video, can you do a video on the RAT script, I can not get some planes to spawn where they should, they won't take off from the airfield or land at mcCarren,
NTTR map has quite a few limits on runways and parking sizes for Ai unfortunately. Not to mention some terrain they can’t out climb. I wasn’t planning on doing RAT in the 10 lessons planned. However if people want more classes covered I will look to do additional ones. Most of the knowledge and techniques used in one class can be easily transferred when using another. As Basic Moose understanding grows you can start to do more complex things. Thanks for the feedback ✌️
@@anytimebaby917 I was copy and pasting for new aircraft thrn changing names, but nothing spawns , having a nightmare lol
@@VELCRO666 go to the moose discord in the Ops RAT channel and put your script file on there, I’ll take a look at it for you. Give me a couple of hours.
@@anytimebaby917 thanks mate that's awsome of you
I've subbed and will watch these. But a question from someone with no scripting experience and builds missions in ME. What's the benefit of scripting to actual building the mission?
The main benefits of scripting, is it allows you to do more complex missions with way less triggers and overhead. If you watch the lesson on spawning you’ll see what I mean. The reason a trigger action in the ME is do script or do script file is to allow the mission designer to do more. Moose makes it easier to do. Thanks for the sub 👍
Thanks for the Videos! Question: You showed us how to download the sounds as well, what do we do with those? How do they get loaded into the mission? Do we have to setup something similar like the "load moose" trigger? Or do they get loaded when we run the mission with our own Moose Mission .lua containing Airboss for example? Does a dedicated server have to have the sounds downloaded and put into a certain directory too to have them work in the mission or do they get saved in the .miz file?
Hey, see lesson L2 or L6, I explain how to add the sounds to your miz file. Moose on!
@@anytimebaby917 thx!
Could you do a tutorial on how to use the Moose documentation so we can add extra things to our scripts? The documentation often lacks examples of the code in an actual lua file, leaving newbies lost on syntax. It doesn't explain why there are multiple entries for the same function with slightly different naming (Airboss:SetDefaultPlayerSkill vs. Airboss.Difficulty.xxx). It doesn't explain which entries need "local" and which don't, etc. Whenever I ask on the Discord they say "read the documentation" which I already did and don't understand because it has so many information gaps.
Hi mate, what you are asking are really coding conventions. A global variable vs a local variable is simply what block of code it applies to. You could use a global variable and what you define will be used across the entire environment that is loaded in the mission, or by making it local it only apples to what follows in the block. The example :SetDefaultPlayerSkill vs. Airboss.Difficulty.xxx the first is a switch that is defined in the Moose script ie Set default. The second is an argument that you could call to then do something else if it is true e.g If player.Data = Airboss.Difficulty.EASY then , This is not designed so much for basic users of the Moose script but for those who are more advanced. It's sort of outside the basic nature of these lessons. The idea was to show people some basic cut and paste can have you using script in your missions without having to really understand lua.
To really take advantage of all those functions in your script or get involved with developing the Moose script. I recommend this as a good reference guide www.lua.org/pil/contents.html#P1
the volume is bit too low