The Editor: Scenario Designers' Wishlist

[bcgames]

ORIGINAL: Red Lancer

So what.....well there appears to be 3 options.
1. Do nothing, embrace anarchy and hope for the best.
2. The community implements its own configuration control of the core data - but this will require some element of production team buy in as future patches might undo this.
3. A change in code as to how core data is handled.

What do others think?

I am for any option that maximizes production of scenarios and mods. The enemy to this goal is player frustration caused by data conflicts with scenarios and/or mods created by third-parties, and/or game patches released by Matrix. Cuz this is a wishlist, I wish for Option #3...with a slight change in wording.

Don't change at all how the code current handles core data...leave it as is. Provide the scenario designer/modder the capability to block core data from loading. This should be a simple radio button. Under the hood, the code takes the data file names for that scenario and loads them instead. As such, nothing happens to any Matrix-created scenarios or any Core Data scenarios developed using the criteria you suggest in your post/Option #2.

Now...If wishes were horses then beggars would ride. So off the wish list and on to the problems of right now. I think your "core data" language plus el hefe's description of a "mod" provide a good framework for the WitE community to understand what they are getting from a third-party--or designing--is it a Core Data Scenario or is it a Mod? A Core Data Scenario is locked-and-loaded-ready-to-play. A Mod requires the use of the Generic Mod Enabler as Iron Duke suggests or manual file swapping.

[bcgames]

ORIGINAL: shane_056

What I am getting at here, is that to do this we the modelers will not be satisfied with doing it in the sceanario and will want to change ground elements and toe's just for starters which currently can only be done in the core files, so unless the game is setup with separate user core files, so you have a sequence of first opening a scenario with the core files loaded in overiding the scenario data files, then lastly the user files are loaded in overing scenario and core data, that way the user gets what he wants and the core files remain unchanged. I want total control and flexibility in doing this with no hard coding freezing or limitations. Remember in this game we are the supreme warlords.

after a year or so the historical games will be worn out, and then the gamers will want something else, with the what if's being one of them..

I like this wish too.

[bcgames]

Add German Infantry and Panzer Kampfgruppe for the period 1941-45 to the generic TOE(OB).

[bcgames]

Add to the generic _ob file German security regiments, landesshutz battalions, SS panzergrenadier battalions, and korpsabteilung.

Add to the generic _ob file Soviet antiaircraft divisions, separate tank brigades, Guards tank brigades, Guards motorized brigades, Guards heavy gun regiments, Guards heavy antitank regiments, security battalions, and antitank rifle battalions.

[bcgames]

Add ability to assign hex ownership in small scenarios by either clicking on the appropriate hexes or by providing a capability to draw a "front line".

[bcgames]

Add capability to "zero out"--with one tick box--all impacts of the strategic game on short, isolated area scenarios. No production, no replacements.

[TAIL GUNNER]

ORIGINAL: bcgames

Add capability to "zero out"--with one tick box--all impacts of the strategic game on short, isolated area scenarios. No production, no replacements.

Like that suggestion..

Would also like to see the ability to "zero out" the Units tab for new scenario creation.

[bcgames]

ORIGINAL: bcgames

Add ability to assign hex ownership in small scenarios by either clicking on the appropriate hexes or by providing a capability to draw a "front line".

Done. See Editor Hotkeys post on this thread here.

What else do you wish to see?

[Captain B]

Hey guys,

A couple of suggestions for the editor.

1. Early on I asked about having the ability to change the morale and experience levels in Air Groups. You can change them, but they go right back to the default when you save the file. I would like to see that function fixed in the editor.

2. Also, (other than by using the CSV's) a way to change all of a Units "elements" to the same "experience" number and maybe even the number damaged other than one element at a time. In other words, if I want to drop a German's division for a division that has each of its elements experience at "80" to "70" I have to do each element one at a time. Frustrating. Of course, I have started using the CSV's much more regularly for unit editing...but the column headings are not always intuitive, that would help.

3. How about a listing of what each database contains and what the range of numbers mean. For example, If I look at the Aircraft Database, I see an Armor number of "1" for the Bf 109K-4. What is the acceptable range? 1-10, 1-100? Is one better or is 100 better? Similarly, the reliability is "10". does that mean 10% chance of flying or a 90% chance of flying? Same thing for maneuver...is 40 better than 50 or is 40 better than 30?

4. An editor manual explaining all of this [:)]

5. I'll add more "nice to haves" to this list later. Thanks.

[antwniago]

Could we see an increase in the size of the AOG database - currently it is only 475 rows with 60+ being free but scattered in ones and twos between all existing entries, a block of 50-100 spare at the end would be helpful to save scattering new entries.

[Denniss]

please post this in the WitE2 section