ME question

[Kyth]

Kyth
  Thanks for getting back to this. Nope, not giving up just a bad case of the flu. My line is now edited to this-all is the same as yours with the exception of 0, and it's still a no-show.

ext, add_mo, map0, attack_rub, 0xc0000080, 0x80202020, 4.0, 0, txt_md_ger_startzone1,  0, startzone1, -1, true, 0;

I'm deleting the  "0" to see what happens, and.......nothing. makes no difference. the symbol does not show up.

Make sure there's an actual contour in the Mission Editor map that's named "startzone1".  Not "Startzone1" or "startzone01" etc.
The name in the script must match up.

ext, add_mo, map0, attack_rub, 0xc0000080, 0x80202020, 4.0, txt_md_ger_startzone1, 0, startzone1, -1, true, 0;

should get a rather large symbol plonked down on the briefing screen:

[hemisent]

Kyth & Iceman
  Success at last. Got the blue symbol but the text was gray question marks. I played around with the text line and finally found my error.

Thanks-off to make copies of these working lines and sort of make a tutorial to myself-more questions to follow I'm sure.

Cheers
H

[Kyth]

Kyth & Iceman
  Success at last. Got the blue symbol but the text was gray question marks. I played around with the text line and finally found my error.

Thanks-off to make copies of these working lines and sort of make a tutorial to myself-more questions to follow I'm sure.

Cheers
H

Okay, good  Add this to your tutorial:

In adding any map object, (the ext, add_mo command) the following describes the relevant settings in each line:

               1       2           3            4       5             6            7       8       9   10   11
ext, add_mo, map0, attack_rub, 0xc0000080, 0x80202020, 4.0, txt_md_ger_startzone1, 0, startzone1, -1, true, 0;

1. Name of the object, or group of objects. Useful for changing colours, or removing later on.

2. Symbol or sprite name. Refer to table 9.2 for a listing.

3. Symbol colour (0x, alpha, red, green, blue)

4. Text colour (0x, alpha, red, green, blue), if any.

5. Size of the object. At any one size, some symbols are already larger than others, so play around to see what's suitable.

6. Text string for (4), if any.

7. Skew / tilt angle of the symbol in degrees. Ranges from -180 to 180. '0' = symbol follows the map contour heading.

8. Map contour for the placement of the symbol.

9. Contour point number. Default '-1' (not specific). Anyway, try to use one-point contours for placement of symbols.

10. Rotate along with the map, true / false. Flag symbols should always be upright, hence, 'false'. (Flag placement contours should point due north).

11. Offset value for text, left-right.  Default value '0' (centered).

[frinik]

 Hem Hemi we are all impatiently waiting for your first mission....

[Iceman]

added to FAQ

[Kyth]

added to FAQ

Thanks, 

[frinik]

Hemi-ssion! We want our first Hemi-ssion

[hemisent]

Kyth
 That was exactly what I needed. Up to now I've been filling in the the different items with what I have gathered from the various threads and replies but a lot was left open. This helped out a bunch.

 I haven't even gotten to the radio messages and triggers yet but what I would like is a short, step by step guide to the initial mission briefing. I know it seems like I don't read the manual that much but I do and I really have a hard time deciphering it the way it presented. I've read all the threads I can find about the briefing but cannot get it to show up. I'm sure it's some small error but so far unable to pin it down

Frinik
 I have something in mind but still need to firm up my understanding of many of these fine points. I believe the briefing, map info and radio traffic are just as important to a good mission experience as the actual mission itself. That's why I find Kyth's missions so amazing and now I have a bit of understanding of all that goes into it.

 Again, thanks to all for the help.

H



 

[Kyth]

 what I would like is a short, step by step guide to the initial mission briefing.

Hi,

Actually adding the lines for the initial briefing is one of the easier things. 

Take the example below:

   ext, add_misobj, brief, map_ritmental, 4, txt_brief_testmission_1, txt_mis_order;
   nop;

The 1st line consists of:

- The command ext, add_misobj (add mission objective)
- Name of the objective, in this case just 'brief'
- Contour on the map. Supposedly the location of the ultimate objective. But you can leave it blank also,
- Status of the objective ( 4 - information only )
- Text string for the briefing, goes into the main box in the briefing screen.
- Text string for a description, goes into the side-box in the briefing screen. In this case, use the txt_mis_order string - "Mission"

The 2nd line, which is 'nop;' (no operation) indicates that the game should pause here and wait for the player to start.   

[Kyth]

Talking about the briefing, it's best to format it in a readable and presentable way.

Take the 'inspiring' briefing example below: 

   Well, now it's official:

   We're surrounded!

   The breakout is planned for tonight - you and your tank platoon will take the lead, along with whatever infantry support we can collar. You will be heading in the direction of Ritmental, where we think they won't be expecting us. Watch out for ambushes!

   And one more thing, don't screw up, or it'll surely be the last time ever for you!

Formatting tags for the in-game text strings are:

\t - tab or indent
\n - move to next line

The example above would look like this in the 'xxx_loc_data.text' file:

   txt_brief_testmission_1() { \n\t\tWell, now it's official: \n\n\t\tWe're surrounded!\n\n\t\tThe breakout is planned for tonight - you and your tank platoon will take the lead, along with whatever infantry support we can collar. You will be heading in the direction of Ritmental, where we think they won't be expecting us. Watch out for ambushes!\n\n\t\tAnd one more thing, don't screw up, or it'll surely be the last time ever for you!; }

The end-result should look like the screen below:



Good luck, but you won't need it, if you follow my instructions exactly!

[hemisent]

Thanks kyth
 This is what I was looking for. Except.......you mention the loc_data.text file. I've seen this file name in other threads and for the life of me I cannot find it. The closest thing I come up with is in the
data/k42/loc_rus/text folder, which contains three filer with the loc_ prefix:

loc_kit.text
loc_kit_subs.text
loc_kit_tools.text

Can you direct me or is this yet another folder my DL'd version is missing?

Thanks
H

[Rends]

hemi
 check your data/k42/loc_rus/levels/LEVELS/SCRIPTS/"campaign name" directory for the text files

[hemisent]

Thanks Rends
I knew it had to be something dumb. I was looking in the wrong area.

I plugged in Kyth's example in my test mission file and I still get nothing on the initial briefing screen.

//Graviteam mission create system ver. 0.1

loc_rus()
{
//äîáàâü òåêñò ñþäà
//â ôîðìàòå txt_ldm_<èìÿ òàáëèöû íà àíãëèéñêîì>() { <òåêñò1> ; <òåêñò2>; ... <òåêñò n>; }
//ïðèìåð: txt_ldm_text1() { Òåêñòîâàÿ ñòðîêà ¹1; }

}
loc_eng()
{txt_brief_single tiger-02() { \n\t\tWell, now it's official: \n\n\t\tWe're surrounded!\n\n\t\tThe breakout is planned for tonight - you and your tank platoon will take the lead, along with whatever infantry support we can collar. You will be heading in the direction of Ritmental, where we think they won't be expecting us. Watch out for ambushes!\n\n\t\tAnd one more thing, don't screw up, or it'll surely be the last time ever for you!; }
 }

[Kyth]

I plugged in Kyth's example in my test mission file and I still get nothing on the initial briefing screen.

//Graviteam mission create system ver. 0.1

loc_rus()
{
//äîáàâü òåêñò ñþäà
//â ôîðìàòå txt_ldm_<èìÿ òàáëèöû íà àíãëèéñêîì>() { <òåêñò1> ; <òåêñò2>; ... <òåêñò n>; }
//ïðèìåð: txt_ldm_text1() { Òåêñòîâàÿ ñòðîêà ¹1; }

}
loc_eng()
{txt_brief_single tiger-02() { \n\t\tWell, now it's official: \n\n\t\tWe're surrounded!\n\n\t\tThe breakout is planned for tonight - you and your tank platoon will take the lead, along with whatever infantry support we can collar. You will be heading in the direction of Ritmental, where we think they won't be expecting us. Watch out for ambushes!\n\n\t\tAnd one more thing, don't screw up, or it'll surely be the last time ever for you!; }
 }

The name of the text string should not have any spaces in between. Avoid dashes also. Like this: txt_brief_single_tiger_02

Did you add in the 2 lines, mentioned in my earlier post? They should be in the cs_main() section, by the way. Let's take a look at them,

[Iceman]

Thanks Rends
I knew it had to be something dumb. I was looking in the wrong area.

I plugged in Kyth's example in my test mission file and I still get nothing on the initial briefing screen.

//Graviteam mission create system ver. 0.1

loc_rus()
{
//äîáàâü òåêñò ñþäà
//â ôîðìàòå txt_ldm_<èìÿ òàáëèöû íà àíãëèéñêîì>() { <òåêñò1> ; <òåêñò2>; ... <òåêñò n>; }
//ïðèìåð: txt_ldm_text1() { Òåêñòîâàÿ ñòðîêà ¹1; }

}
loc_eng()
{txt_brief_single tiger-02() { \n\t\tWell, now it's official: \n\n\t\tWe're surrounded!\n\n\t\tThe breakout is planned for tonight - you and your tank platoon will take the lead, along with whatever infantry support we can collar. You will be heading in the direction of Ritmental, where we think they won't be expecting us. Watch out for ambushes!\n\n\t\tAnd one more thing, don't screw up, or it'll surely be the last time ever for you!; }
 }

Do not use section loc_eng()!
Write all text in section loc_rus()
The section loc_eng() more isn't actual after localization

Additional. The program ignores the standard line breaks and tabs.
So you can divide lines for the convenience
Ie will work like this

Code:

loc_rus()
{
txt_brief_single_tiger_02() { \n\t\tWell, now it's official: \n\n\t\tWe're surrounded!\n\n\t\tThe breakout is planned for tonight - you and your tank platoon will take the lead, along with whatever infantry support we can collar. You will be heading in the direction of Ritmental, where we think they won't be expecting us. Watch out for ambushes!\n\n\t\tAnd one more thing, don't screw up, or it'll surely be the last time ever for you!; }
}

and this

Code:

loc_rus()
{
txt_brief_single_tiger_02() { \n\t\tWell, now it's official:\n\n\
t\tWe're surrounded!\n\n
\t\tThe breakout is planned for tonight - you and your tank platoon will take the lead, along with whatever infantry support we can collar. You will be heading in the direction of Ritmental, where we think they won't be expecting us. Watch out for ambushes!\n\n
\t\tAnd one more thing, don't screw up, or it'll surely be the last time ever for you!; }

}

And like say Kith, not use any spaces and dashes in name of identifiers.

P.S. Example of text from mission for video-lesson
 Original
 Google translation