I have been working on a complete rewrite of AnCasino the past couple of weeks, and I have decided to deploy a beta version so I can ensure that everything works nicely for the official release. The plugin works largely the same way as you are used to, and this page will detail some of the changes you need to be aware of to give it a spin.

I emphasize that this is a beta release, and that you might encounter errors, bugs, and other kind of nonsense. I will be updating this release frequently until it is ready for official release, so do inform me of any problems or suggestions you might have. Without further ado, you may now grab the plugin right below.

Download Here - Always the latest beta version

You will probably want to read up on some of the changes before using this version, so continue on reading below.

Configuration

The layout of config.yml has changed slightly from v1.2, so it is recommended that you delete your config file prior to installing. A few options have been added to the config file, and should be self-explanatory. Slot machines are saved in a slightly different format as well, but should still be compatible with the old format.

Managed Slot Machines

Many have requested an option to have slot machines take money from and return money to a player, and and a system for this is finally in place. Managed slot machines can be added via the command /casino addmanaged, and the owner can then deposit funds into the slot machine with /casino deposit <slot> <amount>. This money is spent on dispensing rewards, and the use-cost of the machine is added to this deposit upon every spin. If there is not enough money in the slot machine to dispense the highest prize, the slot machine will be disabled. The owner can withdraw their potential profits with /casino withdraw <slot> <amount>.

Player-Owned Slot machines

A system is now in place which allows for normal players to join in on the fun and create their own slot machines. Depending on permissions, a player can create both managed and normal unmanaged slot machines. Players are only allowed to create slot machine types as outlined in the permissions section below. A creation cost is defined for each slot machine type, and the player will be charged this amount when creating either kind of slot machine. Players are able to edit their own slot machines similarly to admins, but are not allowed to see usage statistics (mostly because they are not recorded on a per-slot basis).

Permissions

The permissions format has changed somewhat from v1.2, so make sure to update your permissions as follows:

ancasino.use

This permission now acts as the universal permission node for access to slot machines and types. A user is required to have this permission in order to use slot machines, and will at the same time grant permission to use all types of slot machines. If you wish to deny access to a certain type of slot machine, give them a negative permission node like so: -ancasino.use.<type>.

ancasino.create

A new permission node designed to give users the ability to create their own slot machines. Functions similarly to the new ancasino.use permission. Give a player -ancasino.create.<type> to deny access to creation of that type. Refer to the separate section on slot machines for more information about this.

ancasino.manage

Allows for the creation of managed slot machines. Refer to the separate section on this for more information.