Keeping track of Scenario Design

Matrix Games Forums

Forums Register Login Photo Gallery Member List Search Calendars FAQ

My Profile Inbox Address Book My Subscription My Forums Log Out

Keeping track of Scenario Design

View related threads: (in this forum | in all forums)

Logged in as: Guest

Users viewing this topic: none

Printable Version

All Forums >> [New Releases from Matrix Games] >> Command: Modern Operations series >> Mods and Scenarios >> Keeping track of Scenario Design

Page: [1]

Message

<< Older Topic Newer Topic >>

Keeping track of Scenario Design - 11/2/2013 6:11:09 PM

ArmyVet2004

Posts: 52
Joined: 10/2/2013
Status: offline

Fellow gamers,

I have a question

How do you guys keep track of the events while in the design of a certain scenario?
And, how do you save all the different events?

Just trying to get some ideas here. I'm getting pretty confused and start to lose track of my design. Tried different methods but just seems to not work out for me.

Thanks in advance,

Orlando

Post #: 1

RE: Keeping track of Scenario Design - 11/2/2013 6:36:15 PM

El Savior

Posts: 337
Joined: 7/31/2003
From: Finland
Status: offline

I'm still designing my style, but I use this:

Name:

Side-Event name-number

Example:

RUSSIAN-Kilo teleport #1

If for AI, I use RUSSIAN Event #1 - so name will not tell what it does. Events show can be disabled for view, but I find this useful.

_____________________________

El Savior

(in reply to ArmyVet2004)

Post #: 2

RE: Keeping track of Scenario Design - 11/2/2013 6:38:44 PM

ArmyVet2004

Posts: 52
Joined: 10/2/2013
Status: offline

Thanks El Savior,

Trying to get the same thing in at not letting anyone what the event will be.

Regards,

Orlando

(in reply to El Savior)

Post #: 3

RE: Keeping track of Scenario Design - 11/2/2013 6:53:19 PM

Meroka37

Posts: 770
Joined: 7/31/2009
Status: offline

I use as prefix M_ E_ T_ A_ ( for Mission, Event, Trigger and Action�so I can even use the same name for all of them if they are related to each other), as name I use always a description and� I have an Excel file with a list of all META I'm using in a scenario design.

�

So if I want to create an event which activates an air mission attack on a convoy.

�

I create mission M_Attack_Convoy� (with status inactive), then I create an Event named E_Attack_Convoy, the trigger (of any kind) will be called T_Attack_Convoy and the Action which change M_Attack_Convoy status to active will be named A_Attack_Convoy; this I way I have track of even dozens of events.

< Message edited by Meroka37 -- 11/2/2013 9:28:57 PM >

_____________________________

'Better honor without ships, than ships without honor"

(in reply to ArmyVet2004)

Post #: 4

RE: Keeping track of Scenario Design - 11/2/2013 8:13:51 PM

ArmyVet2004

Posts: 52
Joined: 10/2/2013
Status: offline

Very helpful Meroka37......This is really helping me out

Thanks

(in reply to Meroka37)

Post #: 5

RE: Keeping track of Scenario Design - 11/3/2013 2:38:21 AM

Temple

Posts: 529
Joined: 7/31/2002
Status: offline

I subscribe to the belief that a player will turn off the event message log and pop-ups so as not to spoil the surprises if I be sure to mention it in a readme.txt or side description. So I use very descriptive trigger, action and event titles. After all, if they want to figure out what's going out behind the curtain they can just load up the scenario in the editor.

(in reply to ArmyVet2004)

Post #: 6

RE: Keeping track of Scenario Design - 11/3/2013 11:50:15 AM

brassem