Announcements

In General
Be respectful! There's another person on the other end of that conversation! The forums are a place to discuss anything related to Overwolf and beyond but want this to be a place where people feel comfortable to participate and have fun!
Keep it on topic, keep it constructive - Threads should be constructive and have a clear topic. Replies to that topic should be relevant. Bumping a thread without adding relevant information is not considered constructive. Bumping a thread from a long time ago is also not constructive (Overwolf updates every 2 weeks, things change).
Attacks or Accusations are not acceptable - Attacking another person is unacceptable, the circumstances are irrelevant, just don't do it.
Read the topic - Know what people are talking about in the thread. Stick to the given topic and don't derail it.
Search - We have a great search function, use it before you post a new thread as it's possible someone has asked your question before and there's info on it. Don't see something about your question or topic after searching? Post it! (keep in mind that bumping threads from a long time ago is not recommended, post your own).
Don't post about locked or deleted topics; they were deleted for a reason.
No petitions, demands or "When will.." We have places for asking for games, features and we will tell you when something is coming. We don't give dates for a reason.
Don't try getting around the swear filter, it's not cute or funny.
This is not a place to break NDA's, talk about something illegal or break any law from any country. We will contact the necessary parties involved and you will be pursued to the extent of the law.
No spam. You will be banned and your post deleted.
Please write in English. This is an international forum and we'd like everyone to be able to participate.
Bad Behavior
Insults, racial slurs, profanity, vulgarity.
Trolling - You know who you are, and we will find you.
Nudity, porn or anything obscene.
Flaming - We don't have a trained fireman on staff, so don't do it.
No advertising - No one wants to buy that shirt off of you, or that WoW gold.
No insulting any religion (fake, real, or imagined), sexual orientation, gender or culture.
No talking about drugs or performing illegal activities.
Impersonation - Don't do it, people find out and you end up looking stupid.
What will we do if you break a rule?
Warnings - You get only one.
Thread/Post deletion - We delete your thread/post from the forums.
Suspension - Temporary forum ban.
Account termination - Permanent forum ban.
Legal action or report violations to the appropriate legal authorities.

Dear gamers, how about some DIY? -
http://support.overwolf.com/
The knowledge-base for all your Overwolf related troubleshooting, faq, bugs, known issues and much more!
Just start typing anything related to your issue (for example, 'fps' or 'heartharena') and discover new ways to work things out.

Hi
It would be problematic.
In overwolf you can only use C# SpeechRecognitionEngine for this.
You would somehow need to redirect team speak audio source into default input device, maybe with virtual cable or voicemeter, or somehow get audio stream from teamspeak.
With that you could turn dictation mode and recognize spoken words.
Having all that then it would be possible but It might work poorly since it is window recognition requires training (you need to train engine to correctly recognize your voice or voice of your friend by reading some phrases shown by windows), without training the recognition either wouldn't work or it would work poorly.
I still need to update my own recognition apps into c#, so when I will do that I might also look into your request, but I'm packed at the moment but if I do anything I will update this page.

Most likely the developers that made those apps didn't port their plugins to new format (Overwolf removed support for NPAPI plugins and all apps that are not ported were removed from store), I didn't port my own apps yet, so I imagine it will take a while for others too but it will depend on creators (they might not be willing to port it).

Well if overwolf is not supported then of course they wont see anything you have in overwolf.
However if you stream with xsplit or obs you can use this chat and add it as one of the scenes in those programs so that your stream can see it.

I know this is old but I played around with window.open functions.
You can open a popup window (it will have id of parent window)
var newwin = window.open('index.html', 'popUp',"height=300,width=450,location=no,scrollba rs=no,menubars=no,toolbars=no,resizable=no, menubar=no");newwin.focus();
Child window can access parent window variables and DOM
window.opener.overwolf
You cant really make the window transparent so it will have default overwolf window look but I thought it is interesting.
You probably won't be able to call anything from overwolf.window to affect that opened popup (same id as parent) but maybe someone will make something interesting with it.

You can always open overwolf browser (play in windowed, or open it in normal browser) and open NighDevs twitch chat widget (https://www.nightdev.com/kapchat/) - you just fill couple of things, get a link and open it in browser window.
If it is needed for obs just open that link in obs browser source

I don't know what they will support or not I'm just saying your code will stop working (if I'm not mistaken, the goal is to move all apps that use NPAPI plugins to the new way, in about 2 months support will end)
Plugin are loaded now with extra-objects in manifest and with overwolf.extensions.current.getExtraObject("Name", function (result) {}); in javascript

Not to diminish your work but Overwolf is moving away from NPAPI plugin architecture so you would need to rewrite your code and use the new way of loading dlls (check simple io plugin c# code for an example).

Maybe stupid question but - did you try to create Action as a member object of the class you exposing to overwolf, like in sample app ( onGlobalEvent )?
In c#
public event Action<object> InfoEvent;
Then in js
libObj.InfoEvent.addListener(onInfoEvent);
I think calling local member does not work since reference to it will be lost after function call (or something like that, for me it also does not work if callback is called from new Thread() and works if callback is a member), so you cant make multiple calls to a local callback, it wont work but the global one can be used anywhere.