I find this rather odd.
A stuck bet on a game that doesn't exist
I think this exposes another lie from MGS. The game DOES still exist on the server. Why?
There IS a way to play the old LOTR, and Markus and his "third party casino client" would be able to help.
Since there is no casino offering this game, it was a decision from MGS. Given that it still exists on the server, it was not NECESSARY to force players onto the new one, but is further evidence that the whole thing was designed to FORCE LOTR fans to play the "mega moolah" pooled progressive, and thus contribute around 6% of their
RTP to the pool. This means more winners and faster climbing pools on all the games using this shared pool.
What's next, Mega Moolah Tomb Raider and removal of the old one.
ALL removed games could trigger this error, and could mean quite a few players end up with an unsolvable problem. This is something MGS should have addressed when they changed from their former "never remove an old game" policy.
The removal of the old LOTR was hardly popular, yet popular demand to remove other "crap" games has been resisted by MGS.
It shows there is no practical reason for not giving players the choice between old LOTR and the new progressive version. It's still there taking up space on the server, and still there in the client taking up space on the hard drive.
Front line CS don't stand a chance, the tags that come up for games are not really that clear, and I expect they just saw something like "LOTR 1" against the stuck bet, and assumed it was the current version. It took second line support to discover the problem, and there IS a case for compensation, and 32Red should bend the ears of some MGS execs over this in London.
Bookmarks