These I created myself with pixel art in Photoshop, based on the Mystery Dungeon sprites. Due to the default nature of Minecraft, I am limited to 16x16 pixel spaces.
Alright, bear with me. You will need a little imagination to see what is happening so far with this mod.
Essentially, what I hope to code into my Minecraft mod is that when your tamed Eeveelution "dies," it drops an "item" of itself (the bottom one). To heal it, you "craft" it with some healing crafting recipe to get the top.
Then to bring them back, you essentially throw the healed item (top) to summon them and it should automatically assign ownership to the one who threw it.
This does a number of things I like. Your Pokemon is destroyable and you can lose them if you die and are not careful. It still creates some limit to the number you can carry since they will not stack.
It also makes trading, if desired, easier to do.
The coding for all this should work pretty smoothly with the exception of one part. I am not sure at this point how to code in taming assignment to the Pokemon once it is brought out from its thrown item.
I will also need to work out disabling this item from being thrown by any non-player devices (ex: dispensers).
For now, I will probably work with Eevee, which I intend to make the only wild Pokemon of these bunch. And of course, toss in some evolution items (likely require crafting). (ex: Mossy Rock, Lunar Ribbon, ect.)
Much of my coding for my mod I want to stick mostly with combining other bits of the official vanilla coding and avoid doing any major original coding changes. I also want to avoid as much as possible getting other mod's coding involved.
Since I see the above problems caused Tekkit difficult to scale, especially after the 1.3 coding overhaul. And I believe this was rather fatal to seagoingmanatee's Pokemobs mod, which I also saw he is just starting over from scratch since that release.
If you are interested, I keep my thoughts, notes and ideas on this journal now, when I am actively working on the mod: [link]
I will try and keep that around when I am not actively working on it.
As a small warning, a lot of it is in terms of my own programmer thought process and might not make the best sense, even to other programmers.