- Thread starter jrider
- Start date
Users who are viewing this thread
Doktor_e5
Banned
# Jrider + TITLES v0.3.2 update both player and troop titles
(try_begin),
I found out that the error due to this piece of code!
How can I fix it?
(try_begin),
Code:
(store_troop_faction, ":troop_faction", ":troop_no"),
(eq, ":troop_faction", "$players_kingdom"),
(call_script, "script_troop_set_title_according_to_faction_gender_and_lands", "trp_player", "$players_kingdom"),
(call_script, "script_troop_set_title_according_to_faction_gender_and_lands", ":troop_no", "$players_kingdom"),
(try_end),
# Jrider -I found out that the error due to this piece of code!
How can I fix it?
Code:
Initializing...
Compiling all global variables...
Exporting strings...
Exporting skills...
Exporting tracks...
Exporting animations...
Exporting meshes...
Exporting sounds...
Exporting skins...
Exporting map icons...
Creating new tag_uses.txt file...
Creating new quick_strings.txt file...
Exporting faction data...
Exporting item data...
Exporting scene data...
Exporting troops data
Exporting particle data...
Exporting scene props...
Exporting tableau materials data...
Exporting presentations...
Exporting party_template data...
Exporting parties
Exporting quest data...
Exporting info_page data...
Exporting scripts...
ERROR: Usage of unassigned local variable: :troop_no
ERROR: Usage of unassigned local variable: :troop_no
Exporting mission_template data...
Exporting game menus data...
exporting simple triggers...
exporting triggers...
exporting dialogs...
Checking global variable usages...
Exporting postfx_params...
______________________________
Script processing has ended.
Press any key to exit. . .
Search module scripts for the variable and manually fix it. 
Otherwise, you probably added something incorrectly
Otherwise, you probably added something incorrectly
all done but during compile i have this error
Code:
Initializing...
Compiling all global variables...
Exporting strings...
Exporting skills...
Exporting tracks...
Exporting animations...
Exporting meshes...
Exporting sounds...
Exporting skins...
Exporting map icons...
Creating new tag_uses.txt file...
Creating new quick_strings.txt file...
Exporting faction data...
Exporting item data...
Exporting scene data...
Exporting troops data
Exporting particle data...
Exporting scene props...
Exporting tableau materials data...
Exporting presentations...
Error: Unable to find object:str_name_kingdom_text
ERROR: Illegal Identifier:str_name_kingdom_text
Error: Unable to find object:str_default_kingdom_name
ERROR: Illegal Identifier:str_default_kingdom_name
Error: Unable to find object:str_default_kingdom_name
ERROR: Illegal Identifier:str_default_kingdom_name
Exporting party_template data...
Exporting parties
Exporting quest data...
Exporting info_page data...
Exporting scripts...
Exporting mission_template data...
Exporting game menus data...
exporting simple triggers...
exporting triggers...
exporting dialogs...
Checking global variable usages...
Imported 21 global variables for saved-game compatability that are not used.
Exporting postfx_params...
______________________________
Script processing has ended.
Press any key to exit. . .
So i'm a noob on the coding stuff, how do you actually use this?
I tried to comment out the titles etc for companions, the fisque, hero etc. but everytime i do it i get a missing str OR just a read error, any more indepth explenation on how to remove it? i like it for the lords etc, jsut not the companions when they are in my party (their names get a bit long for my liking)
I wonder if one may know if it is ok or not to use it in 1.171 module system... Or how to achieve such things in 1.171? Ta for any help...
---
So sorry that I wasn't clear enough – it is always one of my biggest disadvantages.. I meant if the version 1.171 is ok or not because sometimes I use OSP that doesn't fit 1.171 & crash... But still cheers to Eärendil tho
---
So sorry that I wasn't clear enough – it is always one of my biggest disadvantages.. I meant if the version 1.171 is ok or not because sometimes I use OSP that doesn't fit 1.171 & crash... But still cheers to Eärendil tho
Last edited:
It's an OSP code, you are allowed to use it.
Yeah, he edited his post after I wrote the response ^^No, I believe he asks if the OSP is compatible with the 1.171 module system.
It should be possible to use it with the latest module system, yes.
If you want I can annoy you until you tested it
Sorry for the double post, but it is important and relevant to the thread (and that's why I choose to make separate post and not edit my previous one ).
During Christmas I tested the script in the latest system + Dipomacy 1.154. There are a couple of differences, in the 1.171 Native due to scripts being updated and in the Diplomacy MS due to Dipomacy's additions and edits; nothing major, just you need to watch the lines and not follow the OP blindly. But other than that, it is fully compatible so far, with both. With the usual caveats, I have no doubt it would be compatible with anything else, provided you edit it to adapt to any module changes you did.
).During Christmas I tested the script in the latest system + Dipomacy 1.154. There are a couple of differences, in the 1.171 Native due to scripts being updated and in the Diplomacy MS due to Dipomacy's additions and edits; nothing major, just you need to watch the lines and not follow the OP blindly. But other than that, it is fully compatible so far, with both. With the usual caveats, I have no doubt it would be compatible with anything else, provided you edit it to adapt to any module changes you did.
