Halloween Trick Or Treating 2.4

Lets your players go trick or treating, to celebrate Halloween correctly!

  1. LocutusOfNord
    Native Minecraft Version:
    1.14
    Tested Minecraft Versions:
    • 1.12
    • 1.13
    • 1.14
    • 1.15
    • 1.16
    Languages Supported:
    Spanish, Finnish
    For 1.12, use v1.1 of this plugin.

    Please note that 2.X versions are IN NO WAY BACKWARDS COMPATIBLE with 1.X versions (but 1.x configs can be updated to 2.x configs without too much work).


    This is my first plugin, so I would really appreciate feedback in order to improve.


    A Spigot plugin to allow your players to go trick or treating!


    Note video is of v1.1

    Players can knock on doors, and get CUSTOM treats (or tricks) defined by a series of console commands in the config.yml file.

    Once you've enabled the doors, all your players need to do is knock on any part of the doors in a very intuitive way (more specifically, they must PUNCH the CLOSED door THREE TIMES with an EMPTY HAND within 5 seconds, which is plenty of time to punch a block three times).

    They will then see a particle effect (if enabled) on the door(s), and after a moment, the door(s) will fling open, with a sound effect (if enabled), to show their "prize".

    COMMANDS:
    PERMISSIONS:
    tot.* — all admin commands


    /regdoor <x> <y> <z>
    Saves the door at x,y,z in the database, enabling trick or treating at that door.
    Only one side of a door is enabled for trick-or-treating, and you must register the door from the side you want to enable. Also note that the two blocks behind each door will be automatically set to air each time the door is used (normally, they're going to be air anyway).

    /regdoubdoor <x1> <y1> <z1> <x2> <y2> <z2>
    Saves a set of double doors (one at x1,y1,z1, the other at x2,y2,z2 [must be next to each other on the same y-level]) in the database, enabling trick or treating at those doors.
    Only one side of a door is enabled for trick-or-treating, and you must register the door from the side you want to enable. Also note that the two blocks behind each door will be automatically set to air each time the door is used (normally, they're going to be air anyway).
    Also note that double doors may not overlap - that is to say that both doors in a double door set must not already be in the database.


    /listdoors <page_num>
    Lists the doors that have been saved to the database, in groups of ten, by their row_id in the database. A page number can optionally be specified to view that section of results (for example, page 2 would be results 11-20) AFTER HAVING RUN THE INITIAL LOOKUP.

    /deldoor <id>
    Deletes the specified door, using the row_id specified in listdoor results. In the future, I may add in the possibility of deleting a door by coordinates, but I judged it more important to get the plugin published so that people could use it for Halloween.

    /deldoorall
    Deletes the entire database of saved doors. Obviously, USE WITH CAUTION.

    /reloadtotconfig
    Reloads config.yml, as you might expect.

    /resetinteractions (<player name> | all)
    Resets the limit counter for all players or for one specific player.

    CONFIG:

    In the config file, you can specify your own tricks and treats using normal console commands (without the preceding slash). For example:
    rewards:
    creeper:
    name: Hisssssss...
    where: door
    commands:
    command1: summon minecraft:creeper <<x>> <<y>> <<z>>
    weight: 1
    will summon a creeper behind the door when the player knocks.

    NAME
    specifies what this result will be called in the chat and in the log file.
    WHERE specifies whether to use the coordinates of the door (actually, the block BEHIND the door) or the player if replacing coordinates in commands (see following).
    COMMANDS SECTION specifies the console commands to run if this result is chosen (they are randomly selected). You can enter any console commands you would normally be able to run, and you can run several commands in a row (each command MUST have a different key value [e.g. command1, command2, etc...]!).
    <<x>>, <<y>>, and <<z>> are replaced at execution with the appropriate part of the coordinates specified in WHERE. <<player_name>> is replaced by the name of the trick-or-treater, so "kill <<player_name>>", for example, would kill the trick-or-treater if it's selected.
    WEIGHT specifies the reward's weight in the randomized selection process. Its probability of being selected is (weight)/(sum of ALL prize weights).

    Saving a door:
    2017-10-22_17.23.16.png

    Knocking on a door:
    2017-10-22_17.23.55.png

    Got lit TNT:
    2017-10-22_17.24.45.png

Recent Updates

  1. 1.16+ compatibility!
  2. Spanish translation added
  3. Bug fix and Finnish language support

Recent Reviews

  1. mrfloris
    mrfloris
    5/5,
    Version: 2.4
    Last year I said: "I have a feeling I will be back for a 1.16 version next year ;) " Well, here we are. 1.16.3 and it's ready yet again. Great support, great plugin, players love it. I can't wait to use it on our production servers. Thank you again for the hard work despite it being 2020.
  2. mrfloris
    mrfloris
    5/5,
    Version: 2.1
    Woah, I used this plugin last year and it needed an update. I spoke with the developer and I got a working version! This year I was worried I wouldn't be this lucky and threw down a list of bugs, feature requests and 'can it do this stuff', the result was that the developer completely rewrote the version for 1.13.2 so we can use it on 1.13.2 and 1.14.4 this year, and in time for Halloween. It works exactly how I wanted it to, and I am very happy with the personal support, the working version, and I therefore did not hesitate to donate some PayPal money towards the project. I have a feeling I will be back for a 1.16 version next year ;) Thank you so much for the hard work and the support, it's soooo appreciated. Fantastic job on version 1 and 2.
    1. LocutusOfNord
      Author's Response
      I'm glad to hear you're happy with the plugin (and thanks for the donations too)! My own players are enjoying it too.

      It was a bumpy road getting v2.0/v2.1 out the door, but it happened in the end, and with so many improvements over the 1.x versions.

      Hopefully another entire rewrite won't be needed to bring the current version up to date for 1.15 or 1.16 or whatever we're on next Halloween. :)
  3. snw
    snw
    5/5,
    Version: 1.1
    Thank you for this! I'd pay for something like this in the future. A lot of effort has gone into this for sure.
    1. LocutusOfNord
      Author's Response
      Hey, thanks! It was really nice to hear you like it, and I hope it worked well for you.