Error 16 when trying to post to metaverse

Error --> "(16) The results of this game could not be posted to the Metaverse. Would you like to try posting your results again?"

This is the first game I have attempted to post (or play) since updating to DA 1.7.

pndrev mentioned in #72 here that he got the same error.

I have a saved game I can send if that will help diagnose this problem.
3,608 views 13 replies
Reply #1 Top
I've got the same problem.
Reply #2 Top
Hmmm... So much for using the beta for a league game it looks like.
Reply #3 Top
Actually, that was my league game
Reply #4 Top
That sucks. Did you archive when you updated? You could revert back and play another or use DL if your unable to roll it back.
Reply #5 Top
Actually, that was my league game

We already have a precedent for this. When FireBender started he was having "Error 12" issues and we allowed his submission with the posting of a screenshot of the game.

See post #55 of the "The Metaverse League" Results & League Ladder thread. Only the post of the victory screen is probably necessary, although it's a good idea to repeat the setting used.
Reply #6 Top

Archiving will not change the version of the save game, so that won't help.

The next update should fix the issue with submitting the games.

Reply #7 Top

Archiving will not change the version of the save game, so that won't help.


The next update should fix the issue with submitting the games.



So are you saying that I will never be able to post the 2 conquest maps I've completed with 1.7? If that the case I won't be playing any Metaverse games until it is fixed. On that note, is there an ETA for the next update?

Reply #8 Top
So are you saying that I will never be able to post the 2 conquest maps I've completed with 1.7? If that the case I won't be playing any Metaverse games until it is fixed. On that note, is there an ETA for the next update?

Note that AFAIK this is v1.7 *Beta*. Issues and glitches with a Beta are to be expected. You can avoid this by letting others be the guinea pigs and wait at least a week before updating.

Also it is not necessarily true that you won't be able to submit the two games started under v1.7. Most updates that I'm familiar with will allow the game to be started in the previous rev and submitted in a later rev that may not have this issue. I'm not sure that will be the case here but I assume that it's far more likely than not.
Reply #9 Top
Just tried posting the same saved game to the metaverse after updating to v1.72... received the same error
Reply #10 Top
For safety you should always start a fresh game with each new update. Whilst some things are ok to move between the versions the majority are not. This has always been the case and is especially true with beta builds. The error for MV posting may well have been caused at the initial start of the game and by playing a later version the error will not disappear, rather it will still be there in the saved game.


Harry Potter Fans - Join Dumbledores Army and fight in the Metaverse together

Reply #11 Top
Just updated to the new beta and played a quick tech games and it posted fine. Still can't post the games started with 1.7 beta1 though.
Reply #12 Top
Just updated to the new beta and played a quick tech games and it posted fine. Still can't post the games started with 1.7 beta1 though.


If it was an issue with the 1.7b1 metaversedata folder (IIRC it was), a patch can't retroactively fix games since the 'bad' data is included in the saves.
Reply #13 Top

Just updated to the new beta and played a quick tech games and it posted fine. Still can't post the games started with 1.7 beta1 though.


If it was an issue with the 1.7b1 metaversedata folder (IIRC it was), a patch can't retroactively fix games since the 'bad' data is included in the saves.




Thanks for the update. No problem, I'll delete those save files.