Quote:
Originally Posted by klem
What I had hoped for was a bank of these modules with a basic very brief explanation of their purpose so that we could interpret, learn to understand and use. Studying existing modules is one way but is long and laborious as you first have find one that may contain what you want, understand what the script module is trying to do and you still may not find what you are looking for.
|
I was as frustrated as you are when I tried to make a mission for Repka #1 back in April. It was even worse because there were no examples available.
Now there are plenty of examples and missions posted in this section. Of cause it is not easy to find them if you did not follow the discussion from April. It takes time, weeks and months, to learn something new.
If you tell what modules you would like to use in your mission I will try to tell you in which threads/examples they are available.
It is better to start a new thread for each new module you need. Kodiak and other people knowing C# are very helpful and helped me a lot even back in April not having any manual (they just looked up lists of methods, etc. from .dll files in Visual Studio):
Quote:
Visual Studio will let you see all of the methods in roundabout way. Try this:
1. File >> New >> Project Type in a name and solution name at the bottom. Don't worry about what kind of project you create.
2. On the right side under "Solution Explorer", right click on "References", "Add Reference..."
3. Click on the "Browse" tab, navigate to "Steam/steamapps/common/il-2 sturmovik cliffs of dover/parts/core"
4. Go through each .dll file in that list and try to add it. Some will give you an error, just skip those.
After you've added all the .dll files, right click on the name of your project and do "Add Existing Item". Find one of your script files and add it. Now Visual Studio will show you all the possible methods as you're typing your code. You can also go to View >> Object Browser and have a look in there.
Important: When you import an existing item, Visual Studio makes a copy of the file so any changes you make won't be reflected in the original file, you'll have to copy the new one over it. If anybody knows how to change this, I'd be quite grateful.
|
Sorry, do not remember who posted this
This shows that for people who know C# it is really easy to learn everything needed from game dll-s themselves.