deusvult
|
I've got a session where it won't give me the option on picking what module/scenario my table played. All I can do is fill in the characters' numbers, but cannot report what it is they played (in this case, Feast of Ravenmoor).
Is this the sort of thing a 'wait and try again tomorrow' might fix or do I need the assistance of Paizo's Web Gnomes to report the event now?
Fromper
|
My group has had problems with Feast of Ravenmoor, too. We played it in two sessions, but when the GM tried to report it, the second session rejected for every player, saying that the same person had already played that adventure (the first session). So the web site says we all have 2 less prestige than what's on our chronicle sheets, because we only got half credit for that module.
On the up side, that adventure was a ton of fun. I highly recommend it to anyone who hasn't played it yet.
| Whiskey Jack |
Well today when I went in to try to report it again, all the fields were there. The entire section with the pull down menu where you select the scenario, followed by the GM info fields were literally not there yesterday, but there they are today.
Odd, but hopefully just a temporary glitch.
I haven't had any problems like that in the last twelve weeks or so of reporting sessions. What browser and version of browser are you using? Is it possible that you have any customization to your browser (like Firefox plug-ins) that may affect the rendering of the DOM or interpretation of CSS? You would think if it were a problem with a browser/settings, it would be a constant issue for you and not intermittent.
WJ
EDIT - Flagged this thread such that it might be moved to the "technical issues with the site" area.
Lissa Guillet
|
Well today when I went in to try to report it again, all the fields were there. The entire section with the pull down menu where you select the scenario, followed by the GM info fields were literally not there yesterday, but there they are today.
Odd, but hopefully just a temporary glitch.
IE7 is kinda flaky for some of these things. IE8 specifically had a problem with these that I can't remember. That page also doesn't have anything else on it, which gives it a different set of problems dealing with height. It's something we fixed awhile back but an old CSS sheet might have gotten stuck and it might not have updated 'til today as well.