deleted this add-on because it was literally the worst add-on inconvenience ever.
the old RTB manager will do just fine.
I find that incredibly surprising as you can configure Glass to be nearly silent and purely in the background. Sorry that your experience wasn't the best, but if you'd like to see change then we need more input than that.
nice
all of these just appeared at the same time
Interesting. I'm curious if it was a network issue or a problem with the notifications themselves. I'll work on notification pooling when I have time.
two bugs i noticed with preferences:
- it doesnt update the preferences window if i edited values through eval/whatnot before opening the preferences window
- if i edit the server name/welcome message without changing the length of the string, it wont detect that the value has been changed
The first one is hard to compensate for unless we constantly check the variables to see if they've changed, and if that's put on a schedule then there'll be a delay to the gui updating. Will check on the second issue.
I do have to admit, seeing all those messages all the time unless your disconnect from glass is very annoying.
If wish there was a way to make it so you can still be connected to glass but not have that constantly popping up.
If there is PLEASE tell me!
If not then please make it so!
You've been able to disable most notifications since day one.
Had an issue where I was unable to join my own server due to sequence "base/data/shapes/player" missing for m.dts; removing Glass fixed the issue. This was with a dedicated server where the client im joining the server with is the same that the server is hosted on. I was able to join it fine with an alternate install without glass.
Oddly enough, if I spammed join attempts to my server on the client that got rejected, i would be able to get in after a number of times, only to suffer a runtime error or crash midway through loading.
notably, the console spammed connection dropped errors (iirc error 7 and 3), despite the inital posting to glass server being successful. Earlier today i was able to join my own server with Glass running, and at that time api.blocklandglass.com was connecting fine.
I don't believe Glass touches anything that could possibly cause that issue, and I think that's been a long standing engine issue when hosting a dedicated server while playing on the same installation.
I can't log into my Glass account.
Why? I've forgotten my password
OR
Someone is using my ID, though unlikely.
Password recovery coming this week.