Gambling Addiction Test

This test is made to help those who feel unsure about their gambling habits which can negatively affect their life.

Author:Online Best Group (profile at wordpress.org)
WordPress version required:
WordPress version tested:5.6.13
Plugin version:1.0
Added to WordPress repository:12-02-2021
Last updated:20-05-2021
Warning! This plugin has not been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.
Rating, %:0
Rated by:0
Plugin URI:http://casinobest.ca
Total downloads:441
plugin download
Click to start download

Gambling addiction test is created for casino players who spend more time and money on casino games. These players do not enjoy games anymore. This problem is widely spread all over the world. With the help of this test, gamblers can realize at what addiction stage they are at the moment. The test results show the percentage of gambling addiction. There are four results:
Gambling addict.
Close to gambling addiction.
Early stage of addiction.
Not addicted.

A few notes about the sections above:

  • “Contributors” is a comma separated list of wordpress.org usernames
  • “Tags” is a comma separated list of tags that apply to the plugin
  • “Requires at least” is the lowest version that the plugin will work on
  • “Tested up to” is the highest version that you’ve successfully used to test the plugin. Note that it might work on
    higher versions… this is just the highest one you’ve verified.

  • Stable tag should indicate the Subversion “tag” of the latest stable version, or “trunk,” if you use /trunk/ for
    stable.

    Note that the readme.txt of the stable tag is the one that is considered the defining one for the plugin, so
    if the /trunk/readme.txt file says that the stable tag is 4.3, then it is /tags/4.3/readme.txt that’ll be used
    for displaying information about the plugin. In this situation, the only thing considered from the trunk readme.txt
    is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk readme.txt to reflect changes in
    your in-development version, without having that information incorrectly disclosed about the current stable version
    that lacks those changes — as long as the trunk’s readme.txt points to the correct stable tag.

    If no stable tag is provided, it is assumed that trunk is stable, but you should specify “trunk” if that’s where
    you put the stable version, in order to eliminate any doubt.

FAQ
ChangeLog