next »

[ferstaberinde]

Latest Release: v2-0-1 Released (Public Beta)

On behalf of the whole F2 team I'm pleased to announce our new release of the F2 Mission Development Framework. F2 is the successor to the popular BAS f mission development framework for ArmA (discussed in this thread). The new framework contains many of the features you know from BAS f, updated to work with ArmA 2, plus some new components which take advantage of the new game's special features.

For downloads and to find out more please see our online manual:

http://www.ferstaberinde.com/f2/en/ (English version*)

Huge thanks to all team members and contributors to F2 (and BAS f), as well as the testers from Shack Tactical.

* A Russian-language version of the manual will be available soon. We're looking for a German translator, please PM Fer if interested.

[bedges]

I think this is definitely worthy of a frontpage story, posting now. 

[Kremator]

Got really excited when I saw this.  However, Linky isn't working !

[bedges]

Links updated, I suspect Fer pasted directly from BIF... 

[Kremator]

Ahhhh got it now from the link on Armaholic.

Thanks

[ferstaberinde]

Thanks for posting, bedges

[xMobiusTyrx]

good work! Do you by any chance know how to script the AI creation via barracks to follow you?

[ferstaberinde]

Er, not sure what you mean.

[Chief]

Thanks Fer. Excellent resource. Using many of its features in my missions for the Phoenix Soldiers Tactical co-op gaming group.

[ferstaberinde]

New Release: v2-0-3

About the new release

From the ReadMe.txt file:

2-0-3 | 24 AUG 2009
Updated Kegetys Spectator Script component.

+++

New Release: v2-0-2

About the new release

From the ReadMe.txt file:

2-0-2 | 24 AUG 2009
Added Disable BIS Conversations component.
Replaced stringtable.csv with stringtable.xml.
Removed First Aid: Action pre-placed game logics from mission.sqm file (Preplaced Game Logics component).
Updated manual: Various changes (EN and RU versions).

About F2

The F2 Mission Development Framework (F2) is the successor to the popular BAS f mission development framework for ArmA (discussed in this thread). The new framework contains many of the features you know from BAS f, updated to work with ArmA 2, plus some new components which take advantage of the new game's special features.

For downloads and to find out more please see our online manual:

http://www.ferstaberinde.com/f2/en/ (English version*)
http://www.ferstaberinde.com/f2/ru/ (Russian version)

Huge thanks to all team members and contributors to F2 (and BAS f), as well as the testers from Shack Tactical.

* We're looking for a German translator, please PM Fer if interested.

[tcp]

This is really great. Better than using other people's map to try to learn what you are supposed to script like.

I just got started with this, but noticed a couple things. http://www.ferstaberinde.com/f2/EN URL doesn't work with capital letters, and that's from the Readme file.

Also, it says to use underscores in our folder name but to match briefingName EXACTLY. Why can't we use regular spaces in briefingName to make it look nice on the mission selection screen?

EDIT: So, this doesn't include options for keeping gear assignments after respawn?

[ferstaberinde]

I just got started with this, but noticed a couple things. http://www.ferstaberinde.com/f2/EN URL doesn't work with capital letters, and that's from the Readme file.

Oooh. Thanks for the heads-up on that. Damn you, UNIX server! Put in some redirects now.

Also, it says to use underscores in our folder name but to match briefingName EXACTLY. Why can't we use regular spaces in briefingName to make it look nice on the mission selection screen?

Actually, you probably can. F2 is based on BAS f, which was written for ArmA. There used to be some strange issues with spaces and special characters in mission names, which is why the instructions here are so conservative.

EDIT: So, this doesn't include options for keeping gear assignments after respawn?

Someone just asked another respawn-focused question over in the BI forums, and here's what I responded with (since it's relevant too):

... One of the challenges for me is that I never play missions with respawn, so it's a whole area of the game that I know little about. From a scripting perspective respawn brings its own challenges. If you yourself have some experience/skills in this area, perhaps you (or someone else reading this post) can consider submitting such a component for inclusion?

Hope that helps

[Worldeater]

Is there a reason why this framework does not use proper tags for its globals? That's the second framework I see today that does not "play nice"...

[ferstaberinde]

Is there a reason why this framework does not use proper tags for its globals? That's the second framework I see today that does not "play nice"...

Is there an agreed convention that you can point to?

[Pirin]

I imagine something as simple as using an F2V_ prefix to global variables might be good?

Read more here: http://www.ofpec.com/tags/