SH3Cmdr Pre-release 2.6 for events testers

[JScones]

As I've made some changes to the Randomised events feature plus added a new Static settings feature (following a similar concept), I would like to offer a pre-release of the next SH3Cmdr to users who understand and are indeed using the Randomised events feature (may just be Hemisent and Jason, but I don't know).

Anyway, if you are one of these people and are interested in checking out the latest enhancements, pls PM me. I'll be seeking feedback/comments/suggestions from you as part of the testing.

FYI after Hemisent finishes the sabotage/malfunctions settings I'll build those into SH3Cmdr. Then, depending on whether I have the time/energy to add a few other features, the final SH3Cmdr release will be ready to go. I think then I will have achieved in providing users with total control over how they play *their* game.

[K_Sea6]

I have been following the Randomised Events since it's conception
I use it and love it. It just keeps getting better and better,
so keep it coming, I have added my own flavor to the ship damage of the chaos mod. This makes game play more unpredictable and a little
more realistic. this is the ultimate mod for me

Thanks, Kerry

[gouldjg]

Have sent you a PM

[JScones]

Glad you did. :up:

[irish1958]

Have you added the Choas idea to the new CMDR?
irish1958

[JScones]

Have you added the Choas idea to the new CMDR?
irish1958
No. I want to a) wait until it's finished and b) guage player reaction.

It will determine how, or if, I include the mod as standard in SH3Cmdr.

Either way, I'll be using it.

[gouldjg]

Hi Jscones

I will post you tommorow concerning the file capability. Have just been a bit tied up lately and had to do a reinstall.

Gouldjg

[HEMISENT]

Jscones
Just sent you the completed malfunctions files last night for your review. Did you receive them? I may play around with the settings or combinations a bit but for the most part it's a done deal. All files were using testing only percentages-I'm working on the odds right now.
The files did not include TypeII's & Type XXI's as these will be done later as an add-on.
Also, borrowing from Gouldjg's chaos theme I'm thinking of combining one or two seperate files which will incorporate a host of malfunctions with real long odds-(sort of like everything that could break just broke)What do you think?

Do you want the Sabotage files also? These are date specific as you know.
Please send me the updated Commander test version.

Yahoo!- We're getting close.

[HEMISENT]

Have you added the Choas idea to the new CMDR?
irish1958
No. I want to a) wait until it's finished and b) guage player reaction.

It will determine how, or if, I include the mod as standard in SH3Cmdr.

Either way, I'll be using it.

Just throwing my two cents in. I tried out the beta chaos settings and it seemed to work great with NYGM/HT/Unified-I was impressed. I have not gotten back to it since its final release but as soon as my current project is wrapped up I will get the latest version from Jason's blog.

I think it's going to be one of those "must have" mods for me. Gouldjg went above and beyond on this one.

[HEMISENT]

Jscones
Commander 2.6 up and running-thanks!

2 questions;

1. dates/random-
From randomized events instructions:
regarding dates.
;Copy, paste and rename this file to "Randomised events_19xx.cfg" to allow settings to be war year specific. This file can be deleted if feature unwanted.

Does this mean that I set all the percentages on all the files (using choosefrom=)currently in "Randomized Events" to what I want for a given year then copy/rename to "Randomised events_19xx.cfg".

Then do the same thing all over again with different choosefrom=settings and rename to the next year and so on and so on?
I will eventually end up with 7 "Randomised Events_19xx.cfg" folders?

2 static folder-
Isn't this doing the same job as the original DATE folder. I use the DATE folder now for a certain skins to appear at a certain time and also for a later war Sim.cfg to come into play. Could you elaborate on the difference?

[JScones]

1. dates/random-
From randomized events instructions:
regarding dates.
;Copy, paste and rename this file to "Randomised events_19xx.cfg" to allow settings to be war year specific. This file can be deleted if feature unwanted.

Does this mean that I set all the percentages on all the files (using choosefrom=)currently in "Randomized Events" to what I want for a given year then copy/rename to "Randomised events_19xx.cfg".

Then do the same thing all over again with different choosefrom=settings and rename to the next year and so on and so on?
I will eventually end up with 7 "Randomised Events_19xx.cfg" folders?
Yup. For example, create your "base" Randomised events.cfg file. Copy that and paste it seven times. Rename each one Randomised events_1939.cfg, Randomised events_1940.cfg and so on.

Open up Randomised events_1939.cfg and then tinker with whatever aspect you need to make malfunctions real to 1939. You may want to just change the ChooseFrom percentages, you may also want to adjust the range or content of some of the values you have added. You may want to remove some pieces of equipment or add some new ones.

Repeat for each subsequent file.

2 static folder-
Isn't this doing the same job as the original DATE folder. I use the DATE folder now for a certain skins to appear at a certain time and also for a later war Sim.cfg to come into play. Could you elaborate on the difference?
Yes and No. If you want to include graphic files such as ship/u-boat skins and the like, you need to use the Date folders. If you want to include settings, yes you can include files in the Date folders, but you run the risk of compatibility problems. For example, you may only want to change one value in SIM.CFG, but by including a full version of the file, all other settings in the SH3 version of SIM.CFG will be overwritten with yours. This may create conflicts or crashes.

The Static settings feature works around this problem by allowing you to set *specific* values within files. Then, only those parts of the files will be adjusted. So you don't need a whole Zones.cfg file just to adjust the HitPoints of the Type XXI's rudder (for example). It reduces conflicts to practically zero plus giving you the ability to "force" your preferred settings into SH3 regardless of what mods you have installed (albeit accepting the risk that your changes may not suit some mods out there).

Of course though, if you require changes to occur on a specific date, such as 6/6/1944, then you'll need to continue using the Date folders, at least until I build a user friendly way of controlling date based settings via the Static settings and Randomised events files. The current year adjust just provides a nice compromise.

[HEMISENT]

Great! Thanks for the fast response-I'm playing with the percentages right now.

[JScones]

Actually Hemisent, when you've finished your seven files and are happy with them, can you pls email them to me? I'll review and provide feedback like you asked. The advantage of doing it this way is that I can look at exactly what you are playing with.

What you've sent me so far looks 100% OK though.

[Vermin]

Sorry - I 've been using various SH3Cmdr for ever but I did not notice the random events thingy... (I'm using v2.5 ATM).

Can you please point me to a hread on this so I know what you're talking about (please) :D

I know - I'm not vey observant...

[HEMISENT]

Actually Hemisent, when you've finished your seven files and are happy with them, can you pls email them to me? I'll review and provide feedback like you asked. The advantage of doing it this way is that I can look at exactly what you are playing with.

What you've sent me so far looks 100% OK though.

Still tweaking here and there. Should be in you hands before the weekend.
Any idea how I can get the Sabotage files to be year/month specific?
Now that the Randomized Events.CFG is in place the Random folder structure while working perfectly is a bit outdated and bulky.

[JScones]

Randomised events.cfg is only year specific at the moment. When I port it all across to a specific malfunctions file I hope to add month support as well.

Hehe. Although the way you are going I may not need to create a unique malfunctions function!

I'll think of user friendly ways to incorporate support for month changes.

[U-Schultz]

Any estimated public release date?

This randomization feature is really huge in my book. I use it with version 2.5. I see alot of possibilities and uses with it. :yep:

[Spaxspore]

Any estimated public release date?

This randomization feature is really huge in my book. I use it with version 2.5. I see alot of possibilities and uses with it. :yep:


Ive been out of a loop for a while, what does the randomization feature do?

[HEMISENT]

Jscones.
A couple more questions for you.

1. For testing purposes only- My normal routine is to launch SH3 thru Commander, wait for it to load, then wait for SH3 game to load, once game has loaded I then can Alt/Tab to minimize and open mini tweaker to determine which file loaded. It takes awhile each time I go thru the whole process. Is there any way to activate Commander, let it go thru the file selection process and check which randomized files it has selected without waiting for the game itself to load each time? In other words cheat the system and avoid loading the game itself.

2.Right now in Commander 2.6 we have DATE folders, Random Folders, Randomized CFG, Static settings.CFG.

What is the order of precedence? I think the in game info stated Static was the last in the chain.

3.(sorry just came up with an additional one)Malfunctions now has crash depths modified and they are in year specific Randomized Events.CFG as instructed.
malfunctions example:
[0_data\Submarine\NSS_Uboat7b\NSS_Uboat7b.CFG]
FileType=T
ChooseFrom=50
RndMidPat=1

3_Properties|CrashDepth=95 ;[70]
4_Properties|CrashDepth=137
5_Properties|CrashDepth=158
6_Properties|CrashDepth=179
7_Properties|CrashDepth=250

When Commander does not choose a loaded file and issues the default setting can I put this into the Static .CFG to use as my new default?
I do not want my crash depth to be an automatic 70m.

[0_data\Submarine\NSS_Uboat7b\NSS_Uboat7b.CFG]
Properties|CrashDepth=I|50|90|Y ;Randomises level off depth on crash dive.

[JScones]

1. For testing purposes only- My normal routine is to launch SH3 thru Commander, wait for it to load, then wait for SH3 game to load, once game has loaded I then can Alt/Tab to minimize and open mini tweaker to determine which file loaded. It takes awhile each time I go thru the whole process. Is there any way to activate Commander, let it go thru the file selection process and check which randomized files it has selected without waiting for the game itself to load each time? In other words cheat the system and avoid loading the game itself.
:hmm: I suppose I can add a "debug" switch. I'll think about it.

2.Right now in Commander 2.6 we have DATE folders, Random Folders, Randomized CFG, Static settings.CFG.

What is the order of precedence? I think the in game info stated Static was the last in the chain.
When you press "Launch SH3!", SH3Cmdr performs the following steps in this order (for the sake of brevity, let's just assume that an existing career is being launched):

1. Removes previously installed files
2. Reads SH3Cmdr settings/options
3. Determines whether career will be retired (if option selected)
4. Determines next patrol start date
5. Copies into SH3 any Flotilla folder files
6. Copies into SH3 any U-boat folder files
7. Copies into SH3 any Date folder files
8. Copies into SH3 any Random folder files
9. Determines whether crewman will be retired (if option selected)
10. Writes Text Settings to **_menu.txt
11. Writes Menu variable text to **_menu.txt
12. Writes Days in Base value to Basic.cfg
13. Writes Crew fatigue model to Basic.cfg (if option selected)
14. Writes correct U-boat availability dates to Basic.cfg (if option selected)
15. Writes deck gun settings to GUNS_SUB.sim (if option selected)
16. Writes water density setting to scene.dat (if option selected)
17. Writes wave height setting to scene.dat (if option selected)
18. Writes random tonnage variations
19. Writes random crush depth
20. Writes random events
21. Writes static settings
22. Randomises Gramaphone tracks (if option selected)
23. Launches SH3!!!!

3.(sorry just came up with an additional one)Malfunctions now has crash depths modified and they are in year specific Randomized Events.CFG as instructed.
malfunctions example:
[0_data\Submarine\NSS_Uboat7b\NSS_Uboat7b.CFG]
FileType=T
ChooseFrom=50
RndMidPat=1

3_Properties|CrashDepth=95 ;[70]
4_Properties|CrashDepth=137
5_Properties|CrashDepth=158
6_Properties|CrashDepth=179
7_Properties|CrashDepth=250

When Commander does not choose a loaded file and issues the default setting can I put this into the Static .CFG to use as my new default?
I do not want my crash depth to be an automatic 70m.

[0_data\Submarine\NSS_Uboat7b\NSS_Uboat7b.CFG]
Properties|CrashDepth=I|50|90|Y ;Randomises level off depth on crash dive.
No. What you put in Static settings.cfg will always overwrite any previous changes made by SH3Cmdr during the launch process. BUT with just a smidge of lateral thinking, you can get the effect you want by adding the following to Randomised events, in this order:

;THIS RANDOMISATION HAPPENS FIRST
[0_data\Submarine\NSS_Uboat7b\NSS_Uboat7b.CFG]
Properties|CrashDepth=I|50|90|Y ;Randomises level off depth on crash dive.

;THIS RANDOMISATION HAPPENS SECOND. IF A VALUE IS CHOSEN, IT WILL OVERWRITE THE ONE CALCULATED ABOVE. IF NO VALUE IS CHOSEN, THE ONE CALCULATED ABOVE WILL BE MAINTAINED
[1_data\Submarine\NSS_Uboat7b\NSS_Uboat7b.CFG]
FileType=T
ChooseFrom=50
RndMidPat=1

3_Properties|CrashDepth=95 ;[70]
4_Properties|CrashDepth=137
5_Properties|CrashDepth=158
6_Properties|CrashDepth=179
7_Properties|CrashDepth=250

Note that Static settings is set up only to accept static settings. Setting a value in Static settings.cfg to something like "I|50|90|Y" will mean that the whole string of characters will be written into the game. In other words, your crash depth will literally become "I|50|90|Y"

[HEMISENT]

Thank You
That helps a great deal.
BTW. everything is pretty much wrapped with malfunctions files + since I had the format already worked out I did the XXI boat last night-testing now, should have all files in your hands by friday.

PS. a "debug" switch would certainly speed things up a bit.

[JScones]

FYI just figuring out how best to handle months within each year. I'm thinking the best way is to add a new (optional) "ApplyToPeriod" setting which will have the value "YYYYMMDD|YYYYMMDD"

This means that you could have:
[0_data\Cfg\SIM.CFG]
ApplyToPeriod=19400401|19400901
AI Detection|Lost contact time=I|15|25|Y

[1_data\Cfg\SIM.CFG]
ApplyToPeriod=19400902|19401125
AI Detection|Lost contact time=I|15|45|Y
This will randomise the lost contact time between 15 and 25 seconds between 1 Apr 1940 and 1 Sep 1940 and will randomise the lost contact time between 15 and 45 seconds between 2 Sep 1940 and 25 Nov 1940.

Now, if for example the first block did not include the "ApplyToPeriod" setting, then the 15 to 25 variation will occur for all the whole year EXCEPT between 2 Sep 1940 and 25 Nov 1940. I hope this is clear - reply if not.

The disadvantage of this approach is that whole blocks which may differ only by "ChooseFrom" probability will need to be repeated. However, the advantage is that you have total flexibility and can apply any setting to any period within the year.

With this addition I was contemplating rolling the yearly files (_19**) back into one main file (as it used to be), but I think doing so will become too cumbersome and unwieldly. Even though it goes against data normalisation, I think having separate yearly files are easier to manage. Although I would be keen to hear thoughts on this assumption from people using the feature. One thing I am *really* seriously considering is making this change for "Static settings" as the inclusions will generally be much less and thus easier to manage. Again, thoughts?

[lurker_hlb3]

FYI just figuring out how best to handle months within each year. I'm thinking the best way is to add a new (optional) "ApplyToPeriod" setting which will have the value "YYYYMMDD|YYYYMMDD"

This means that you could have:
[0_data\Cfg\SIM.CFG]
ApplyToPeriod=19400401|19400901
AI Detection|Lost contact time=I|15|25|Y

[1_data\Cfg\SIM.CFG]
ApplyToPeriod=19400902|19401125
AI Detection|Lost contact time=I|15|45|Y
This will randomise the lost contact time between 15 and 25 seconds between 1 Apr 1940 and 1 Sep 1940 and will randomise the lost contact time between 15 and 45 seconds between 2 Sep 1940 and 25 Nov 1940.

Now, if for example the first block did not include the "ApplyToPeriod" setting, then the 15 to 25 variation will occur for all the whole year EXCEPT between 2 Sep 1940 and 25 Nov 1940. I hope this is clear - reply if not.

The disadvantage of this approach is that whole blocks which may differ only by "ChooseFrom" probability will need to be repeated. However, the advantage is that you have total flexibility and can apply any setting to any period within the year.

With this addition I was contemplating rolling the yearly files (_19**) back into one main file (as it used to be), but I think doing so will become too cumbersome and unwieldly. Even though it goes against data normalisation, I think having separate yearly files are easier to manage. Although I would be keen to hear thoughts on this assumption from people using the feature. One thing I am *really* seriously considering is making this change for "Static settings" as the inclusions will generally be much less and thus easier to manage. Again, thoughts?


I think it's a good Idea. Keep the yearly files. Since I started testing 2.6 the yearly files have worked out well

[JScones]

Bugger it, you can have both options. :up:

Users will be able to, at their own discretion, either:

a) maintain separate Randomised events and/or Static settings files for each year of the war with ApplyToPeriod settings being added to each file as required, or
b) use one Randomised events and/or Static settings file and use ApplyToPeriod settings to cover any period of the entire war.

The choice will be yours! SH3Cmdr will just go with the flow.

***FYI all SH3Cmdr R2.6 testers will receive an email in the next 5 or 6 hours advising them of the updated version for testing.

[HEMISENT]

Jaesen,
So as I understand we could use the Randomized events.CFG with ApplyToPeriod= from beginning of the war, keep the same basic file but change the 0_data & ApplyToPeriod=xx progressing thru the war years? It is then possible to avoid the player manually changing the Randomized events.CFG year by year.

So does this mean that the below scenario would work for the randomized Sabotage files? Same file just changed the 0_data & the ApplyToPeriod= settings.

Sample VIIB
[0_data\Submarine\NSS_Uboat7b\NSS_Uboat7b.sim]
ApplyToPeriod=19440601|19440731
;Maximum speed both surfaced and submerged reduced, surface and submerged ranges reduced, increased dive time, increased turn radius.
;19440601 25%
FileType=B
ChooseFrom=44
RndMidPat=1

0_x03FC=11 ;Max deisel speed[17.2]
0_x0430=297 ; Rpm's[471]
1_x03FC=7
1_x0430=188

2_x0573=3.0 ;Max e motor speed [8.0]
2_x0595=107 ;Rpm's[290]

3_x03FC=7 ; Combination deisel/e motors
3_x0430=188
3_x0573=3.0 ;
3_x0595=107

4_x05BB=5200 ;Surface range decreased[6500]

5_x05E5=40 ;Battery range decreased[90]
6_x05E5=18 ;Battery range decreased

7_x0619=6750 ;Increased dive time[9000]

8_x0487=0.02 ;turn rate[0.05]

9_x0573=3.0 ;Combination e motors/battery range/dive time
9_x0595=107
9_x05E5=18
9_x0619=6750

10_x03FC=11 ;Combination max speed/surface range
10_x0430=297
10_x05BB=5200
;--------------------------------------------------------------------
[1_data\Submarine\NSS_Uboat7b\NSS_Uboat7b.sim]
ApplyToPeriod=19440801|19441231
;Maximum speed both surfaced and submerged reduced, surface and submerged ranges reduced, increased dive time, increased turn radius.
;19440801 30%
FileType=B
ChooseFrom=37
RndMidPat=1

0_x03FC=11 ;Max deisel speed[17.2]
0_x0430=297 ; Rpm's[471]
1_x03FC=7
1_x0430=188

2_x0573=3.0 ;Max e motor speed [8.0]
2_x0595=107 ;Rpm's[290]

3_x03FC=7 ; Combination deisel/e motors
3_x0430=188
3_x0573=3.0 ;
3_x0595=107

4_x05BB=5200 ;Surface range decreased[6500]

5_x05E5=40 ;Battery range decreased[90]
6_x05E5=18 ;Battery range decreased

7_x0619=6750 ;Increased dive time[9000]

8_x0487=0.02 ;turn rate[0.05]

9_x0573=3.0 ;Combination e motors/battery range/dive time
9_x0595=107
9_x05E5=18
9_x0619=6750

10_x03FC=11 ;Combination max speed/surface range
10_x0430=297
10_x05BB=5200
;--------------------------------------------------------------------
[2_data\Submarine\NSS_Uboat7b\NSS_Uboat7b.sim]
ApplyToPeriod=19450101|19450601
;Maximum speed both surfaced and submerged reduced, surface and submerged ranges reduced, increased dive time, increased turn radius.
;19450801 42%
FileType=B
ChooseFrom=26
RndMidPat=1

0_x03FC=11 ;Max deisel speed[17.2]
0_x0430=297 ; Rpm's[471]
1_x03FC=7
1_x0430=188

2_x0573=3.0 ;Max e motor speed [8.0]
2_x0595=107 ;Rpm's[290]

3_x03FC=7 ; Combination deisel/e motors
3_x0430=188
3_x0573=3.0 ;
3_x0595=107

4_x05BB=5200 ;Surface range decreased[6500]

5_x05E5=40 ;Battery range decreased[90]
6_x05E5=18 ;Battery range decreased

7_x0619=6750 ;Increased dive time[9000]

8_x0487=0.02 ;turn rate[0.05]

9_x0573=3.0 ;Combination e motors/battery range/dive time
9_x0595=107
9_x05E5=18
9_x0619=6750

10_x03FC=11 ;Combination max speed/surface range
10_x0430=297
10_x05BB=5200

[HEMISENT]

Second question
Does the;-----------------------------------------
need to seperate the individual files from one another
0_dataxxx
;-------------------------------------

1_dataxxx
;-------------------------------------

2_dataxxx
;-------------------------------------

etc.

[JScones]

Jaesen,
So as I understand we could use the Randomized events.CFG with ApplyToPeriod= from beginning of the war, keep the same basic file but change the 0_data & ApplyToPeriod=xx progressing thru the war years? It is then possible to avoid the player manually changing the Randomized events.CFG year by year.
Yes. I chose to give you both options in case rolling back into one file became too messy.

So does this mean that the below scenario would work for the randomized Sabotage files? Same file just changed the 0_data & the ApplyToPeriod= settings.

Sample VIIB
[0_data\Submarine\NSS_Uboat7b\NSS_Uboat7b.sim]
ApplyToPeriod=19440601|19440731
;--------------------------------------------------------------------
[1_data\Submarine\NSS_Uboat7b\NSS_Uboat7b.sim]
ApplyToPeriod=19440801|19441231
;--------------------------------------------------------------------
[2_data\Submarine\NSS_Uboat7b\NSS_Uboat7b.sim]
ApplyToPeriod=19450101|19450601
Yep. If the next patrol start date is say 12 Sep 1944, then ONLY [1_data\Submarine\NSS_Uboat7b\NSS_Uboat7b.sim] will be looked at.

BTW, you no longer need the "FileType" parameter - SH3Cmdr is now smarter and instinctively knows what type of file you are editing.

[JScones]

Second question
Does the;-----------------------------------------
need to seperate the individual files from one another
0_dataxxx
;-------------------------------------

1_dataxxx
;-------------------------------------

2_dataxxx
;-------------------------------------

etc.
No. I just use the line to make identifying each section easier. Just like I do in my code.

[Scorpius]

I sometimes wonder will we ever run out of things to mod on this game!

Oh and btw Jscones, did you get my pm?

[HEMISENT]

One other thing before I forget.

Please , please, please include the debug switch in the final release as we discussed earlier-makes repeated testing a whole lot less time consuming-perhaps by as much as 75%.

[JScones]

What output do you want to see from such a switch?

[HEMISENT]

What output do you want to see from such a switch?

If I could "Launch SH3" thru Commander, have Commander choose whichever files it wants but not actually start the game.

Once Commander goes thru the loading sequence I would like to be able to look in mini tweaker and see what it just loaded. When editing files for randomization all I do is "launch/load game/check setting" repeatedly to determine percentages. This switching function would save an enormous amount of time (not to mention wear and tear).

I can grovel if that would help.

[JScones]

Why don't you use the current /nolaunch switch? It's been in SH3Cmdr since R2.2.

Everything runs *except* SH3.

I like these easy fixes! ;)

[HEMISENT]

Why don't you use the current /nolaunch switch? It's been in SH3Cmdr since R2.2.

Everything runs *except* SH3.

I like these easy fixes! ;)

Okay..... At the risk of sounding stupider than I already am-the next question that comes to mind is......What no launch switch? This is the first I'm hearing about it and I've used Commander since the beginning.
I just opened up Commander while writing this to see if I missed something but ..... :doh:

[JScones]

If you don't already have a shortcut to SH3Cmdr on your desktop, create one (right-click on SH3Cmdr.exe then select Send To|Desktop (create shortcut)).

After you've created the shortcut on your desktop (or really anywhere you like), highlight it and select "Properties". In the Target box, add a space to the end of the entry and then append /nolaunch. You should end up with an entry that looks like:

"C:\<installpath>\SH3 Commander\SH3Cmdr.exe" /nolaunch

Press OK.

Use this shortcut when you don't want to run SH3.

[HEMISENT]

"C:\<installpath>\SH3 Commander\SH3Cmdr.exe" /nolaunch
Use this shortcut when you don't want to run SH3.

Thank You, Thank You,Thank You, Thank You!
Worked like a champ.
AAAARRRRRGGGGHHH!!!!!

Question-Did I miss this in the readme or where is this info displayed-I usually go thru all the instructions pretty completely even if they don't have pictures.

[JScones]

It was discussed on the forum around the time of release. It's the last listed feature in the HTML readme. And the steps to follow are essentially the same as those outlined under the first listed feature in the readme (the one referring to pointing SH3Cmdr to multiple installations of SH3).

[HEMISENT]

Jscones
All I can say is I guess I win the Cement Bicycle award.

Thanks again(maybe pictures would have helped)

[Selle]

It is possible a feature to intigrate into the newest SHIII_CMDR version?

I have this Idea:

Ever you sunk a ship and reportet this to the BdU, you get the sam answer.

It is possible to randomise the answer with dificult one´s in SHIII_CMDR?

An if this possible, I could write some answer´s from BdU and will sending this to you.

Sorry, my english isn´t the best... :oops:

greetings from germany

Selle

[Uber Gruber]

Its a good idea but I think it has been done already....can someone confirm ?

[Sailor Steve]

Yes, it's been done, but I don't remember which mod does it! I do get a variety of messages to my reports.

Sorry.

[JScones]

It is possible a feature to intigrate into the newest SHIII_CMDR version?

I have this Idea:

Ever you sunk a ship and reportet this to the BdU, you get the sam answer.

It is possible to randomise the answer with dificult one´s in SHIII_CMDR?

An if this possible, I could write some answer´s from BdU and will sending this to you.

Sorry, my english isn´t the best... :oops:

greetings from germany

Selle
gouldjg has done it already as part of the "randomised events" feature. There's a post around here with the settings he used, but prolly lost to the ages now with no easy way to find it...

With the randomised events feature (which is included as part of SH3Cmdr R2.5 and will be improved in R2.6) you can randomise *any* **_menu.txt setting, although due to SH3 limitations you'll get the same text label during each SH3 session. This is because SH3 loads and locks the key game files at startup.

[Georg_Unterberg]

Jscones,

there is something I have in mind where I could use the "ApplyToPeriod" feature - is it already implemented in your beta?

I'm quite unhappy with the way renown is handled to "buy" upgrades in GW. E.g. there is a simple FAT I torpedo, which costs 100 renown. If you want decent torpedos you can't "buy" anything else - I don't like this.

NYGM doesn't satisfy me either, because in general I like the idea of renown - you must be successful on patrol to get "privileges". In NYGM you can buy all stuff with time - too much time IMO.

OK, I want to to this: Only new technology should cost renown for some months - and if a commander wants to have this brand new upgrade, he must be "privileged" - in SH3-terms he pays with renown. This feels right, because I believe a famous and successful commander should have the possibility to get new tech earlier than "green" ones. Could be that in reality it happened that way.

After several months, technology is generally mass produced and delivered, so all boats can get the upgrades for free after some defined time.

I need to do time-related changes to Basic.cfg - like e.g.
FAT I torp
from 1943/1/1 to 1943/3/1 = 50 renown cost
from 1943/4/1 to 1945/5/1 = 0 renown cost

i think you get the idea - can I do this (easily) with your new beta?

Thanks for help!

Georg Unterberg

[gouldjg]

It is possible a feature to intigrate into the newest SHIII_CMDR version?

I have this Idea:

Ever you sunk a ship and reportet this to the BdU, you get the sam answer.

It is possible to randomise the answer with dificult one´s in SHIII_CMDR?

An if this possible, I could write some answer´s from BdU and will sending this to you.

Sorry, my english isn´t the best... :oops:

greetings from germany

Selle
gouldjg has done it already as part of the "randomised events" feature. There's a post around here with the settings he used, but prolly lost to the ages now with no easy way to find it...

With the randomised events feature (which is included as part of SH3Cmdr R2.5 and will be improved in R2.6) you can randomise *any* **_menu.txt setting, although due to SH3 limitations you'll get the same text label during each SH3 session. This is because SH3 loads and locks the key game files at startup.

You mean this lot. It was a test only but man its good to see new messages. After exam I am so filling it up.

[0_data\Menu\en_menu.txt]
ChooseFrom=13
RndMidPat=1

0_STRINGS|4198=Keep up the good work Kaleun!
1_STRINGS|4198=Great stuff Kaleun!
2_STRINGS|4198=Very impressive!
3_STRINGS|4198=Happy Hunting
4_STRINGS|4198=Look Forward to seeing you back at base!
5_STRINGS|4198=Great stuff Kaleun!
6_STRINGS|4198=Very impressive!
7_STRINGS|4198=Happy Hunting
8_STRINGS|4198=Keep up the good work Kaleun!
9_STRINGS|4198=Great stuff Kaleun!
10_STRINGS|4198=Very impressive!
11_STRINGS|4198=You are doing well

[1_data\Menu\en_menu.txt]
ChooseFrom=6
RndMidPat=1

0_STRINGS|514=I hope she holds!
1_STRINGS|514=Standbye for leaking!
2_STRINGS|514=The men are getting uneasy!
3_STRINGS|514=Do you want me to level off captain?
4_STRINGS|514=I don't think she will hold the pressure!

[2_data\Menu\en_menu.txt]
ChooseFrom=6
RndMidPat=1

0_STRINGS|515=We have never been this deep before!
1_STRINGS|515=Suggest we rise a little!
2_STRINGS|515=The men are nervous Sir!
3_STRINGS|515=I think we should level off?
4_STRINGS|515=The pressure will get us soon!

[3_data\Menu\en_menu.txt]
ChooseFrom=3
RndMidPat=1

0_STRINGS|598=Enemy is pinging us, sir!
1_STRINGS|598=Those Bastards!
2_STRINGS|598=Were being pinged!

[4_data\Menu\en_menu.txt]
ChooseFrom=3
RndMidPat=1

0_STRINGS|599=Enemy ship engaging us, sir!
1_STRINGS|599=There comming for us!
2_STRINGS|599=What shall we do Sir?


[5_data\Menu\en_menu.txt]
ChooseFrom=3
RndMidPat=1

0_STRINGS|601=We may have been detected, sir!
1_STRINGS|601=Damn they have detected us, sir!
2_STRINGS|601=I think they have detected us!

Also like the idea about torpedos from georg_unterberg.

Just a damn shame all these new things have been been discovered now instead of three weeks from now :damn: :damn:

[JScones]

That's the one. :up:

[Selle]

Cool! :up:

Sorry about my short answer, but i´m very busy....

by
Selle