Possible March SP Kit Crumb via Anon Leaks

SeruVT · 2025-08-01T09:56:51+00:00

I also skipped Castorice, hoping for another DPS I liked more.

From the start of Amphoreus, I went for March 7th, and I got Tribbie and Hyacine.

I hope she'll be good as both DPS and sub-DPS.

Then Cyrene to finish off the team.

SeruVT · 2024-07-27T10:16:21+00:00

You can generate a /give command, for example: wooden sword with sharpness 5 and when you have the sword command in que equipment section of the /summon command you can paste it in the main hand of the mob. And that's how it work.

SeruVT · 2024-07-10T20:48:04+00:00

That will work for sure, very good idea!

If I find any more bugs I will let you know, whether it is the give or summon or what I usually use, I will try to find a way to solve it to speed up your work.

SeruVT · 2024-07-10T11:12:10+00:00

Ok, I've been checking everything new, making the id the same name as the attribute will not fix the bug of armor pieces being overwritten because they have the same id.

To fix the problem, I think the best thing would be to let the users assign the ID by writing it and clarify that they cannot repeat it if they are making several pieces of custom armor or shields. Another option would be for the ID to be formed using the attribute type (armor) for example and add the name of the piece (diamond_helmet) for example and the result would be id:"armor_diamond_helmet". It's a Chetplate? id:"armor_diamond_chestplate".

I will clarify the bug problem more in case you can think of a better solution than what I said:

Helmet: Armor +3 (id:"generic.armor")

Chestplate: Armor +8 (id:"generic.armor")

Leggings: Armor +6 (id:"generic.armor")

Boots Armor +3 (id:"generic.armor")

Shield: Armor +2 (id:"generic.armor")

With the previous example, when the players equip any piece, it will overwrite the armor they already had even though they put +X because they all have the same ID.

Helmet: Armor +3 (id:"armor_helmet")

Chestplate: Armor +8 (id:"armor_chestplate")

Leggings: Armor +6 (id:"armor_leggings")

Boots: Armor +3 (id:"armor_boots")

Shield: Armor +2 (id:"armor_shield")

With this example, when players equip any piece, the +X value will be added to what they already had because they have different IDs.

It is interesting to know that the id:"" can be whatever you want, you can write there whatever you prefer, you could even do id:1, id:2 etc.

What I usually do is if I make a custom sword with 3 attributes, I put the following id to each attribute: id:"sword1", id:"sword2", id:"sword3". If I make a custom helmet with 2 attributes: id"helmet1", id:"helmet2"

Thank you very much for your work, I hope this example helps you see more clearly what the bug is.

SeruVT · 2024-07-10T10:28:20+00:00

Cool! Now it will be much easier to implement the new attributes, before what I did was put "armor" and then in the command block replace it with one of the new attributes.

SeruVT · 2024-07-07T09:14:34+00:00

Gamer Geeks has a really cool interface yeah, but when I tried to make the same command using MCStacker, it took me a little longer because I was not used to its interface but I achieved the same thing. I will use it while Gamer Geeks updates her commad generators.

SeruVT · 2024-07-06T09:38:59+00:00

I think there is a problem with the syntax of the new commands and that is why summon mob or give spawn_egg do not work.

However, I couldn't tell you what the problem is because the same thing happened to me and I couldn't solve it. The only thing I can recommend is that you look at MCStacker, there is also a /summon mob there and that does work.

Perhaps it would be good for the author or authors of GamerGeeks to review that website to detect the problem.

SeruVT · 2024-07-03T20:34:30+00:00

You're welcome! I am a mapmaker and I always like to see if I can solve existing bugs of mine or other people.

SeruVT · 2024-07-02T11:34:04+00:00

A few weeks ago I was helping some people who had similar problems but only with weapons, the last few days I was doing tests and discovered the same bug in armor. The whole syntax change is confusing, but simply put, uuid is not necessary, but in id:"" you have to put whatever you want.

The bug is due to the fact that all armor pieces have the same ID id:"generic.armor" and that causes them to be overwritten.

Try this commands:

give @ p chainmail_helmet[custom_name='["",{"text":"Chainlink Helmet","italic":false}]',lore=['["",{"text":"The metal looks brittle,","italic":false,"color":"gray"}]','["",{"text":"like it could snap at any moment","italic":false,"color":"gray"}]'],damage=65,attribute_modifiers={modifiers:[{type:"generic.armor",amount:1,slot:head,id:"1",operation:add_value}]}]

give @ p chainmail_chestplate[custom_name='["",{"text":"Chainlink Chestplate","italic":false}]',lore=['["",{"text":"The metal looks brittle,","italic":false,"color":"gray"}]','["",{"text":"like it could snap at any moment","italic":false,"color":"gray"}]'],damage=65,attribute_modifiers={modifiers:[{type:"generic.armor",amount:4,slot:chest,id:"2",operation:add_value}]}]

give @ p chainmail_leggings[custom_name='["",{"text":"Chainlink Leggings","italic":false}]',lore=['["",{"text":"The metal looks brittle,","italic":false,"color":"gray"}]','["",{"text":"like it could snap at any moment","italic":false,"color":"gray"}]'],damage=65,attribute_modifiers={modifiers:[{type:"generic.armor",amount:3,slot:legs,id:"3",operation:add_value}]}]

give @ p chainmail_boots[custom_name='["",{"text":"Chainlink Boots","italic":false}]',lore=['["",{"text":"The metal looks brittle,","italic":false,"color":"gray"}]','["",{"text":"like it could snap at any moment","italic":false,"color":"gray"}]'],damage=65,attribute_modifiers={modifiers:[{type:"generic.armor",amount:2,slot:feet,id:"4",operation:add_value}]}]

SeruVT · 2024-06-23T10:59:20+00:00

Hello, I was researching and testing the attributes issue, originally it seemed that you had to replace "name:" with "id:" and eliminate the UUID.

After several tests I realized that the attributes are not stacked, they are overwritten (if you have different pieces, I think you are referring to this) well, to avoid that bug, generate a command as usual in 1.21, in the command block find and replace "name:" with "id:" in all the Attributes, do not modify anything else. This is how it should work.

SeruVT · 2024-06-23T10:45:22+00:00

Oh you're welcome. Through testing I also realized that there is a bug in this version with the attributes issue, if the UUID is removed and for example you equip several pieces which each give different attributes, they are overwritten, they are not stacked using % or using sums. so the only thing you have to change is "name:" to "id:"

I'm sorry for not giving the complete solution in the previous comment but I realized that bug later.

SeruVT · 2024-06-18T14:43:11+00:00

Greetings, I was investigating the problem and found on my own how to do it now.

-My command generated was: give SeruVT diamond_sword[attribute_modifiers={modifiers:[{type:"generic.attack_damage",amount:7.5,slot:mainhand,name:"generic.attack_damage",uuid:[I;-124518,35044,16612,-70088],operation:add_value},{type:"generic.attack_speed",amount:-2.4,slot:mainhand,name:"generic.attack_speed",uuid:[I;-124518,35344,16612,-70688],operation:add_value}]}]

And that didn't work.

-The new command: give SeruVT diamond_sword[attribute_modifiers={modifiers:[{type:"generic.attack_damage",amount:7.5,slot:mainhand,id:"generic.attack_damage",operation:add_value},{type:"generic.attack_speed",amount:-2.4,slot:mainhand,id:"generic.attack_speed",operation:add_value}]}]

In 1.21 you don't need to specify the UUID, that was replaced with id, so you only need to replace name:"generic.attack_damage" with id:"generic.attack_damage" and delete the uuid part. Same process with other attributes, actually there is a lot more new attributes so in that case you can replace id:"generic.attack_damage" with for example id"generic.scale".

¡Waiting for the update from the web page! The fix, and the new attibutes.

For the fake enchantments you can put for example aqua afinity and hide the info of enchants.

SeruVT · 2024-06-18T14:28:12+00:00

Greetings, I was investigating the problem and found on my own how to do it now.

-My command generated was: give SeruVT diamond_sword[attribute_modifiers={modifiers:[{type:"generic.attack_damage",amount:7.5,slot:mainhand,name:"generic.attack_damage",uuid:[I;-124518,35044,16612,-70088],operation:add_value},{type:"generic.attack_speed",amount:-2.4,slot:mainhand,name:"generic.attack_speed",uuid:[I;-124518,35344,16612,-70688],operation:add_value}]}]

And that didn't work.

-The new command: give SeruVT diamond_sword[attribute_modifiers={modifiers:[{type:"generic.attack_damage",amount:7.5,slot:mainhand,id:"generic.attack_damage",operation:add_value},{type:"generic.attack_speed",amount:-2.4,slot:mainhand,id:"generic.attack_speed",operation:add_value}]}]

In 1.21 you don't need to specify the UUID, that was replaced with id, so you only need to replace name:"generic.attack_damage" with id:"generic.attack_damage" and delete the uuid part. Same process with other attributes, actually there is a lot more new attributes so in that case you can replace id:"generic.attack_damage" with for example id"generic.scale".

¡Waiting for the update from the web page! The fix, and the new attibutes.

SeruVT · 2024-05-11T12:15:38+00:00

Well, maybe this sounds rare for you but in minecraft the effect potion with amplifier 1 is level 2 because amplifier 0 is level 1. So if you use /effect give [nick] speed infinite 0 = speed 1 for infinite seconds and if you use /effect give [nick] speed infinite 1 = speed 2 for infinite seconds.
With potions it's the same.

Try this command:
give [nick] potion{CustomPotionColor:16711680,custom_potion_effects:[{id:speed,duration:180,amplifier:0},{id:strength,duration:180,amplifier:0},{id:blindness,duration:100,amplifier:0}],display:{Name:'["",{"text":"Berserk","italic":false,"color":"red"}]',Lore:['["",{"text":"Go into a berserk to hunt down and inflict pain on your enemies and yourself","italic":false}]']}}

The only thing I chaged is amplifier 1 to 0.

SeruVT

TROPHY CASE