mdingena / att-voodoo Goto Github PK

changed my language and tried restarting voodoo but still won't pickup my voice my mic is set to the headset but still won't work

So I asked around and some say its the Alta's API being crappy but I'm writing this because maybe there is another reason?

I invited the bot, made him mod but voodo never worked since then. today i kicked and invited him new, but no bot appeared.
server; Badlands End, invite code 144503708

it will not pick up speech on windows

I think windows doesn't trust the app to allow microphone access.

voodo kinda just breaks after the third or second charge of water (refuses to spawn anymore bottles of water). i have voodo on my hand so i saw that it heard me say the right things :P

I've been attempting to log in for 30 minutes. The first time I was sent to the Alta website where it allowed me to use my log-in information. After I did nothing happened. I tried to restart Voodoo. Every time I try to log in now, I get a black webpage, occasionally asking me to open Voodoo even though it's already open. Clicking open does nothing. I have not yet made it passed the authenticating screen.

I can't sign into alta, and yes I checked my system time and a few other things before posting

OS: Windows 10 Pro
Browsers: Opera (Default), Chrome (Fallback)

I can get the app the recognize my voice to awaken and activate, but it will not do anything for incantations. It just sits on the base attunement window. After opening the debug it confirmed that it is hearing me and recognizing the incants, but doesn't recognize the items I have in the belt.

On random occasions the app navigates back to the Ready! screen even after the user has already acquired a play session. The Ready! screen should only be visible for a few seconds.

It seems to happen at random, from within 5 seconds of acquiring the session up to 30 minutes later (and possibly beyond that).

The Network tab in DevTools seems to suggest that there is a second authentication taking place in the background that will force the app to navigate to its /auth-callback route, which shows the Ready! screen because the user is already authenticated.