I think a new facesprite would be cool instead of "recycling" the front sprite.
I hope I will find time to fix the time and create a backsprite.. but feel free to do it yourself, currently Im pretty slow again.

No worries, let's use these ones as a placeholder until someone makes new face sprites for Jemuar from scratch.

I finished off the face sprites for a few Catch Challenger creatures, adding another 6 to our total!

Edit:
And Nudimind:

Which finishes off another line, bringing it to 63!

EDIT 2:

And Trapsnap and Sapsnap faces, bringing it to 65!

EDIT 3:

EDIT 4:
Budaye, which I've made a prevolution of Bamboon (as well as Frondly, which I have a front sprite coming for soon).

EDIT 5:
Agnidon

Last edited by Sanglorian (23 Oct 2016 09:08)

Was gonna hold these back, but thought what the heck:

Gets us up to 100, by my count!

Last edited by Sanglorian (30 Oct 2016 12:14)

Thanks tamashi - and my bad on Propellercat, I've fixed that now.

Amazing!! You must be working your tail off, but that's how games get finished!

Wow, 100! now we need to get them into the game! Thanks so much for your help Sanglorian - it means a lot to me.

Amazing!! You must be working your tail off, but that's how games get finished!

Wow, 100! now we need to get them into the game! Thanks so much for your help Sanglorian - it means a lot to me.

Thank you for the kind words - I really appreciate it!

Thanks to everyone who participated.

Awesome work to everyone who helped in this sprint! To get these in the game we just need the following now:

• A file entry like this one in resources/db/monster for each monster.
• The monster sprite images put in resources/gfx/sprites/battle.
• An entry in resources/db/locale/en_US.json with each monster's name, description, etc. located here.
• Optionally the monsters put in an encounter file in resources/db/encounter like this one, so they can be encountered in the game.

Once this is done, we'll be able to encounter all of these creatures in Tuxemon.

Thanks ShadowApex. Is their a guide on what range of stats and stat mods represents what? For example, it would be useful to have a guide like:

Speed of 10 represents extremely slow, Speed of 40 represents average, Speed of 70 represents extremely fast. 1/10 should have Speed 10-20, 2/10 Speed 20-30, 4/10 Speed 30-50, 2/10 Speed 50-60 and 1/10 Speed 60-70.

Speed mod should be 1, unless Speed is below 30, in which case it should be 0.9, or above 50, in which case it should be 1.1.

Overall, a monster's average stat should be 40 and their average stat mod should be 1.

(Or whatever suits the rules of the game).

Last edited by Sanglorian (3 Nov 2016 06:06)

I think, for a lot of those things, it is relative. If the fastest Tuxemon in the game has a Speed of 100, then 10 would be incredibly slow and 70 would be above average.

These are actually the kinds of things that monster creators would be deciding as they make the monsters

As a note, the values can be so large as to be unwieldy (talking in the trillions), so don't feel like you have to keep the numbers in the tens. Making the scale too large will make UI stuff hard though. It's just good to leave room for Tuxemon to gain stats as they level and to have some granularity. Perhaps have a design (not code) limitation of 999 ?

I think the monster creators need to know what the values represent before they can decide which values to give the monsters. Once we know whether the fastest monster in the game has a Speed of 100, then we can decide if a particular monster is the fastest in the game and - if it is - give it a Speed of 100.

Last edited by Sanglorian (4 Nov 2016 22:37)

I think, for a lot of those things, it is relative. If the fastest Tuxemon in the game has a Speed of 100, then 10 would be incredibly slow and 70 would be above average.

These are actually the kinds of things that monster creators would be deciding as they make the monsters

As a note, the values can be so large as to be unwieldy (talking in the trillions), so don't feel like you have to keep the numbers in the tens. Making the scale too large will make UI stuff hard though. It's just good to leave room for Tuxemon to gain stats as they level and to have some granularity. Perhaps have a design (not code) limitation of 999 ?

I think the monster creators need to know what the values represent before they can decide which values to give the monsters. Once we know whether the fastest monster in the game has a Speed of 100, then we can decide if a particular monster is the fastest in the game and - if it is - give it a Speed of 100.

The fastest monster in the game will, by definition, be the monster with the highest Speed attribute. It's all relative. If you decide that Cardinale is going to be the fastest Tuxemon in the game and give it a base Speed of 99, then I come by and make a two-headed falcon Tuxemon called Pairagrin with a base Speed of 106, Pairagrin is the fastest now.

The developers do need to document what each attribute actually does (Speed determines which Tuxemon goes first in combat, higher goes first), but after that it's all up to content creators. Since ShadowApex thinks 100 is the highest base value we'll use, assume that 100 is really high and just pick values in line with the Tuxemon's concept. I imagine Nudiflot would be pretty slow, but maybe have higher than average hp.

I think the monster creators need to know what the values represent before they can decide which values to give the monsters. Once we know whether the fastest monster in the game has a Speed of 100, then we can decide if a particular monster is the fastest in the game and - if it is - give it a Speed of 100.

The monster attributes are definitely going to take some time to tweak and balance. Coming up with appropriate stats is going to be an ongoing issue that we'll need to refine with time. At this early stage with monster stats, we can be pretty relaxed on the initial stats of each monster and tweak things as we go. For starting stats, I would suggest trying to keep the numbers low (below 100).

In order to help people put together monsters sprites, stats, etc. I created a new Tuxemon web project that will help people more easily put in all these monster details (stats, name, description, etc.). This project makes it a little easier for people who don't want to write monster stats directly in JSON format, and it will also let us put sensible defaults and restrictions on stats to help people make new monsters. The project can be found on GitHub here: https://github.com/Tuxemon/Tuxemon-MonsterMaker

Right now it isn't ready to be put on the website yet, but when it is people can use it to create and submit new monsters. Here's a quick screenshot of what it looks like right now in its basic form:

https://raw.githubusercontent.com/Tuxem … rmaker.png

Sorry ShadowApex, I somehow missed this post the first time around.

MonsterMaker looks good! Funnily enough I've been toying with my own tool to make monster making easier - a spreadsheet with formulas that would make calculations automatically, and that could then be converted automatically to a JSON file.

If the stats are going to change, possibly dramatically, can I suggest an alternative to picking actual values?

If we just got people to describe stats in qualitative terms, we could generate preliminary values from that, and then tweak the whole set at once, instead of tweaking monster by monster. Once we know where we want the numbers to be, we could go in and manually adjust the values.

For example,

I create Lambert, and assign it Attack: Good, Defence: Great, HP: Good, Special Attack: Terrible, Special Defence: Good and Speed: Bad.

The formula (which aims for an average of 40, and a minimum of ~10 and a max of ~72) assigns it Attack: 48, Defence: 60, HP: 48, Special Attack: 12, Special Defence: 48 and Speed: 24.

This averages to 40, with steps of 12 points: Terrible: 12, Bad: 24, Average: 36, Good: 48, Great: 60.

On the other hand, I create Rockitten (for example) with Attack: Great, Defence: Great, and all other values Terrible.

This results in an Attack of 72, a Defence of 72, and all others 24. (Again, for an average of 40).

If in the future we decided that the gap between stats was too great, and we wanted stats between 25 and 55, we could trivially change the formula without needing to redo every monster.

You can see an implementation of this idea (and you can fiddle around with it), here: https://docs.google.com/spreadsheets/d/ … sp=sharing

Well, it doesn't need to be a developer - but there should be a general agreement in the community. I'm happy for everyone to use my system, or I'm happy to use someone else's system, as long as there's a system.

For example, the D&D point buy system that you link to assumes that higher scores are disproportionately better than lower scores - that +3 Strength and +1 Intelligence is better than +2 Strength and +2 Intelligence (increasing returns).

This is quite possibly the case for Attack and Special Attack, because you can focus on one and just always techniques associated with your better stat.

But the other possibility is that higher scores are disproportionately worse than lower scores - that +2 Strength and +2 Intelligence is better than +3 Strength and +1 Intelligence.

This is quite possibly the case for Speed, because once you're faster than your opponent, it doesn't matter (usually) how much faster you are.

Yeah, there's an interesting discussion to be had around whether some tuxemon should be better than others. For example, should tuxemon get stronger as they evolve, or should that just open up new options? As you say, legendaries and fossils are other ones that might warrant higher stats.

this discussion about the stats could be moved into a new threat maybe?

Botbot is now complete.

Sharpfin needs back and face sprites.

Monkeybot is now complete.

Fishbot is now complete.

Birdbot complete.

Bigfin complete (based on tamashihoshi's Dollfin face sprites).

From josepharaoh99's initial sprite. Still needs back and face sprites.

Last edited by Sanglorian (20 Nov 2016 01:03)