Monopoly is a multi-player economics-themed board game. In the game, players roll two dice to move around the game board, buying and trading properties, and developing them with houses and hotels. Players collect rent from their opponents, aiming to drive them to bankruptcy.
Implement Logic and required UI changes to accommodate case where player is in jail
Implement logic to see if user is only visiting jail or he is in the jail
or
You can make it simple by just considering it a jail, which means if a user comes in jail he has to pay a 100$, no other option will be given and the amount will be automatically deducted and on the next turn if a user is in debt user will be shown pop with the options declare bankruptcy or repay debt, repay debt option will only be enabled if the user has assets of more worth than the dept otherwise user will have to declare bankruptcy
add some sort of time, if the time is over an appropriate action will be taken, such set active user, if the user had no other option than bankruptcy than declare bankruptcy.
When a user comes on to go to jail user has to go back to jail
When a user comes on chance in which user has to move back to someplace
In short, I just need to calculate how many corners the user is crossing and use logic that I am currently using to handle a single corner and modify it to handle multiple corners.
E.g. When a user comes from row 1 to row to the user has to through jail.
When a user comes to row 4 from row 1 user has to go through jail, resort, and go to jail to reach there(For cases like this I have to modify existing logic)
If a player has just crossed jail/go/parking/go to jail and mortgage one his land then there an unnecessary movement happens, Player goes back to crossing point jail/go/parking/go to jail and from there he comes back to the current position
To fix this we can use a flag called isMoved and while moving players you can check if the player has already moved that way we can prevent unnecessary movement of player
Your website is not connected with social media using the API's provided by Facebook, Google +, Twitter, Pinterest, or using addthis.com
Your website is not using a custom 404 error page. Default 404 error pages result in a poor experience - it can mislead users into thinking an entire site is down or broken, greatly increases the chance they leave your site entirely, and looks unprofessional. By creating a custom 404 error page, you can improve your website's user experience by letting users know that only a specific page is missing/broken (and not your entire site), providing them helpful links, the opportunity to report bugs, and potentially track the source of broken links in your site.
It does not appear that you are caching your pages. Cached pages serve up static html and avoid potentially time consuming queries to your database. It also helps lower server load by up to 80%. Caching most visibly benefits high traffic pages that access a database, but whose content does not change on every page view. Common caching methods include Alternative PHP Cache, Quickcache, and WP Super Cache (for Wordpress sites). Caching mechanisms also typically compress HTML, further reducing page size and load time.
Your server signature is on. Turning off your server signature is generally a good idea from a security standpoint. Read more on how to turn off server signature and improve your website's security.
Your website is not using cache headers for your JavaScript resources. Setting cache headers can help speed up the serving of your webpages for users that regularly visit your site.
Your website is not using cache headers for your images. Setting cache headers can help speed up the serving of your webpages for users that regularly visit your site and see the same images. Learn more about how to add expires headers to your images.
A Google Analytics script is not detected on this page. While there are several tools available to monitor your site's visitors and traffic sources, Google Analytics is a free, commonly recommended program to help diagnose potential SEO issues.
Your website is not using cache headers for your CSS resources. Setting cache headers can help speed up the serving of your webpages for users that regularly visit your site.
Your webpage doesn't take the advantages of HTML Microdata specifications in order to markup structured data. View Google's guide for getting started with microdata.
Your DNS server is not using an SPF record. SPF (Sender Policy Framework) allows administrators to specify which hosts are allowed to send mail from a given domain by creating a specific SPF record or TXT record in the Domain Name System (DNS). You can find more information about SPF records here.
add h1 heading to page
use good hedings on page
This page has only very few internal links. If it's a welcome page, consider removing it
Based on the calculations repay debt option will be enabled/disabled
if the user doesn't have assets which is worth more than or equal to dept, then the repay debt option will be disabled, and the user will have no other choice than to declare bankruptcy