[REL] Patrol Routine Scripts

[TheDarkWraith]

Originally Posted by Abd_von_Mumit

So this is the answer to your question - I can't use these two commands as the script is intended to run "silently" in high TC. However I'll test them a bit and consider making alternative scripts for those who don't mind going to lower TC and manning the station themselves as well. Maybe we'll find some more issues to fix.

there are commands available to automatically man and disman the stations in Automation

[Abd_von_Mumit]

Originally Posted by TheDarkWraith

there are commands available to automatically man and disman the stations in Automation

But would Sweep_hydrophone,x,y,a,b work as intended if the station was unmanned immediately upon command start and TC x128 restored? As I understand manning the station drops TC to 1, so I would then have to:
1. switch to NavMap (TC x128 is not possible in first person view),
2. Restore TC x128

[TheDarkWraith]

Originally Posted by Abd_von_Mumit

But would Sweep_hydrophone,x,y,a,b work as intended if the station was unmanned immediately upon command start and TC x128 restored?

nope. I have condition in the Sweep_hydrophone command that says if station is not manned in 15 seconds to order a skip command.

[Abd_von_Mumit]

Originally Posted by TheDarkWraith

nope. I have condition in the Sweep_hydrophone command that says if station is not manned in 15 seconds to order a skip command.

So conclusion is I can't use the two Sweep commands without interrupting TC x128, is that correct?

Btw, while testing the scripts I came to conclusion that there should be a "Description" tag that would show its value on hover in game. Well, also a "Print" would be good, that sends its value to message box, possibly with some parameters... I know, I know... :P

[TheDarkWraith]

Originally Posted by Abd_von_Mumit

So conclusion is I can't use the two Sweep commands without interrupting TC x128, is that correct?

Btw, while testing the scripts I came to conclusion that there should be a "Description" tag that would show its value on hover in game. Well, also a "Print" would be good, that sends its value to message box, possibly with some parameters... I know, I know... :P

manning hydrophone doesn't drop your TC level to 1. Just tried it at TC32 and it stayed at 32.

You can exceed 32 inside the sub but you have to edit your \Documents\SH5\data\cfg\main.cfg file:

[TIME COMPRESSION]
; The first value is the default one, the second value is used when 'travel mode' is activated.
; The two values should be separated by a comma.
; If only one value is specified, that value is used for both default and travel mode.
TimeStop=0
RealTime=1
LandProximity=8,8192
CriticalDamage=1,1024
CrewEfficiency=128
AirEnemyDetected=1,8
SoundEffects=2
CharacterAnim=32
FriendDetected=32,8192
EnemyDetected=8,64
RadioReport=32,8192
Particles=32
PrayState=8,32
HunterState=8,32
3DRender=32
Maximum=8192

I believe 3DRender is the value that will need to be changed to be able to exceed 32 inside the sub.

What is this "Description" tag and "Print" that you are referencing? What would they do?

[Abd_von_Mumit]

Originally Posted by TheDarkWraith

[...] I believe 3DRender is the value that will need to be changed to be able to exceed 32 inside the sub.

I understand that, but that would require players to manually edit the file if they wanted the TC to be higher than x32, which kind of defeats the purpose of this simple little mod. I'll think about it though.

Originally Posted by TheDarkWraith

What is this "Description" tag and "Print" that you are referencing? What would they do?

Description would be to tell player what the automation script does or whatever else the author would need to include in it. This would serve user friendliness - I assume the number of user scripts will grow fast as time passes, and one day people will have too many of them to remember what each one of them is for (name is too short to include all details). As an example for my main script the value of Description would say something like:

Runs at TC x128 in NavMap mode,
every ~1 hour does a sonar scan at depth of 20 metres
then goes back to surface to fuel efficient speed,
intended to use in open waters for searching contacts.
Runs until stopped by user.

This would show on mouse hover in Automation window.

Print would just post a message in message box, for example I would add a line that says "New depth 20 metres", as for a reason I don't know Set_new_depth doesn't give a message in message box at all.

It could serve other purposes, like a script that reminds you every X hours to do something ("Herr Kaleun, time to clean the toilet Sir!", "Talk to Cook for another Special Meal", "Past Midnight, time to update your ChalkBoard!") and so on.


Another suggestion is: the message box info about a loop being started again is a bit of an immersion killer. Players use scripts, but do they want to be reminded about that in the message box?

[TheDarkWraith]

Originally Posted by Abd_von_Mumit

Description would be to tell player what the automation script does or whatever else the author would need to include in it. This would serve user friendliness - I assume the number of user scripts will grow fast as time passes, and one day people will have too many of them to remember what each one of them is for (name is too short to include all details). As an example for my main script the value of Description would say something like:

Runs at TC x128 in NavMap mode,
every ~1 hour does a sonar scan at depth of 20 metres
then goes back to surface to fuel efficient speed,
intended to use in open waters for searching contacts.
Runs until stopped by user.

This would show on mouse hover in Automation window.

Print would just post a message in message box, for example I would add a line that says "New depth 20 metres", as for a reason I don't know Set_new_depth doesn't give a message in message box at all.

It could serve other purposes, like a script that reminds you every X hours to do something ("Herr Kaleun, time to clean the toilet Sir!", "Talk to Cook for another Special Meal", "Past Midnight, time to update your ChalkBoard!") and so on.

Another suggestion is: the message box info about a loop being started again is a bit of an immersion killer. Players use scripts, but do they want to be reminded about that in the message box?

I like the Print thing...I'll add a new command in Automation for this

Description I like also but it would fundamentally change the script parser....I'll see what I can do.

What I'll do about the start, stop, and loop message box messages from Automation is to define a user option so you can control if they are all displayed or not.