ParadeFloat (1.8)

Discussion in 'Plugin Requests' started by chefcarl2004, Dec 31, 2015.

Thread Status:
Not open for further replies.
  1. Offline

    chefcarl2004

    Plugin category: World Editing and Management

    Suggested name: ParadeFloat

    What I want: I would like to have a plugin where i can use command blocks to move large "floats". I would be able to select an area to move, and how many blocks per second it moves.

    Ideas for commands: /paradefloat <x1> <y1> <z1> <x2> <y2> <z2> <x change per second> <y change per second> <z change per second> <total seconds for the float to move before ending>

    Example: Let's say i had a float that is between the coordinates (12, 36, -17) and (15, 40, -20). I want to move it one block up once every second, and i want the rising to last for 5 seconds. (+1 Y per second, lasting 5 seconds). The command would look like: /paradefloat 12 36 -17 15 40 -20 0 1 0 5

    Ideas for permissions: N/A, the command is only used in a command block, which only OP's can use.

    When I'd like it by:
    A couple weeks, who knows. I have no requirement. If i had to wait a year i would.

    Thanks!
     
  2. Offline

    chefcarl2004

  3. Offline

    bitFred

    I'll have a look at this.
    EDIT: This plugin could drastically decrease your performance if the BPS and the selected float is too big, just a tip.
     
  4. Offline

    chefcarl2004

    Yeah, I was wondering if it would be easier to use a WorldEdit schematic file, so the command would be like

    /paradefloat <schematic name> <x1> <y1> <z1> <ticks between moves> <x blocks change per "move"> <y blocks change per move> <z blocks change per move> <total time in ticks before moving stops>

    If you've started on the original version, it's no problem. As for the decrease in performance, the floats wouldn't be too big, and I would most likely have them move at a 1 block per second speed. (20 ticks between moves)

    Thanks for your help!

    EDIT: The <x1> <y1> <z1> would be the starting coordinates or the float. Does this seem easier for you to do, or would sticking with the bunch of coordinates to copy blocks over be easier? I could go with either.
     
    Last edited: Jan 2, 2016
Thread Status:
Not open for further replies.

Share This Page