Skocz do zawartości

PoweredDragon

Użytkownik
  • Ilość zawartości

    3064
  • Rejestracja

  • Ostatnia wizyta

  • Wygrane w rankingu

    4

Treść opublikowana przez PoweredDragon

  1. PoweredDragon

    Skrypt na granaty

    1. Jakie są błędy 2. Molotov 3. To masz: command /granade: trigger: give snowball named "&2Granat" to player command /molotov: trigger: give slimeball named "&4Molotov" to player on rightclick with snowball: name of player's tool "&2Granat": shoot a snowball from player set {grenade::%shot projectile%} to "Grenade" on rightclick with slimeball: name of player's tool "&4Molotov": shoot a snowball from player set {grenade::%shot projectile%} to "Molotov" on shoot: {grenade::%projectile%} is "Grenade": wait 2 seconds create a safe explosion of force 5 at projectile {grenade::%shot projectile%} is "Molotov" wait 2 seconds loop blocks in radius 5 of projectile: ignite loop-block loop entities in radius 5 of projectile: ignite loop-entity
  2. PoweredDragon

    skrypt na perły

    on damage: victim is player: damage cause is ender pearl: cancel event
  3. PoweredDragon

    Skrypt na granaty

    A nie lepiej normalny wybuch? command /granade: trigger: give slimeball named "&2Granat" to player on rightclick with slimeball: name of player's tool "&2Granat": shoot a snowball named "Granat" from player on shoot: name of projectile is "Granat": wait 2 seconds create a safe explosion of force 5 at projectile
  4. command /report [<text>] [<string>]: trigger: text-arg is set string-arg is set log "%player% zgłosił gracza %text-arg% z powodem: %string-arg%" to "zgloszenia.log" plik log pojawi się w folderze scripts
  5. set block under player to red wool loop 2 times: set block loop-number north from player to red wool set block loop-number east from player to red wool set block loop-number west from player to red wool set block loop-number south from player to red wool set block loop-number north 1 east from player to red wool set block loop-number north 1 west from player to red wool set block loop-number south 1 east from player to red wool set block loop-number south 1 west from player to red wool set block loop-number south 2 east from player to red wool set block loop-number south 2 west from player to red wool set block loop-number north 2 east from player to red wool set block loop-number north 2 west from player to red wool
  6. Ogólnie w twoim skrypcie nie widzę tego systemu obrony o którym wspominasz (chyba, że mówisz o domyślnej obronie w MC). Widzę natomiast damage-{jakaśtam zmienna na ogół większa od maksymalnych obrażeń} -> Przecież to zmniejsza zadawane obrażenia - max obr. na dobrą sprawę to diamentowy topór +sharpness V, a to jest jedynie ok. 12 obrażeń(12-30? Chcesz uleczyć przeciwnika? XD). Na co ty liczysz? Przede wszystkim: on damage: set {lasta::%attacker%} to 0 set {_cyferka5::%attacker%} to {@max} loop {@max} times: if lore of attacker's tool contains "&7Atak: &c%{_cyferka5::%attacker%}%": set damage to damage-{_cyferka5::%attacker%} set {lasta::%attacker%} to damage+{_cyferka5::%attacker%} stop set {_cyferka5::%attacker%} to {_cyferka5::%attacker%}-1 Chyba, że po prostu ja czegoś nie rozumiem, więc proszę o logiczne wyjaśnienie. Teraz po krótce 1. Skrypt powinien sam zaokrąglać; jeśli jednak tego nie robi, to może to być problem 2. Czekam 3. Choćby wyrzucenie tego (set {_cyf...}), co zrobiłem wyżej.
  7. command /warp [<text>]: trigger: arg is "stworz": set {_p} to player's account {_p} > 1000: block under player is gold block: set {warp::%player%} to location of player remove 1000 from player's account else: set {_p} to "%arg%" parsed as player {warp::%{_p}%} is set: teleport player to {warp::%{_p}%}
  8. Do Quacziego to się nie umywa, ale ogólnie spoko skrypt. Można by wiele rzeczy dodać <2/10 = 1/5 => 3/5 za skrypt :V>
  9. command /surowce: trigger: player is not in world "world": teleport player to spawn point of "world" wait 1 seconds execute player command "/rtp" send "&7Zostales przeleportowany do &3surowce"
  10. PoweredDragon

    Teleport

    command /ustawtp: trigger: targeted block is button: set {randomtp::%location of targeted block%} to true on rightclick on button: {randomtp::%location of targeted block%} is true: set {_x} to random integer between -50000 and 50000 set {_z} to random integer between -50000 and 50000 set {_y} to 60 loop 90 times: block at ({_x}, {_y}-1, {_z}) is solid: block at ({_x}, {_y}, {_z}) is air: teleport player to ({_x}, {_y}, {_z}) stop loop set {_y} to {_y}-1
  11. PoweredDragon

    Generator

    command /setBlockDiamondDrop: trigger: set {b::%location of targeted block%} to true on mine of diamond block: {b::%location of block%} is true: cancel event set {b::%location of block%} to false chance of 10%: drop 1 diamond ore at event-location stop chance of 20%: drop 1 diamond block at event location else: drop 1 cobblestone at event-location Komendą ustawiasz patrząc na ten blok :v
  12. command /tp [<number>] [<number>] [<number>]: trigger: arg 1 is not set: send "&aWpisz koordy!" stop arg 2 is not set: send "&aWpisz koordy!" stop set {_x} to arg 1 set {_z} to arg 2 set {_y} to arg 3 {_y} is not set: teleport player to ({_x}, 70, {_z}) else: teleport player to ({_x}, {_y}, {_z})
  13. set damage to damage+<dodatkowe obrazenia wyrazone iloscia serduszek> a poprawny warunek to: if name of player's tool is "&cMiecz Przeciw Zarazie" V:
  14. teleport player to spawn zamień na teleport player to spawn point of "world"
  15. Możesz losować zmienną z listy. Np. add {zmienna} to {zmienne::*} set {_r} to random integer between 1 and (size of {zmienne::*}) set {_randomowazmienna} to {zmienne::%{_r}%}
  16. normalne zmienne da się losować. Zawsze możesz spróbować tak: options: test_1: coś test_2: coś test_3: coś A to pod innym wydarzeniem. set {_r} to a random integer between 1 and 3 send {@test_%{_r}%}
  17. PoweredDragon

    Generator

    on mine of diamond block: cancel event set block to air chance of 10%: drop 1 diamond ore at event-location stop chance of 20%: drop 1 diamond block at event location else: drop 1 cobblestone at event-location
  18. PoweredDragon

    Ban cheatera

    on chat: {sprawdzany} is player: cancel event command /przyznajsie: trigger: execute console command "tempban %player% 7d" Przy czym zmienną {sprawdzany} zmieniasz na zmienną taką, jak masz w skrypcie na sprawdzanie Prosze o naj
  19. on join: set {eq::%player%} to player's serialized contents command /zwroc: trigger: restore inventory of player from {eq::%player%}
  20. on command "/warp gildie": player is in world "normalny swiat": set {eq::%player%} to player's serialized contents wait 10 ticks clear inventory of players on world change: future event-world is "normalny swiat": restore player's inventory from {eq::%player%} on pick up: player is in world "swiat gildii": cancel event
  21. Spróbuj: command /surowce: trigger: player is not in world "world": teleport player to spawn wait 1 seconds execute player command "/rtp" send "&7Zostales przeleportowany do &3surowce"
  22. PoweredDragon

    Skrypt na teleport

    command /ustawspawnsklep: permission: sklep.setspawn trigger: set {sklep::spawn} to location of player command /sklep: trigger: teleport player to {sklep::spawn}
  23. PoweredDragon

    Skrypt na teleport

    command /ustawspawnsklep: permission: sklep.setspawn trigger: set {sklep::spawn} at location of player command /sklep: trigger: teleport player to {sklep::spawn} Proszę o najlepszą odpowiedź
  24. Biorę udział
  25. Biorę udział w konkursie
×
×
  • Dodaj nową pozycję...