Dice Roller Error
-
Need some advice. A friend who I play PBF (WWII Global 1940 2nd Ed) has had this error (see attachment), when trying to roll combat on his turn. I'm not sure what the problem is, although I suspect it might be a java issue.
I can get him to post on here if it helps, but I can give some information now which might ring a bell with someone who is more qualified.
I believe he's running 9687 stable whereas I'm running 10286.
This is 1st round of this game and his first combat where he is rolling dice (previously there has been no combat, only non combat moves).
The dice server works ok for me (have tested).
We have played before without problems (this is 4th game together).
Any hints, help would be appreciated, otherwise I can tell him tomorrow to post on the forum. -
@ssoloff
The recent server config changes shouldn't have anything to do with this, right?
I'd suspect it might be contacting the wrong port? I recall you submitting a PR a while back fixing some issues with dice server ports.
Is this related or even the same issue? -
@scousemart I would still recommend update java
then repost
Atm I am using latest in pbem vs Wasp
=0 Issues
he is running stable -
@prastle to clarify .11376
vs stable -
@scousemart I think you're running into the same issue fixed here: https://github.com/triplea-game/triplea/pull/3449
You need to be on 10303 or later if you're going to play a PBEM/PBF game using MARTI with someone who has 9687.
-
*Hello, thanks for posting the question and all the responses its very much appreciated. Yes I am the user with the issue.
Un-installed the previous Java version and downloaded the new one (version 8 update 181)
I'm running 1.9.0.0.9687
The game loads fine, but the dice server just isn't happy
Checking the dice server
internal works fine
the Beta is saying that my opponents email is not registeredhowever my opponent sent me a Marti test roll last night (my time)
I can successfully test the dice server as well
I threw some yen into the donation pool as well
-
@donpaulo said in Dice Roller Error:
The game loads fine, but the dice server just isn't happy
Checking the dice server
internal works fine
the Beta is saying that my opponents email is not registeredhowever my opponent sent me a Marti test roll last night (my time)
I can successfully test the dice server as well
Indeed, the beta dice server (dice-staging.tripleawarclub.org) needs a separate registration.
Registering on dice.tripleawarclub.org only does not include the beta server. -
@donpaulo You have two options:
- Your opponent can upgrade to pre-release 10303 or later. They must then load and save the game before re-sending/re-posting the save game file to you (this fixes the bug you're experiencing in not being able to connect to the dice server).
- You can upgrade to pre-release 10303 or later. No change should be required to the save game file you last received.
If you do not want to upgrade your TripleA installation past the latest stable (9687), then option (1) is what you want.
If you want to play the save game your opponent sent you as quickly as possible, then option (2) is what you want.
The latest pre-release is available here.
-
-
@scousemart Can you please post the save game you sent @donpaulo?
-
@ssoloff No probs. Will be away from PC for next 3 hours. Work
0_1534911689096_triplea_Ger1_test_11376.tsvg -
@scousemart @donpaulo Please ignore any emails you receive from me while I test that save game.
-
@ssoloff 0_1534912502249_triplea_Ger1.tsvg
I think this is the file you are requesting
oops I see it was already posted.
well 2 times is better than zero I suppose
-
@scousemart @donpaulo I tried both save games that were posted. Unfortunately, I was not able to reproduce the error message in the latest screenshot above using 9687. All emails appear to have been sent successfully (at least according to my Sent Mail folder; you guys should have both received 7 emails from me between 04:30 and 05:00 UTC).
Not sure what else to try right now, but I'll try to dig into this further tomorrow.
-
@ssoloff Yes I received the emails
thanks
-
@donpaulo I tried something else before shutting down for the night and may have found a possible reason you're getting that error. If I leave the Login field empty on the PBEM configuration screen, I get the same error you did when posting your save game.
Can you verify you're entering your Gmail username and password on the PBEM configuration screen before starting the game?
-
@ssoloff Regarding the previous posts and your investigation of the game save, I too received your emails, so as you say, there isn't a problem. However, @donpaulo and I have been having other problems trying to play a PBEM game.
I downloaded 9687 and started a PBEM game to see if @donpaulo could receive and post. He was unable to. He sent an image of the fault which I've enclosed here:
I've no idea what it is or what is causing it. @donpaulo has uninstalled and reinstalled 9687 so I'd assume the installation would be ok. Maybe it isn't. I said I would post the error but obviously he will have to give more information.
On a side note, I tested a PBEM game using 11376 and 9687 on two pc's, with two different Gmail accounts and I experienced no problems.
I'll email @donpaulo and inform him to seek help here and hopefully you or someone else can figure out the problem. -
@scousemart The screenshot you posted shows that the Login field in the Play By Email configuration is blank. I think that's the root cause of the
AddressException
. @donpaulo needs to enter his Gmail username and password before clicking the Test Email button or playing the game. -
Thanks everyone
I like to think I know my way around a PC, but at times like this I am left shaking my head and questioning my self assessment.
now on to defending britain
I suppose the good out of all of this is that I threw some cash at the site to help out
looking forward to more games in the future !
-
FYI... As of build 11550, you are now required to enter a username and password when using PBEM with either Gmail or Hotmail. Hopefully, that will prevent this rather mysterious error message from confusing someone in the future.