VoxelSniper

VoxelSniper

1M Downloads

Getting rid of performers and VoxelLists

kethomassen opened this issue ยท 5 comments

commented

We should get rid of performers completely. A replacement would be /v 35:4 - mat-mat could be implemented by /vr having a none option, or n. (/vr n)

Now, VoxelLists could be replaced by /vr 5,6,7,8:3 for example. To use exclusions you simply have to add a ! /v could also support multiple values, which could be randomly spread. They could also have a percentage, /v 20%stone,80%dirt

Example use:

/b b
/b 5
/v 10%wool:green,10%grass,80%stone
/vr !:5,!:7,!wool:yellow

This would replace everything (except blocks with the data value of 5 or 7, as well as yellow wool) with 10% of green wool, 10% of grass and 80% of stone in a ball with the size of 5.

Using this system we would no longer need to use performers. This would also be much stronger than performers as the last example, is not currently possible with performers ( I think? )

commented

No, more no.

You should go back to original sniper when we didn't have performers and had a system like this(It was terrible, like, you wanted to break your keyboard).

Performers solve problems, this just requires recoding of a working, functional, and great system.

The issue here is you don't like performers, or don't understand them:

"This would also be much stronger than performers as the last example, is not currently possible with performers ( I think? )"

Anything possible with blocks can be done with performers. Also your "syntax" requires heavy command parsing & disgusting UI...

commented

Yes I do understand performers completely and can use them very well. You could do that example with performers - but it would take multiple snipes. In total, that version would probably be less typing than performers. Yes - it would be a lot of code for it to be implemented, however we would no longer need a whole folder full of different performers. Again, this method would be much stronger than performers because you could do stuff in one snipe, that would usually take two, or more.

commented

I'm not arguing this, and I'm pretty sure myself & the rest of the server would say no to this. VS6 is built around performers, it's not changing now.

commented

Denied. There are already plans for VoxelSniper until Version 7, that are far beyond what you are expecting here.

commented

"You have to think bigger than just the server."

FYI VoxelPlugins were created for our server, and we decided to release them to the public.