Permissions Changes:Man. Sorry for all the permissions hullabaloo, guys. I had no idea how sensitive/idiosyncratic Chrome was about this stuff. I made two changes to the permissions settings, and apparently that makes Chrome extensions just silently disable themselves (??).
Anyway, I removed the "access your tabs and browsing activity," so I no longer know which porn sites and terrorist forums you're visiting. Only your local ISP, your government, and the 12-yr old who's hacking your wifi do.
The other change was which sites the extension runs on. It used to be "*.goko.com/Dominion/gameClient.html" and now it's "*.goko.com/Dominion/gameClient.html
*". In particular, it now runs on "gameClient.html
?" instead of mysteriously disappearing if you happen to trigger the bug than sends you there.
User SettingsIf something has changed, check here first. If it's not a bug, then there's probably a new option for it.
The "User Settings" link should be on the main screen right under the "Logout" button. Sometimes it goes missing. This is because... well look, it's all magic, ok? Anyway, someday I'll fix it but for now the answer is to reload the page once or twice until it shows up.
In particular, "VP counter: Always request" is now ticked by default. This automatically enables the counter and sends a #vpon request. You can untick it or instead tick "VP counter: Always refuse". That will automatically send a #vpoff if/when your opponent says #vpon.
Documentation![](http://cdn.meme.li/i/ol8qw.jpg)
Yeah. Sorry. I don't like writing docs. Try experimenting a bit. Check the options. Search this thread for my posts. If you figure it out and feel like helping out your fellow f.dsers, add something to the woefully inadequate docs on
the github wiki. I think anyone can edit the wiki who has a github login, but anyone who wants to become a "collaborator" on the project is welcome too.
Bug ReportsEXTENSION BROKE PLZ HLP I M RUNNNIG THE COMPUTER VERSIN!
On rare occasions I can usefully respond to such reports, but the wise user will tell me at least his browser (e.g. Chrome) and extension version (e.g. v2.3.2). Detail like "Safari v6.0.5 build 8536.30.1" and "Windows 8, Toaster Edition" is unnecessary.
Your odds of getting help go up further if you can include a screenshot and instructions for reproducing the error. "This happened once..." is rarely enough for me to diagnose a problem.
If you're really serious about getting the problem fixed, include a copy of your Javascript console log. This is particularly valuable when the problem is that something is
not happening (e.g. extension not loading at all):
1. Go to User Settings and enable "Extra logging"
2. Open the JS console (F12 in Chrome; Command-Alt-C in Safari; Tools/Web Developer/Browser Console in Firefox)
3. Reproduce the error and copy the log
4. Include the log in your post, preferably wrapped in "code" tags.
Finally, please refrain from posting "when are you going to fix XYZ?" The answer is, "Whenever I figure out how to make it work for everyone besides you." There have only been a few of these posts (you know who you are). Bumping old requests (say ~1 wk+) is just fine.