Adramelke

October 2

The most likely culprit for this problem is most likely something to do with the text formatting for the item name? i've had this issue before and i'm not sure why this fixes it...

October 2

on armor change:
    player's helmet is golden helmet with name "&fMiner Helmet":
       apply night vision without particles to player for 9999 seconds
    player's helmet is golden helmet with name "&fMiner Helmet":
        remove night vision from the player's potion effects

command:
    permission: *
    trigger:
        give player 1 of golden helmet with name "&fMiner's Helmet"

October 2

set {variable} to floor({variable})

October 1

try the following.... i would expect errors because i'm not testing/debugging it before i send it i missed the important point that you want to limit crafting to only the list you're creating, sorry.

on load:
   set {_i1} to redstone named "&dRegen Spark" with no nbt
   set {_i2} to sugar named "&bSpeed Spark" with no nbt
   set {_i3} to 8 arrows named "&aMercury Arrow" with no nbt#posion arrow
   set {_i4} to scute named "&aPhotosynthesiser" with no nbt#damages by 2 in a 5 radius
   set {_item} to leather helmet named "&aOak Helmet"
   dye {_item} (144, 238, 144)
   set {_i5} to {_item}
   set {_item} to leather chestplate named "&aOak Chestplate"
   dye {_item} (144, 238, 144)
   set {_i6} to {_item}
   set {_item} to leather leggings named "&aOak Leggings"
   dye {_item} (144, 238, 144)
   set {_i7} to {_item}
   set {_item} to leather boots named "&aOak Boots"
   dye {_item} (144, 238, 144)
   set {_i8} to {_item}
   set {_i9} to totem of undying named "&6Midas' Jewel" with no nbt
   set {_i10} to ghast tear named "&7Large Iron Fragment" with no nbt
   set {_i11} to iron ingot named "&7Iron Ingot" with no nbt
   set {_i12} to blaze rod named "&6Strontium" with no nbt
   set {_i13} to nether bricks named "&5Obsidian Spark" with no nbt
   set {_i14} to lime dye named "&aDash Spark" with no nbt
   set {_i15} to magma cream named "&6Golden Spark" with no nbt
   set {_i16} to orange dye named "&6Midas Gel" with no nbt
   set {_i17} to ender pearl named "&5Enderpearl" with no nbt
   set {_i18} to gray dye named "&fArrow &7Storm &fSpark" with no nbt
   set {_i19} to iron boots named "&7Steel Boots"
   set {_i20} to iron leggings named "&7Steel Leggings"
   set {_i21} to iron chestplate named "&7Steel Chestplate"
   set {_i22} to iron helmet named "&7Steel Helmet"
   set {_1item} to iron helmet named "&8Enhanced Steel Helmet"
   enchant {_1item} with protection 1
   set {_i23} to {_1item}
   set {_2item} to iron leggings named "&8Enhanced Steel Leggings"
   enchant {_2item} with protection 1
   set {_i24} to {_2item}
   set {_3item} to iron chestplate named "&8Enhanced Steel Chestplate"
   enchant {_3item} with protection 1
   set {_i25} to {_3item}
   set {_4item} to iron boots named "&8Enchanced Steel Boots"
   enchant {_4item} with protection 1
   set {_i26} to {_4item}
   set {_i27} to crafting table named "&6Crafting Table"
   set {_i28} to 4 oak planks named "&6Oak Planks"
   set {_i29} to 4 oak stairs named "&6Oak Stairs"
       loop 29 times:
           {items::*} does not contain {_i%loop-value%}:
               add {_i%loop-value%} to {items::*}
   register new shaped recipe for {_i1} using spruce leaves, oak Wood, spruce leaves, oak Wood, purple dye, oak Wood, spruce leaves and oak Wood, spruce leaves with id "regen_spark" in group "MIDAS BOX"
   register new shaped recipe for {_i2} using spruce leaves, oak Wood, spruce leaves, oak Wood, light blue dye, oak Wood, spruce leaves and oak Wood, spruce leaves with id "speed_spark" in group "MIDAS BOX"
   register new shaped recipe for {_i3} using arrow, arrow, arrow, arrow, firework star, arrow, arrow, arrow and arrow with id "mercury_arrow" in group "MIDAS BOX"
   register new shaped recipe for {_i4} using spruce leaves, ghast tear, spruce leaves, spruce leaves, coal, spruce leaves, andesite, andesite and andesite with id "photosynthesiser" in group "MIDAS BOX"
   register new shaped recipe for {_i5} using spruce leaves, spruce leaves, spruce leaves, oak Wood, air, oak Wood, air, air and air with id "oak_helmet" in group "MIDAS BOX"
   register new shaped recipe for {_i6} using spruce leaves, air, spruce leaves, oak Wood, oak Wood, oak Wood, spruce leaves, oak Wood and spruce leaves with id "oak_chestplate" in group "MIDAS BOX"
   register new shaped recipe for {_i7} using oak Wood, oak Wood, oak Wood, spruce leaves, air, spruce leaves, spruce leaves, air and spruce leaves with id "oak_leggings" in group "MIDAS BOX"
   register new shaped recipe for {_i8} using air, air, air, oak Wood, air, oak Wood, spruce leaves, air and spruce leaves with id "oak_boots" in group "MIDAS BOX"
   register new shaped recipe for {_i9} using black dye, yellow dye, black dye, yellow dye, diamond, yellow dye, black dye, yellow dye and black dye with id "midas_jewel" in group "MIDAS BOX"
   register new shaped recipe for {_i10} using iron nugget, iron nugget, iron nugget, iron nugget, air, iron nugget, iron nugget, iron nugget and iron nugget with id "large_iron_fragment" in group "MIDAS BOX"
   register new shaped recipe for {_i11} using ghast tear, ghast tear, ghast tear, ghast tear, air, ghast tear, ghast tear, ghast tear, and ghast tear with id "iron_ingot" in group "MIDAS BOX"
   register new shaped recipe for {_i12} using andesite, flint, andesite, flint, light blue dye, flint, andesite, flint and andesite with id "strontium" in group "MIDAS BOX"
   register new shaped recipe for {_i13} using gunpowder, gunpowder, gunpowder, gunpowder, black dye, gunpowder, gunpowder, gunpowder, and gunpowder with id "obsidian_spark" in group "MIDAS BOX"
   register new shaped recipe for {_i14} using air, light blue dye, air, ghast tear, slimeball, ghast tear, air, iron nugget and air with id "dash_spark" in group "MIDAS BOX"
   register new shaped recipe for {_i15} using glowstone, air, glowstone, glowstone, honeycomb, glowstone, air, glowstone and air with id "golden_spark" in group "MIDAS BOX"
   register new shaped recipe for {_i16} using glowstone, glowstone, glowstone, glowstone, yellow dye, glowstone, glowstone, glowstone and glowstone with id "midas_gel" in group "MIDAS BOX"
   register new shaped recipe for {_i17} using air, air, air, air, raw copper, air, air, dragon breath and air with id "enderpearl" in group "MIDAS BOX"
   register new shaped recipe for {_i18} using arrow, arrow, arrow, arrow, andesite, arrow, arrow, arrow and arrow with id "arrow_storm_spark" in group "MIDAS BOX"
   register new shaped recipe for {_i19} using air, air, air, iron ingot, air, iron ingot, iron ingot, sugar and iron ingot with id "steel_boots" in group "MIDAS BOX"
   register new shaped recipe for {_i20} using iron ingot, iron ingot, iron ingot, iron ingot, lime dye, iron ingot, iron ingot, air and iron ingot with id "steel_leggings" in group "MIDAS BOX"
   register new shaped recipe for {_i21} using iron ingot, air, iron ingot, iron ingot, lapis, iron ingot, iron ingot, iron ingot and iron ingot with id "steel_chestplate" in group "MIDAS BOX"
   register new shaped recipe for {_i22} using iron ingot, iron ingot, iron ingot, iron ingot, redstone, iron ingot, air, air and air with id "steel_helmet" in group "MIDAS BOX"
   register new shapeless recipe for {_i23} using iron helmet and iron helmet with id "enhanced_steel_helmet" in group "MIDAS BOX"
   register new shapeless recipe for {_i24} using iron leggings and iron leggings with id "enhanced_steel_leggings" in group "MIDAS BOX"
   register new shapeless recipe for {_i25} using iron chestplate and iron chestplate with id "enhanced_steel_chestplate" in group "MIDAS BOX"
   register new shapeless recipe for {_i26} using iron boots and iron boots with id "enhanced_steel_boots" in group "MIDAS BOX"
   register new shapeless recipe for {_i27} using oak plank, oak plank, oak plank and oak plank with id "crafttable" in group "MIDAS BOX"
   register new shapeless recipe for {_i28} using oak wood with id "oakplank" in group "MIDAS BOX"
   register new shaped recipe for {_i29} using air, air, oak plank, air, oak plank, oak plank, oak plank, oak plank and oak plank with id "oakstair" in group "MIDAS BOX"

on craft:
{items::*} does not contain output: #<--- i'm not sure what expression to use for the crafting output
cancel event

October 1

what are the conditions for the item to drop... and do you use a plugin for custom player heads?

on break:
chance of 0.01:
<stuff to give player head /give command, plugin command, etc>

October 1

what is this supposed to do then? it shows you that you have the recipie correct, but prevents crafting....

on craft:
  if item is {_i1}:
    stop

October 1

when you put the items into the crafting table, does the output show anything?

October 1

any errors? or what's happening that is not supposed to or happening that isn't supposed to?

https://dev.bukkit.org/projects/skript/pages/variables-explanation
"

Nest Variables

Nest variables are when you put the value of an expression inside the variable name. An example could be :

{variable.%player%}

When Skript reads the variable, it will replace %player% with the name of the player. If you were to look in the variables.csv file (You should probably never look in there just in case something gets messed up, but for the sake of the example, I'm going to tell you what you might find) you would see

{variable.Demon_Penguin}

Skript would fill in the name of the player. In this case it was Demon_Penguin. This will essentially make a separate variable per player, which is used in most scripts. You can also put the value of another variable inside a variable name like this:

{favorite.%{color}%}

If {color} was set to green, then you would see {favorite.green}.

There may also be situations where you need multiple expressions to refer to the same player. For example, in a loop, you may need to refer to loop-player to get the correct player for a variable.

Local Variables

Local variables are used when you only want to use a variable for a little bit and don't want/need to save it. There can also exist multiple local variables of the same name at the same time. This is useful for things like log in events. While the code is executing for one player, another player may log in and need their own variable. In order to tell Skript you want this variable to be a local variable all you need to do is prefix the variable name with an _ Looks like this {_local} (Note that you may see it used as '*' in older posts, however in newer versions of Skript the underscore _ is used)"

this is what i was talking about for the variables...

October 1

{_i%{_number}%}

also these are local variables that aren't set before they're used...

October 1

what is it doing that it shouldn't be or, conversely, not doing that it should?

i asked a couple of times, what is this script meant to do?.... no one can help you until you answer that question....

October 1

3 hours ago, CrimsonDefender said:

even tho i hate daily time limit you just gotta space out when you code and stuff like every few hours work on server for like 1 through 2 hours thats how i dont use up daily time limit

this still doesn't increase the limit on the amount of time you can spend working... and it just isn't feasible to have to start and stop a server for debugging...

October 1

replace all "[" and "]" with "" in {_prefix}

       replace all "[" and "]" with "" in {_suffix}
       if length of {_suffix} is greater than 2:
           set score " %{_prefix}% &8+ %{_suffix}%" in sidebar of loop-player to 8
       else:
           set score " %{_prefix}%" in sidebar of loop-player to 8

{_variable} is a local variable that has to be set in the same even/trigger before it can be used?? either change it to a constant one {variable} or reset the variable before using it (set {_variable} to "thing":)

function buy(p: player, i: integer, m: string, it: itemtype):
	set {_uuid} to uuid of {_p}
	if {balance::%{_uuid}%} >= {_i}:
		remove {_i} from {balance::%{_uuid}%}
		give {_p} {_it} named {_m}
		send "{@msg}Bought 1 %{_m}% &3for $%{_i}%" to {_p}
	else:
		send "{@msg}Too poor" to {_p}

October 1

alot of indefinites here... what is this mystery command the "one player will auto execute"?? you basically just want to add the 2 players to a list and teleport one to the other? then remove them from the list? is the list even remotely neccessary?

October 1

what is it doing that it shouldn't be or, conversely, not doing that it should?

on right click:
   if player's tool is diamond sword:
       if player's inventory contains book with lore "&7Poison":    <- check for book
           add "&7Poison" to lore of player's tool                               <-add poison lore to the sword
           If lore of the player's tool contains "&7Poison":                <- if the sword's lore is poison
               remove "&7Poison" from the lore of player's tool          <- remove the lore

you're doing something and immediately undoing it.... i'm not sure what the final result is supposed to be... is it supposed to remove poison lore from the book, poison status effect from player, or from the sword you just put it on? i'm not trying to be critical... mostly.... i'm trying to understand what the end result is for this event

October 1

on death of player:
force event-player respawn
wait 1 tick
set {_randomNumber} to a random integer between 1 and 3 # Customize the range as needed
{_randomNumber} is 1:
give event-player iron sword
give event-player iron helmet
give event-player iron chestplate
give event-player iron leggings
give event-player iron boots
else if {_randomNumber} is 2:
give event-player diamond sword
give event-player diamond helmet
give event-player diamond chestplate
give event-player diamond leggings
give event-player diamond boots
else if {_randomNumber} is 3:
give event-player stone sword
give event-player leather helmet
give event-player leather chestplate
give event-player leather leggings
give event-player chainmail boots

October 1

what add-ons are you using in addition to skript?

October 1

can i ask what this command is meant to do?

command: /MuffenBox
trigger:
execute console command "/mv spawn"

command: /MuffenBox
trigger:
execute player command "/mv spawn"

October 1

how was the item made? for instance, was it made given to the player using /give?, is it an item that was put on an anvil and name changed?

the first thing i would try is using a script to generate the item, simple command give player item name item yada yada....

are there any errors given when this is loaded?

October 1

just open a chest to the player.... save the contents of what they put into the chest as a variable list.... close the chest inventory... open chest to player add contents of variable list to chest...

October 1

on join:
{kills.%player's uuid%} is not set:
set {kills.%player's uuid%} to 0
{deaths.%player's uuid%} is not set:
set {deaths.%player's uuid%} to 0

every 1 second:
    loop all players:
      set title of loop-player's scoreboard to "&6VoldysSMP"
      set line 1 of loop-player's scoreboard to "&7&l» &6Smrti: &7%{deaths.%loop-player's uuid%}%"
        set line 2 of loop-player's scoreboard to "&7&l» &6Zabití: &7%{kills.%loop-player's uuid%}%"
        set line 3 of loop-player's scoreboard to "&6Statistiky"
        set line 4 of loop-player's scoreboard to ""
        set line 5 of loop-player's scoreboard to " &8» &fHráč: &6%loop-player%"
      set line 6 of loop-player's scoreboard to "&6Info"
      wait 1 second

on death:
attacker is a player:
add 1 to {kills.%attacker's uuid%}

on death:
victim is a player:
add 1 to {deaths.%victim's uuid%}

made some corrections, try it and see what it does.... also make sure to add some errors that are returned when you reload the script.

September 30

I've kind of skimmed this thread a little. so maybe some of what i have to say has already been addressed.

it's hard to develop a server if you're doing the coding yourself, with only 8 hours a day the server can be active, particularly to do debug. players don't always play at the same time, i have players that come in at pretty predictable times of day several that haven't ever met after playing on the server for several weeks, because of it. my servers are not for profit, and i'm still being exposed to ads, spammers, hackers, and well everything minehut has failed to fix in the past, such as... failing to warn the community of major changes before implementing them... that's just professionally embarrassing to be honest, but i don't own minehut, so... anyway... so i assume that with this policy change we'll be seeing far less ads, bots, spammers, hackers etc....

i mean, it's not like bots can just bruteforce a simple list of server names(the names have strict requirements remember) and essentially lock any server that isn't whitelisted or paid by joining every possible combination of server names until they find one open and then just sitting there...every day when the reset happens... that could never ever happen...

oh, just one last question... can anyone say they play on any server that has a restricted number of hours it can be open?

December 24, 2020

December 24, 2020

Go to : https://minehut.com/dashboard/

Find the server you're trying to join and turn it on.

You can either add the server in minecraft, usually <name of server>.minehut.gg. or

go to minehut.com in minecraft and type the command "/join <name of server>"

December 24, 2020

What shop plugin and what permissions manager are you using?

December 24, 2020

I'm wondering what files are need to be correctly uploaded to a server. I'd like to know what files it looks for in the compressed file to accept the world files? I've tried to upload 2 different compressed(.zip) "world" files and one was refused immediately, and the other gets to 99-100% then just throws an error with no code or reason.

Profiles

Forums

Gallery

Blogs

Events

Store

Downloads

Posts posted by Adramelke

Nest Variables

Local Variables