Minecraft Forums

Quote from laika923»

Really glad this one is back on business!

Thanks

Quote from Nikslg»

What about other legendaries?
Or is there a command to spawn giratina?

Via command blocks, and using the /pokemake command it can be done.

"/pokemake Giratina l:50" will spawn in a lvl 50 giratina, in altered forme.

Uploaded Pokecube Core 2.2.14

Changelog:

Uploaded Pokecube Revival 2.2.7

Changelog:

Uploaded Pokecube Core 2.2.15 and Pokecube Revival 2.2.8

Core and Revival changelog:

This should reduce the complexity of installing a bit, as it is 1 less mod to download.

either via the legendary spawner blocks, and meeting the correct requirements as shown here:

Or via a command block and the /pokemake <legendary name> command.

Uploaded Pokecube Core 2.2.16 and Pokecube Revival 2.2.9

Core changelog:

Revival changelog: (I suggest reading this)

Uploading Pokecube Revival 2.2.10

Changlog:

Uploaded Pokecube Mobs 1.1.10

Changelog:

Edit:

Uploaded Pokecube Core 2.2.17

Changelog:

Uploaded Pokecube Core 2.2.18 and Pokecube Revival 2.2.11

Core Changelog:

Revival Changelog:

Edit: here is a google document with some samples of the OC support:

https://docs.google.com/document/d/1RVT8zgpuZGH_xbTwVmhVFASSmJsDVIl4EPYGZG7yQ9w/edit?usp=sharing

Quote from smashbro596»

so what would the arguements be for pokemake?

The wiki really needs updating lol, unfortunately, I am not very good at making that sort of thing easily readable. Here are the make arguments:

• s - this makes it shiny
• sh - this makes it a shadow pokemob (cannot be tamed, should be extra agressive)
• l:<number> - makes it spawn at that lvl, if above evolution level, I think it will auto evolve.
• x:m/f - x:m makes it make, x:f makes it female, otherwise it is random based on pokemob.
• r:<number> g:<number> b:<number> - these set "colour" which I don't think is currently rendering, but once re-implemented will tinge the pokemob appropriately, defaults are around 255, cannot be higher than 255 or lower than 0.
• <playername> - assigns <name> as the owner. using @p would also make the selected player the owner.
• a:<abilityname> gives it that ability.
• m:<movename> - makes it start with that move, you can have up to 4 of these arguments, any more are ignored.
• v:x,y,z - spawns at these coordinates relative to the command block, so v:0,2,0 will spawn it 2 above the block.

If it helps, the source for the command is here: https://github.com/Thutmose/Pokecube/blob/1.10/Pokecube Core/src/main/java/pokecube/core/commands/MakeCommand.java

Edit: here is a sample useage:

/pokemake magikarp l:100 x:m s m:explosion v:0,2,0 Thutmose

would make a lvl 100, male, shiny magikarp with explosion, owned by Thutmose and spawned 2 above the command block.

/pokemake rattata

would make a wild, random gender, lvl 1 rattata on top of the command block

Quote from smashbro596»

thank you so much. um.... another question. shouldnt arceus be a flying mount? when i ride it it doesn't fly... also, judgement apparently isnt in the game as no tm spawns.

Arceus probably should be flying, I'll change that in the default database, btw, all of that sort of thing is technically changeable via configs.

I will check judgement, I don't think it was added in, it was one of the special case moves which I think I forgot to account for when I actually added arceus

Edit: this commit will now fix the arceus for the next version updated, I will probably see about fixing judgement before then as well. https://github.com/Thutmose/Pokecube/commit/5fd4130b908a5a31538d8270211cb4a5aaa8cd66

Edit: "Judgment" should work as just a normal type move, it doesn't change type yet, but it should work as a normal move.

Quote from smashbro596»

so just to be clear do flying mounts need fly? or are hms not required for flying, surfing, etc?

HMs Moves are not required, of the mob can fly around normally, it can fly with you on it, if the mob can swim normally, it can surf with you one it.

The actual rules for if it can fly are "is it flying type, or does it say fly="True" in database in the logic section"
for surf, it is "is it water type" though I should probably add a surf="True" section in database.
Dive only works if the dive="True" is set in the logic in the database.

I just commited the fix for judgment not selecting type properly, that will be fixed whenever I next upload updates, which will probably be after I find more bugs to fix.

to make the changes stay, change B:forceDatabase=true to false in the configs.

if you do that though, it will not refresh whenever I make a fix though.

I will check if lugia is set to able to dive, if not, I will set it, I will also see about making a boolean for surf, as I think only water types can atm, and lugia probably should be able to as well.

Check to see if setting them able to dive works, I may need to make a surf setting for that to work, I will probably make the surf setting tomorrow, and get a release out then.