Scenarios and ini files

[DWReese]

Hi gang,

I purchase every set of scenarios that CMANO puts out, even though I rarely ever get around to actually playing them. From what I can tell (remember), in the beginning, most scenarios rarely had any ini files associated with them. I simply loaded the scenario and started playing the game. As time passed, I realize that scenarios needed to be updated, so I "figured" that that was the reason that ini files were created. It was just a means of updating the scenario.

I purchased Sands and Silent Service when they came out and just started messing around with them. Even though I purchased them on Day 1, I noticed that they already had ini files for almost every scenario ready to be loaded. Is this the new norm? If so, then I suppose that I should ALWAYS check to see if the scenario has an ini file available before starting the scenario.

Are ini files the exception or the rule now? If they are the rule, I have never seen any new scenarios come out with a message that instructs the game player to "make sure that you check to see if an ini file is available before playing." Perhaps it's there and I simply overlook it because I have been playing the game for so long.

It's no big deal, but I just wanted to hear some feedback from others about when, and how often, everyone checks for ini file availability.

Thanks for your time.

Doug

[thewood1]

As the manual states, the ini files are there because the author changed/removed/added something on a unit like weapon, sensor, records, etc. The ini file is there so that if the scenario is updated, the ini file can be imported to bring the changes back into the scenario.

The original scenarios didn't do much fiddling around with units. But if you check the community scenarios, I think they all have ini files. I think its good sense to make an ini file, even if don't think it needs it. Its a little future proofing.

[DWReese]

Kevin,

Thanks for your response.

As you mentioned, the ini is there for CHANGES, etc. What is throwing me off is the scenario is being released (FOR THE VERY FIRST TIME) with ini files already in existence. I don't ever recall that happening before.

I do know what the ini file does. I'm just asking if the inclusion of an ini file for a BRAND NEW scenario is now the new norm. If so, then that is a departure from the past.

I, too, think that the inclusion of ini files is a great idea. before this, however, I just never thought to immediately check for any of them right out of the gate.

Thanks again for your informative response.

Doug

[thewood1]

Its changes to the units, not the scenario. I don't think know what it does. Its you change any standard unit. They are called delta template files. Page 84 in the manual...

"Delta Template: exports the delta (difference) between platform
configurations in the scenario and those in the database. The Delta
Template functionality is most commonly used to export aviation
magazine changes or additions. But the generated file will also list
platforms that have new and deleted weapons, weapon quantity
changes, added/removed mounts and magazines, added and
removed sensors, and added and removed communication gear
and weapon datalinks. The Delta Template functionality will not
export damage or changes in fuel levels."

From page 130...

"When making changes, the important thing to remember is that any
“full” scenario rebuild will delete your edits. To retain them you’ll need
to add changes to a scenario configuration file. You can do this by
generating a so-called “delta file” which shows the changes from the
“stock” configurations, and then applying them to the configuration
file. Specific instructions on how this works can be found in sections
7.1.6- 7.1.9. Keep in mind that our DB editors always reserve the right
to change record numbers so it is best to keep up with changes."

btw, scenarios were being released with ini files almost from day 1 of release. Like I already said, the community files almost all have them.

[DWReese]

Thanks

[rmunie0613]

Yes the ini file is to hold onto changes made in a unit, not necessarily in a scenario per se.
I am in various stages of completion of 4 scenarios...all 4 will have ini files on release because all have had unit alterations with the addition of HVP weapons to a class of warship that in reality does not have that. The ini file addition to the scenario simply makes sure that each time someone plays it, when they load the scenario, their 127mm mounts will be loaded with the HVP rounds.

[$trummer]

What does the player of an older scenario do in order to "activate" the .ini file to bring the mission up to date? Please excuse my very basic question.

[thewood1]

I don't mind answering the question, but its right in the manual. I think there is a whole section on it. You rebuild it in the editor. An ini file lets you do a deep rebuild that completely updates all units to the newest db without changing anything in the ini file

[$trummer]

Thanks for the response and apologies if I should have seen this in the manual but I am probably not the only person here who pays less attention to the scenario editor portion of the manual than the gameplay portion because my interest is only in playing the game rather than designing scenarios, for the moment anyway.

[thewood1]

The post just above yours explained what ini files are and the rebuild function was mentioned there. Just using a simple search in the manual would have probably gotten the answer. And my point is, there are tons of resources available to learn the game. And don't worry, you're obviously not the only person to not read the manual. If you are not reading anything past simple gameplay in the manual, your missing out on a lot of explanations on how things work. And you don't have to read the manual word-for-word. The search function in most PDF viewers works really well. Even the quirky search function in the forum can be a wealth of info.

Don't take this post too personally, but there has been an increase in people not looking in the manual, not looking at stickied threads on how to ask for help, not looking in the game itself, not doing the tutorials, or just plain not using the resources available to them to learn the game.

This is not a simple game. Its very complicated and takes a little effort to learn. The are a few people that just don't seem to want to do any of it themselves and just keep bringing issues up that only reflect on how little effort they have put into learning the game. They declare bugs or how something is not right when its that they never bothered to read a manual or do a tutorial. It wastes the devs time tracking down issues like that and frustrates other people on the forum. My personal philosophy is to help people that will at least make a minimal effort to help themselves.

[BDukes]

ORIGINAL: thewood1

The post just above yours explained what ini files are and the rebuild function was mentioned there. Just using a simple search in the manual would have probably gotten the answer. And my point is, there are tons of resources available to learn the game. And don't worry, you're obviously not the only person to not read the manual. If you are not reading anything past simple gameplay in the manual, your missing out on a lot of explanations on how things work. And you don't have to read the manual word-for-word. The search function in most PDF viewers works really well. Even the quirky search function in the forum can be a wealth of info.

Don't take this post too personally, but there has been an increase in people not looking in the manual, not looking at stickied threads on how to ask for help, not looking in the game itself, not doing the tutorials, or just plain not using the resources available to them to learn the game.

This is not a simple game. Its very complicated and takes a little effort to learn. The are a few people that just don't seem to want to do any of it themselves and just keep bringing issues up that only reflect on how little effort they have put into learning the game. They declare bugs or how something is not right when its that they never bothered to read a manual or do a tutorial. It wastes the devs time tracking down issues like that and frustrates other people on the forum. My personal philosophy is to help people that will at least make a minimal effort to help themselves.

He already say he miss in manual so probably know. No need for three paragraph criticize. Criticizing for jaywalk no good for community even if it make you feel smart.

Thanks

[thewood1]

So you stalking me again? You know, when I typed that, I was thinking to myself that is like bait for that crazy guy.

[stilesw]

Holy jumping trolls! In other words Batman:

Yours truly, Robin

[BDukes]

ORIGINAL: thewood1

So you stalking me again? You know, when I typed that, I was thinking to myself that is like bait for that crazy guy.

No not stalking. I told you when you are rude to user I will correct. Be nice or see me lots.

[thewood1]

Looks like stalking. You're being very rude. At least your posts are little more coherent. Smaller words help.

[BDukes]

ORIGINAL: stilesw

Holy jumping trolls! In other words Batman:

Yours truly, Robin

Wow is meme new thing in bully toadie handbook?

As I said to your boss. I will continue until he leave peoples alone. You and he jump on them too hard over stupid things.

Thank.

[BDukes]

ORIGINAL: thewood1

Looks like stalking. You're being very rude. At least your posts are little more coherent. Smaller words help.

You are 5 second in my day. But worth if good user left alone.

Thank

[thewood1]

Looks more than 5 seconds.

[BDukes]

ORIGINAL: thewood1

Looks more than 5 seconds.

I see you have received message so like Bush-- "mission accomplish!". Good time spent. Have nice week wood.

[thewood1]

OK, glad your leaving happy.