Search the Community

Hello everybody I am in need for some guidance and advices so if any of you knows of any way to help, everything is appreciated We will soon start developing casino-style games for a client of ours. So imagine very simple to play games such as slots, flipping cards, etc. User will make a single "Play/Spin/Draw" action and be presented with the outcome of the game. The games will be available on their website and need to be accessible to people through their web browsers on their computers and cellphones. The only "trick" is - the games will be linked to players' real accounts and real money will be both lost and won in those games. Now, the first and most important question is, what approaches to take to make the game tamper-proof and as secure as possible? I couldn't find very much material online, or maybe I just didn't know where/how to look. What I did manage to find out is what is pretty much known to me already - the server is the king. So, when the user is playing a game and makes a roll of the dice or the slots, the request is sent to the server, a result is generated, stored in the database and returned. "That way the user has absolutely no way to do any harm and we can always keep everything in control" -> is safe to make such an assumption, or is it too ignorant/naive? If the user modifies the sent value (for example bet amount), it will still be validated on the server anyway? If the user modifies the return value (for example game outcome/win amount), it still won't matter because the server has already saved the valid outcome and while it might bring joy to the user to see fake winnings, he still won't be doing us harm? Of course, we would still love to minimise (or eliminate, if possible) such events rather than let everyone have a go at trying to modify the game behaviour. Regarding the implementation of the game, security aside, it seems to me that the obvious approach to take would be one of the available HTML5/JS/CSS game engines. But isn't there the problem that with that kind of game the source is always visible and accessible? I am aware there are "uglification" methods which make the code harder to read, but is that enough to keep hobby "hackers" (or even more determined ones) away? Should I worry about the "ease" with which someone can gain access to the client side code when we use this approach, or should we focus on other elements? Also, regarding the client-server communication, how to handle it to ensure maximum security? Are sockets the way to go or something else? I saw on some other sites which host that kind of games that they use Flash, is there any security reason for that? Anyway it isn't really an option as first, we don't have any real experience with it, and second, we have to keep all mobile devices in mind. Any advices, experiences, links to existing articles/documentation/tutorials etc. which deal with the whole matter would be greatly appreciated! Thanks and Kind regards Darko ---- EDIT Just noticed this thread might fit better under "Coding and Game Design" so if a Mod would be kind enough to move it, I'd appreciate it