
Oladon |
Chrome News
Account's been reinstated, but the reinstatement doesn't automatically republish the extension. I've gotten in touch with a few people (real people!) over at Google who may be able to help, so I'm going to hold off on republishing for now in hopes that I can get some real answers.
If I start hearing that Chrome is removing the extension from people's browsers, or we go too long without progress on the human front, I'll go ahead and republish it as-is.

Oladon |
Chrome News
Good news and bad news. The good news is:
- 1.2.0 is back up in the store
- I've got a human contact at Google who's in a position to Make Things Happen
- said contact has acknowledged that all the take-downs are 100% Google's fault and (best part) that "a fix [for the false positive flagging issue] has been submitted"
The bad news is my contact recommended waiting until next week to resubmit the update (presumably to give that team time to apply their fix), so you Chrome users won't get 2.0.1 until then.

Oladon |
Everyone should weigh in on my latest request for input! (Unless you don't care about that feature, in which case, you may refrain.)
Chrome News
Resubmitted 2.0.1 last night... got a takedown notice in response. Extension is still available in the store as 1.2.0. Working with my contact to get 2.0.1 out...

Oladon |
Chrome News
I've now (well, as of last night) released version 2.0.2 for Chrome on the advice of my contact in hopes that it'll kick their system into accepting it. It's exactly the same as 2.0.1 except for a comment in the code to make them "different".
On the plus side, it /sounds/ like they may be making changes to their system in response to my getting in touch with them, which may make a difference in how often this issue recurs in the future.
Will continue to keep you all updated.

Oladon |
News
I've just released version 2.1.1 (will I finally succeed in unifying the version number across the Chrome/Firefox versions??) with two new features:
- The Alias Selector will now work in replies, and
- You may now set custom avatars for posters on the messageboards.
As usual, it'll probably take a few days for the new versions to be reviewed; I'll post again when they are.
- Caveats
- Custom avatars are for you only; there's no automatic sharing with other users of the extension. If you'd like to let others know what avatar you're using for a certain alias, I'd recommend placing a link to the image in the alias's profile with a label like "Avatar:", and then letting people know that it's there.
- You can't set a custom avatar for someone who doesn't have a Paizo avatar set (e.g. me). Just a complexity thing; I've got a Trello card to add that functionality in the future, but didn't want to delay this release.
- Using non-square images will result in skewed avatars. Use an image manipulation program to crop your avatar images to a fairly small square (Paizo's avatars are 90x90).
- I might have missed some places where avatars are displayed... if so, please let me know here or in a PM and I'll try to add them.
- The alias selector in replies will display your base alias until you preview. I'm hoping Paizo will help me make it default to the correct alias when you first click it, but for now it doesn't work that way.
I really enjoy working on this project. Your support (both financial and other) lets me know it's valuable. Thank you!

![]() |

The new version has autoinstalled on Firefox for me.
ETA: The custom avatar selector highlights when I mouse over my avatar. I replied to a comment and although the avatar shown was my main one the avatar selector showed the default ID for that thread.

Oladon |
The new version has autoinstalled on Firefox for me.
ETA: The custom avatar selector highlights when I mouse over my avatar. I replied to a comment and although the avatar shown was my main one the avatar selector showed the default ID for that thread.
Awesome that it's auto-updating.
You can set a custom avatar for your own aliases, just like any other.
When replying to a post, the "poster" will be your base alias until you preview. I've asked Paizo to help me make it default to the correct alias when you first click it, but for now it doesn't work that way.

Oladon |
Love what you've done with this tool so far.
I have a question (this may not be technically possible). When we black/greylist somebody, can there be an option to also not see all of their aliases as well as the name we enter?
Thanks for your consideration and for your hard work! <3
Thank you! Great suggestion, and definitely doable. Let me add it to the list and see where I can fit it in. Thanks for your support and feedback!
Chrome News
The Bad: the extension has been taken down (removed from the store) again.
The Good: I finally got a real answer as to why this keeps happening. It's every bit as silly a reason as I'd thought, and has nothing to do with the code (I'm serious).
I'm working with my contact to get the extension back up and change the thing that's triggering the false positives. Hopeful ETA: before the end of this week.

Oladon |
Love what you've done with this tool so far.
I have a question (this may not be technically possible). When we black/greylist somebody, can there be an option to also not see all of their aliases as well as the name we enter?
Thanks for your consideration and for your hard work! <3
I just went and poked around in the code to see how hard this would be to implement, and discovered that this is already how it works. If I blacklist "Treppa", it will apply to all of your aliases as well as your base user. Is it possible that you were in a thread where you have the blacklist set to not apply?

Treppa |

Treppa wrote:I just went and poked around in the code to see how hard this would be to implement, and discovered that this is already how it works. If I blacklist "Treppa", it will apply to all of your aliases as well as your base user. Is it possible that you were in a thread where you have the blacklist set to not apply?Love what you've done with this tool so far.
I have a question (this may not be technically possible). When we black/greylist somebody, can there be an option to also not see all of their aliases as well as the name we enter?
Thanks for your consideration and for your hard work! <3
Hmm, I will check.
EDIT: It works! I think somebody else made a similar gag alias and it fooled me. My opinion of your awesomeness has increased, and you didn't even have to do anything new!

Oladon |
Is this supposed to work for all aliases? I'm currently in two PbP games, in one it uses the alias for that games character while in the other one it uses the message board default alias.
It is, yes. Have you visited your base user's campaigns page recently?

Oladon |
Don't know why, but it seems to me like the "Default Alias per Campaign" feature died with the last firefox update.
Anyone able to confirm this?Using Firefox 51.01 under Ubuntu and Win10 and in both places it seem to have stopped working as I am stuck with the "default alias" from the account setting again. Also it seems that it doesn't remember aliases marked as unactive.
Any thoughts?
Hi Swordwhale,
The last Firefox version has been out for over a month, and this is the first I've heard of any issues with it. I've been using it actively during that time as well.
Could you start by PMing me your Options for the extension? It'll be easier to troubleshoot over PMs.
Thanks!

![]() |

The most recent version would not work for me (Windows 10, Firefox 53.0.3). I installed version 1.29 and it's working fine, but I would like some of the features that aren't in this version.
A very brief description of the problem I was having:
The reformatting of the campaigns page worked, but when I went into the extension's options, I could change things, but there was no 'OK' or 'apply' or similar button, so every time I closed the options tab, it forgot what I entered. Also, options opened a new tab. In the older version that worked, the options instead came up as a smaller window.
It was the same behavior when I disabled all other extensions, uninstalled the PCT extension, restarted my computer, and then installed PCT.

TheAlicornSage |

Does the firefox plugin work for android firefox, or only windows firefox (they are independent variations)?
Also, where can I get it? The front page links to github, but it is not clear where I'm supposed to click to download something and I've never done enough with github to be familiar with it. Also, isn't github supposed to be for source files? Does that mean I'd have to compile the tools myself?

Lady Ladile |

I've actually been having an odd issue with the latest Chrome version. Most of the features seem to work except that neither the Campaign Sorter nor the New Post Highlighter functions work when viewing my own Campaigns page. However, they work fine when I view the Campaigns pages for other users which baffles me to no end.
@TheAlicornSage - I can't answer most of those questions but I believe that the extension currently only exists in desktop format and isn't available for mobile in either form (Firefox or Chrome). Here is the Firefox version of the extension, though it looks like it might not currently be compatible with the latest version of Firefox.

Oladon |
Redelia, very strange behavior... thanks for the report. Windows 10 may very well be the issue, but I'll spend some time looking into it the next time I have time to work on this project.
TheAlicornSage, currently the extension "should" work on Firefox for Android, but doesn't. I'm not entirely sure if it's simply the fact that the options page needs to be converted to a different format, or whether there are other things going on there.
Lady Ladile, I'm actually somewhat glad to hear of your issue, because it's consistent with another report I recently received from someone with a space in his name. I suspect there may have been some recent change with the site that's messing with the extension for people with spaces.
I'm overwhelmed with personal and work stuff right now such that I don't honestly know when I'll be able to look into these issues -- and I'm sorry to tell you all that. However, posting here to let you know that I've heard you and you're still on my radar.
And of course, if someone else feels inclined to investigate these issues, code contributions are always welcome.

Oladon |
Mobile News
As of today, the extension has started working on my Android (in Firefox). Still can't get to the options page, but the default options appear to be set correctly, with the result that new post highlighting and default alias selection are both working. Haven't tested the other features.
This may bump up the priority of getting the options page working on mobile...

Oladon |
Jesse and Ladile, thanks for the reports/updates. This is the first I've heard of the Firefox version having issues... I'll definitely continue to investigate. It should help to know that it's cross-browser.
Ladile, there was indeed a new Chrome version released recently, but I've no idea why it would fix your issues! Happy to take it, though. :)
I should have some time this weekend to look into these issues; I'll keep you all posted (pun totally intended).

Oladon |
3 people marked this as a favorite. |
Chrome & Firefox News
Great news, everyone... I've fixed some bugs and released version 2.2.0! Bugs fixed:
- Blacklist links in Firefox weren't showing up
- Users with tons of campaigns were getting odd results with the Campaign Arranger (Jesse Heinig, possibly formerly Lady Ladile)
- PFS characters with no avatar were causing issues on Aliases pages
- The Alias Selector was trying to run on pages with no posting box
- Disabling the Campaign Arranger will now fully disable it
Firefox Version (available now)
Chrome Version (publishing in progress, should be available soon)
Mobile (Firefox for Android) News
The extension is now fully functional on Firefox for Android, including the options page. In addition, I've added a new feature for mobile which can be enabled on the options page (it's disabled by default). If enabled, it'll format the campaigns page to make it easier to read & use on a small screen.
Apparently, the version of Firefox for Android that's currently out doesn't actually support the things I just wrote (since I was using the Nightly version to test). Sorry, everyone... I'll poke more at it another day. For now, you're stuck with the default options.
Windows 10 News
Unfortunately, this version may or may not fix the issues those of you who're using Windows 10 are experiencing. Please let me know if it does, but if not, know that I haven't forgotten about you!

Oladon |
Firefox for Android Options
Small update for my technically-inclined users: there is actually a way to access the options page on mobile.
1. First, visit about:config and search for "uuids". You should see an entry with the name "extensions.webextensions.uuids". Copy the UUID from that entry named "pct@mydomain.org".
2. Open a new tab. Using the UUID you just got, enter: [code]moz-extension://[color=orange]UUID[/color]/content/options.html[/code]
3. Bookmark the page for easier access in the future.

![]() |

I'm a relatively tech-savvy user, could you tell me if there is a text file I could get into and edit by hand to turn on the options I want? If the only problem is that the config page doesn't actually make changes, this seems like a good temporary fix.

Oladon |
Redelia, the options are stored in localStorage. I haven't had time to investigate the Win 10 issue yet, but my suspicion based on your description is that they did something to localStorage that's preventing the options from being saved.
ETA: the other thing you can do is set the values directly in about:config. If you'd like, you can PM me the settings with how you'd like them set, and I can tell you which keys and values to add.

Oladon |
Mobile News (Firefox for Android)
I've just released version 2.2.1 for Firefox, which adds an Options button to Campaigns pages. This is a temporary work-around until Firefox for Android 56 is released, when we should be able to access the Options page in a more normal fashion.
Regardless, you can disable the options button on the options page if you don't want it there... just be warned that getting /back/ to the options page may be difficult.
2.2.1 is currently in the review queue (not sure why 2.2.0 was released automatically and 2.2.1 has to go through review, but...); hopefully it'll be available within a few days.

GM Red Box |

Here Win10Pro and Home Win10
Acrobate, Ebates and a the google docs ones seem to be working fine.
These might help.
Screen Grab 1
Would love to learn that I am just doing it wrong. :)

Oladon |
Ah, I think you might be suffering from the same issue as Redelia was.
Could you try checking your cookie settings (as well as any "privacy" extensions) to ensure you're only blocking third-party cookies?
Details:
This extension doesn't use cookies, but for some reason, Chrome in Windows 10 seems to associate cookies with localStorage (which this extension uses for saving your options). Thus, if your browser is set to block all cookies, then (for some inexplicable reason), it won't allow the extension to save its settings in localStorage either.

GM Red Box |

Oladon |
News! (Version 2.4.0 Released)
I've just released version 2.4.0 of the extension for both Chrome and Firefox, and it's fully approved and available. This release fixes a bug with custom avatars breaking in threads where avatarless users have posted, and also adds two new features:
- [code]Code [/code] tags will now preserve whitespace that doesn't occur at the beginning of a line*
- "Need to Post" Indicator: this feature (disabled by default) is intended to remind you to post in your campaigns. Consider this the first version of the feature; I'm sure it will evolve with your feedback. In short, it turns on when there are new posts (or you click the icon to enable it), and turns off when you post in that campaign (or you click the icon to disable it).
As always, let me know if you experience any issues or have any questions or feedback!
* This limitation is due to Paizo removing whitespace at the beginning of lines, and my reluctance to replace line-initial whitespace with non-whitespace "whitespace" characters, which would impact the site for users without this extension installed.