You must login to post a comment. Don't have an account? Register to get one!

• 

  • Reply
  • #1298

  jkmalan May 22, 2013 at 00:50 UTC - 0 likes

  @Andy1517: Go

  There are conflicts between the plugins because they use a lot of the same methods from the Bukkit code as well as similar commands and possibilities. You can avoid many of these problems if you spend some extra time making sure that there are no command conflicts or configuration conflicts. Do not expect them to work together easily.

• 

  • Reply
  • #1297

  Andy1517 May 21, 2013 at 23:22 UTC - 0 likes

  Will this plugin conflict with the Essentials plugin??? Can I have them both installed???

• 

  • Reply
  • #1296

  jkmalan May 18, 2013 at 01:21 UTC - 0 likes

  @craftovski: Go

  Make sure you're putting it in the quotes:

  '397:1'

• 

  • Reply
  • #1295

  craftovski May 17, 2013 at 23:55 UTC - 0 likes

  @jkmalan: Go

  Lol i was looking there but didnt find it, thx.

  1 More thing if anyone knows, how to set data of items in kits, for example for heads id is 397 but it doesnt accept 397:1 and i tried adding data: 1 but that didnt work either.

  Thx

  Last edited May 18, 2013 by craftovski

  46.4.20.136 -> bedrockcraft Dedicated server with 50 slots and nice plugins.

• 

  • Reply
  • #1294

  jkmalan May 17, 2013 at 22:05 UTC - 0 likes

  @craftovski: Go

  Its under special permissions on the wiki. The node is admincmd.spec.notprequest

• 

  • Reply
  • #1293

  craftovski May 17, 2013 at 14:11 UTC - 0 likes

  How to give admin permission to teleport to other ppl without needing approval from other player without giving him admincmd.*. I tried giving admins admincmd.tp.* but they still need approval.

  Thx.

• 

  • Reply
  • #1292

  JeterLP May 12, 2013 at 14:42 UTC - 0 likes

  The german translation file does not work! Please fix that.

  

  

• 

  • Reply
  • #1291

  jkmalan May 10, 2013 at 18:45 UTC - 0 likes

  @nejcneo: Go

  We already have a command that should do that, /asuser <player> <command [arguments]> The ability to chat as that player though isn't included, try making a ticket on the bugtracker for that as a feature request.

  Accepting multiple requests might be nice, but I don't think it'll be practical because each request expires after the set time in the config, and /tpt yes accepts the most recent request so it works fine as is. If you have another reason, you can make a separate ticket for this as well.

• 

  • Reply
  • #1290

  nejcneo May 10, 2013 at 07:59 UTC - 0 likes

  Fake say: "/fsay <player> <message>". So "player" will say "message" in chat. Forcing player to say message by commands. Works even with commands "/fsay <player> /spawn" This will teleport player to spawn. About TPT did you think to add "/tpt yes <player>" (for multi request at same time) To accept only specific player

• 

  • Reply
  • #1289

  jkmalan May 09, 2013 at 18:49 UTC - 0 likes

  @nejcneo: Go

  What do you mean by fake say? Do you mean /broadcast?

  And to set up your tp request system, there are a few steps.

  1. In the config, make sure you have this set to true

  tpRequestActivatedByDefault: true
  

  2. Next, give the normal teleport permissions to the group you want to be able to tp request

  3. You also have to give that group the permission admincmd.tp.toggle.allow

  4. Finally, give staff groups and any groups that bypass it admincmd.spec.notprequest

  5. Players can now use /tp and /tphere, but the receiving player must use /tpt yes to accept the teleport. Any group with the permission from step 3, automatically teleports like normal