- News, Mods, Addons und Missionen für ArmA3

Montag, 15. Oktober 2018
Downloads » ArmA3 Editing » ArmA3 Co-op Mission Making Framework von Zenophon (24.05.17) [Skripte] Download-Infos
ArmA3 Co-op Mission Making Framework von Zenophon (24.05.17) [Skripte]
24.05.2017 von miller

ArmA3 Co-op Mission Making Framework

Co-op Mission Making Framework.



Benötigte Addons:

Weitere Infos:
Steam Workshop


The framework works with any map and requires no addons. It is compatible with any mod because you choose which functions execute. There is effectively no performance impact to compile the entire framework, and every function has been diligently optimized. All 150 public functions are also carefully documented in an exacting style, and many resources are provided to help you learn to use the framework. The framework is created with these goals in mind:
- Simple co-op fun for both players and mission makers
- Bottom-up design using flexible pieces that you control
- Truly random and dynamic missions without extra work for mission designers
- Procedural mission design instead of manual placement using the editor
- Eliminating large, static functions with assumptions about what you want in your mission
- Server-oriented execution to create more efficient multiplayer missions
-- A simplification of locality and interacting with clients in multiplayer
- A solid, powerful, and bug-free library to use as a foundation for your own code

The framework's many functions are divided into 12 categories with a specific purpose:
.1 The Data functions are the foundation of the framework, supporting both simple and complex operations on arrays and strings.
2. The Fire Support system is a tool for mission makers, not players, to create any imaginable artillery, mortar, or airstrike.
3. The Loadout functions, including a full custom loadout system, provide every option you need to easily equip both players and AI.
4. The Math functions are auxiliary functions that deal with various 2D trigonometric operations on positions and polygons.
5. The Misc functions are just that, miscellaneous. They don't fit in anywhere else, but are still useful.
6. The Object functions deal with objects, and provide numerous ways to check on and interact with players, AI, and static objects.
7. The Objective system is designed to make side missions extremely simple for mission makers with just one line of code.
8. The Orders functions provide a tested and working way to make AI do things, and some offer simple but powerful randomization.
9. The Position system generates random positions, and filters them 10 different ways, allowing infinite possibilities in a single mission.
10. The Spawning functions allow you to spawn any object, AI or static, that you need and offer both straightforward and randomized spawning.
11. The Task system is a complex system are meant to separate the mission maker completely from the issues of tasks, making any task operation simple.
12. The Trigger functions perform operations on tasks based on preset conditions and are designed to complement the Task system.

Beta Disclaimer
The framework is currently in the beta stage of development. That means that even though the majority of planned features are implemented and working, there will be bugs. The entire framework has been tested for hundreds of hours to ensure the greatest possible quality. The majority of functions are working very well, but do not expect flawless software at this point. Even if you cannot stand bugs, I urge you to give the framework a try right now anyway and work around any bugs. The more people who use the framework, report bugs, and give feedback, the faster it will improve.

The included documentation explains how to use each part of this large framework in order to create missions. The documentation set features complete, standardized documentation organized by the categories for all of the framework's public functions. Further standard documentation, such as a changelog, FAQ, etc., are provided.

There is a series of 10 beginner tutorials to help first-time mission makers create simple missions using framework functions. For more experienced scripters, there are 15 intermediate demonstration missions and 8 full sample missions to show more advanced scripting techniques and more framework functions. Other helpful resources, including a Notepad++ SQF language, are provided.

Multiplayer and JIP
The framework was designed with the idea that the server should manage everything that it can, and few to no scripts should be run on the clients. Framework functions are designed to work in a multiplayer environment (dedicated servers too, of course) without the mission designer even considering how or why. Regardless if a mission is singleplayer or multiplayer, the framework's functions will do what they say they will without you changing anything.

The framework (or any function) cannot intrinsically deal with JIP and support it without any changes to your mission. Because you cannot reasonably be expected to divine what you need to do to make your usage of the framework JIP compatible, there is a JIP demonstration mission for you. Using the template there in your own mission, with a some customization, will make your mission JIP compatible.

There will be bugs; this is not a final release, nor will it ever be. I have made every effort to test and debug all 190 framework functions, and that that documentation agrees with the actual code. Bugs are not your fault; they come from some mistake within a framework function. It is not possible to produce bug-free software of this magnitude without mass public testing. This holds true whether or not the framework is still in beta. The development cycle of adding, improving, and fixing things goes on forever.

I assure you that I have every intention of fully supporting the framework for a long time. Fixing bugs and issues will always be my first priority over adding new features or tweaking things.

I am not so arrogant as to think that I have considered everything, have a perfect design and implementation, and have judged the needs of ArmA mission makers fairly. I highly encourage you to submit any suggestion that occurs to you, even if you are not sure about it.

For simple feedback like 'I liked it' or 'I hated it', just use the forum thread. If you have something important to say, PM or email will help me to see it sooner. Concerning bugs, please PM or email me a report (others will thank you for improving the framework) with every possible detail.

Concerning issues with understanding and using framework functions, please make use of every resource you have available to you. If you have a technical question about a more obscure function, feel free to look at the source code and experiment with it. If you really cannot figure something out, PM or email me with the information needed to help you.

Your issues, bugs, and feedback are important to me. This framework is important to me, and I am not going to 'get bored' or 'have real life issues' a month after release, leaving you with bugs. I have invested a lot of time into this framework, and I will continue to do so.

Editor Limitations
The framework can be the only resource used to create your mission, or you may use it in conjunction with the editor and your own scripts. However, you cannot use any framework function in an object's init field, a trigger's condition, etc, in the editor. You can still use framework functions in places in the editor that do not execute instantly upon mission start, such as a trigger's activation field.

I have no plans to change this; it seems like a significant problem, but it is in fact advantageous once you learn how to create and organize your mission using external scripts. Your mission will be better organized and easier to change and debug with all of its code and function calls in a few SQF files. There is nothing that can be done in the editor that cannot be done with scripting. There is a lot that can be done with scripting that cannot be done in the editor.

You might think that the editor is preferable to my complex framework. I can say with 100% confidence that my framework is quicker to use, more reusable, easier to test and debug, more effective, and more powerful than the editor. You will achieve better missions more quickly once you learn to use the framework.

What the Framework is Not
First, the framework is not a magic black box that generates lots of features for you with a few inputs. This is not a system of mission templates that lets you create a 2-hour combined arms mission in 5 minutes. This is not a random mission generator, it is not a resource for players. It is a tool for mission makers.

Second, the framework does not implement abstract systems. This means things that do not achieve a direct effect in the game world or perform a concrete operation. I will never add a wounding system, weapon resting, team killing protection, points and scoring, respawn, or anything else that is superfluous to the mission itself.

Third, the framework does not control the mission, your implementation does. The framework does not run any functions unless you call something (most functions also call other framework functions). There are no hidden functions observing the mission and guessing what you want next. Almost every action must be done by you manually, and others are optional.

Finally, the framework is not a collection or compilation of various people's work. Everything in the framework is designed and coded by me without using any external libraries and other people's code (except for a few BIS functions for GUI stuff). I must be able to guarantee the quality and functionality of every line of code (over 11000 lines) if I claim to be the author of the framework. I have purposefully reinvented the wheel numerous times to allow this framework to provide the best experience possible.

In addition to the terms of the Legal.txt file (please read), the framework is also released under the Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International (CC BY-NC-ND 4.0) license.

You might also not be very impressed yet, but I assure you that you will be. I have spent well over 1000 hours creating this framework. Believe me when I say that this framework is worth your time.





- New Function: Zen_ArrayTranspose
- New Function: Zen_CreateAction
- New Function: Zen_DeleteAction
- New Function: Zen_GetActionDataGlobal
- New Function: Zen_GetObjectActions
- New Function: Zen_InvokeAction
- New Function: Zen_RemoveAction
- New Function: Zen_UpdateAction
- Fixed: Zen_OrderAircraftPatrol, Zen_OrderBoatPatrol, Zen_OrderHelicopterLand, Zen_OrderInfantryPatrol, Zen_OrderVehicleMove, and Zen_OrderVehiclePatrol failed to make the AI move in some cases
- Fixed: Zen_ArrayRemoveIndex did not exit on error
- Fixed: Zen_MoveInVehicle did not follow its fourth argument when the third argument was 'All'
- Fixed: Zen_UnlinkControl did not synch the change in MP
- Added: Framework macros ZEN_FMW_Code_GetRemoteVarArray, ZEN_FMW_Code_GetRemoteVarArrayT
- Added: Zen_RefreshDialog arguments for force and ignore refresh for controls
- Improved: Zen_RefreshDialog checks its arguments better
- Documentation: Added for Zen_ArrayTranspose, Zen_CreateAction, Zen_DeleteAction, Zen_GetActionDataGlobal, Zen_GetObjectActions, Zen_InvokeAction, Zen_RemoveAction, Zen_UpdateAction, ZEN_FMW_Code_GetRemoteVarArray, and ZEN_FMW_Code_GetRemoteVarArrayT
- Documentation: Updated for Zen_AddEject, Zen_AddFastRope, Zen_AddFireSupportAction, Zen_AddGiveMagazine, Zen_AddLoadoutDialog, Zen_AddRepackMagazines, Zen_AddSupportActionCustom, ZEN_FMW_Code_GetRemoteVar, Zen_RefreshDialog
- Documentation: Updated demonstrations and sample missions with action system
- Documentation: Updated Notepad++ SQF language and autocompletion file with ArmA 1.70 stable commands

- Fixed: Framework preprocessor library prevents repeated definition
- Fixed: Zen_FindCenterPosition caused an error if given an empty array
- Fixed: Zen_UpdateControl would not update Map control type
- Improved: Zen_RefreshDialog accuracy of detected changes
- Improved: Zen_RefreshDialog causes less flickering
- Improved: Zen_RefreshDialog restores the currently selected list item
- Improved: Zen_SpawnVehicleCrew uses the crew classname defined by the vehicle's config if possible
- Added: Zen_CreateControl properties Event, MapPosition, MapZoom, and Transparency
- Added: Zen_RefreshDialog parameter for control change time
- Added: Zen_CreateControl type StructuredText
- Added: Zen_InvokeDialog parameter to prevent Esc key exits
- Documentation: Improved Zen_SpawnInfantry
- Documentation: Updated for Zen_InvokeDialog, Zen_RefreshDialog
- Documentation: Updated Notepad++ SQF language and autocompletion file with ArmA 1.68 stable commands


Quelle: Bi-Foren
Download starten
Grösse 4,6 MB
Downloads 2238
Datum 24.05.2017
Kommentare 0
Download empfehlen
Wertung ø 3,00
1 Stimme(n)

  Seitenanfang nach oben


Kommentare sind nur registrierten Benutzern gestattet. Bitte loggen Sie sich ein!

Noch nicht angemeldet? Klicken Sie bitte hier!

Login speichern
Aktuelle News, Mods, Addons und Missionen für ArmA3
Seite in 0.03658 Sekunden generiert

Diese Website wurde mit PHPKIT WCMS erstellt
PHPKIT ist eine eingetragene Marke der mxbyte GbR © 2002-2012