Quote:
Originally Posted by vdr1981
Optional addon for grid reposition combat order would also be cool , IF you can come up with solution for mentioned in game current year problem...  |
I'll release an updated version where you can select the year as well.
To be honest I haven't finished a campaign mission or career in a long time. I seem to have the
modder's illness where I always want to make a mod instead of just playing the game.
That's not a bad thing because I'm enjoying making them. That's why I'm not very familiar with the messages during campaign.
So for example in a file like this:
Code:
[Text]
MissionTitle=Patrol the specified area AM2258
MissionBriefing=Patrol the specified area AM2258
Patrol the designated area=Patrol area assigned. Reach the area AM2258 and start operations. Attack any enemy contact
Reposition and patrol the designated area=Reposition and continue patrol operations AE8868
Patrol the specified area=Reposition and continue operations AM2296
Fail4A=Combat task accomplished. In the presence of torpedoes, conduct free anti-shipping operations, otherwise return to base. BdU
Info80R1=Patrol AM2258 zone radius 120 km. Time of patrol 24 hours. BdU
Info80R2=Reposition. Patrol AE8868 zone radius 120 km. Time of patrol 24 hours. BdU
Info80R3=Reposition. Patrol AM2296 zone radius 120 km. Time of patrol 24 hours. BdU
Which parts come as message? I'm guessing some are for description and others show up during game-play, right? Do they show up once the player reaches an area and finishes the time of patrol? What do the endings ...4A ...80R1 ...80R2 mean?
My thought was to create a program to read all the "info...=" in the .tsr files, change numbers and punctuation, and encrypt all at once since these are pretty short. Maybe we can make a package with all these encrypted messages, to give the player options. That's probably what you're doing already.
Another thing, some of the .tsr files like infiltrate, intercept, etc. don't seem to have the same structure. Do they still "send" in game messages?
Quote:
Originally Posted by gap
Besides making the process totally automatic (in my idea, only the tagging of messages that need to be encoded should be manual), the advantage of an automatic encoder scripted directly into the game would be that recursive campaign messages woul be encoded with the correct format for the current year/month. Again I realize that building such an encoder into the game might not be that easy. Just thinking out aloud  |
That's actually a good idea for the combat messages, because it would avoid you being in 1943 and having to decode a message encoded in 1939, making it more realistic.
Save