Multiplayer Belote Changelog

What's new in Multiplayer Belote 1.2.0

Jul 10, 2012
  • Updated the texts inside the game

New in Multiplayer Belote 1.2.0 (Oct 29, 2011)

  • Updated our "send to your friends" function and added facebook support. Now you can send us to your friends using Facebook instead of just email.

New in Multiplayer Belote 1.2.0 (Jun 25, 2011)

  • Fixed a bug in our in the game where the game ad might cause the full screen function to go wrong.
  • You can share your score on Facebook and challenge your friends on Facebook
  • Updated the Facebook share button so you can post your score when you share
  • Fixed a bug in our system which stopped our Twitter status from being updated

New in Multiplayer Belote 1.2.0 (Jun 20, 2011)

  • Added time limit

New in Multiplayer Belote 1.1.0 (Feb 28, 2011)

  • Added an additional .air download to the game.

New in Multiplayer Belote 1.1.0 (Feb 6, 2011)

  • Updated the game so that it works under Windows 7

New in Multiplayer Belote 1.1.0 (Dec 30, 2010)

  • fixed a bug where the facebook, twitter and myspace buttons do not work

New in Multiplayer Belote 1.1.0 (Dec 12, 2010)

  • Updated the Free Lobby Module to support automatic matching of players
  • Updated our Free Preloader Module to support an emailSender parameter so that emails sent will be less likely to be considered as spam
  • Added an emailSender parameter to our Free High Scores Module so that emails sent will be less likely to be considered as spam
  • Fixed a bug where the player cannot enter as guest after a failed login

New in Multiplayer Belote 1.1.0 (Dec 2, 2010)

  • Fixed a bug where the display name is incorrect.
  • Fixed a bug which makes you to fail to enter as guest after a failed log in.

New in Multiplayer Belote 1.1.0 (Nov 29, 2010)

  • Updated the Free Lobby Module to support robots
  • Fixed a potential stability bug in the PHP and ASPX scripts of the Free Lobby Module

New in Multiplayer Belote 1.1.0 (Sep 10, 2010)

  • Fixed a bug in the Free High Scores Module where the page to return to when the close button in the email page was clicked was incorrect