I'm not entirely sure how to implement the ITranslatable interface here though. If anyone who actually knows C# could give me a hand, I'd be really grateful.
MonoBevahiour scripts that implement ITranslatable will be picked up by the Speech Manager provided that it an instance of it is in one of your scenes.
It looks like your InvManager script is what needs to implement this - though bear in mind you could also store the text in Global String Variables instead. These can be translated automatically, and you can then read their values in the game's current language through script - see the Manual's "Variable scripting" chapter for more.
How would I go adapting the script so that it can be used to affect Use interactions instead of Inventory Interactions? The goal is to be able to, depending on the hotspot, read "Look at" or "Marvel at" or "Walk to" or "Shiver at" without the need to create a cursor for each of those, just replacing the text to display when choosing a classic "use" interaction.
Besides that one, anoter of the reasons I am asking is because I have 8 Arrow cursors (named Arrow Up, Arrow UpRight, etc). I need the names to be different for backend purposes, but on the front end I would like all of them to display "Walk to scene", instead of "Arrow DR scene" as it displays right now. That's why I believe it's a good idea to be able to control the text displayed depending on the Hotspot.
I reckon the script can't be that different from the one we have right now, but I have no clue where to start adapting it.
For what backend purposes do you need the cursor names to be different?
You shouldn't need a script so complicated as the above to deal just with Hotspots - the following, attached to each Hotspot you want to override, should do it:
The reason I need different names is so I can select each of them when needed (instead of choosing from a list where everything is named "walk to"). The script will also help me make a few hotspot dependant jokes that I was initially renouncing on because I wasn't going to create a cursor for a one-Time thing.
Comments
Here are @KevRev 's scripts to include both the verb and the preposition.
InvManager.cs
ItemOverride.cs
InvManagerEditor.cs
I'm not entirely sure how to implement the ITranslatable interface here though. If anyone who actually knows C# could give me a hand, I'd be really grateful.
MonoBevahiour scripts that implement ITranslatable will be picked up by the Speech Manager provided that it an instance of it is in one of your scenes.
It looks like your InvManager script is what needs to implement this - though bear in mind you could also store the text in Global String Variables instead. These can be translated automatically, and you can then read their values in the game's current language through script - see the Manual's "Variable scripting" chapter for more.
How would I go adapting the script so that it can be used to affect Use interactions instead of Inventory Interactions? The goal is to be able to, depending on the hotspot, read "Look at" or "Marvel at" or "Walk to" or "Shiver at" without the need to create a cursor for each of those, just replacing the text to display when choosing a classic "use" interaction.
Besides that one, anoter of the reasons I am asking is because I have 8 Arrow cursors (named Arrow Up, Arrow UpRight, etc). I need the names to be different for backend purposes, but on the front end I would like all of them to display "Walk to scene", instead of "Arrow DR scene" as it displays right now. That's why I believe it's a good idea to be able to control the text displayed depending on the Hotspot.
I reckon the script can't be that different from the one we have right now, but I have no clue where to start adapting it.
Thanks!!!
For what backend purposes do you need the cursor names to be different?
You shouldn't need a script so complicated as the above to deal just with Hotspots - the following, attached to each Hotspot you want to override, should do it:
Thanks Chris, that did the job beautifully.
The reason I need different names is so I can select each of them when needed (instead of choosing from a list where everything is named "walk to"). The script will also help me make a few hotspot dependant jokes that I was initially renouncing on because I wasn't going to create a cursor for a one-Time thing.