This guide has not yet been updated for the current season. Please keep this in mind while reading. You can see the most recently updated guides on the browse guides page
Vote received! Would you like to let the author know their guide helped you and leave them a message?
Terra is a great team fighter, capable of good cc, heal, and peel. she has a global ultimate that can have a big effect in fights. However, Terra is a victim of a common misconception. People like to build some dps on guardians in order to have peel and burst, which is great, some guardians thrive off of this, Ymir with
Shoes of the Magi and
Soul Reaver is devastating. but
Terra has an issue. her scaling is GARBAGE. her 2,
Crushing Earth, has 35% scaling. to put this into perspective, if you build for 1000 magical power, the kind of build that
Scylla 1 hits people with, you won't even triple the damage of the base smash damage. you will get an extra 350 damage. that's it. you're sacrificing all the beautiful tankiness that makes
Terra such a good team fighter in exchange for 350 damage, which even on the squishiest of mages will probably be about 290-320. that is dumb.
Terra has a really cool kit, capable of some damage, awesome healing, and strong fighting. But, she has cons as well.
SMITEFire is the place to find the perfect build guide to take your game to the next level. Learn how to play a new god, or fine tune your favorite SMITE gods’s build and strategy.
Copyright © 2019 SMITEFire | All Rights Reserved
The guide isn't great, but it's not bad either. a bit on the short side, but still worth the read. I'm more of an ADC player, so knowing some info on Terra could make me a better team player when it comes to her point of view.
If CC is such a big deal to avoid early game, maybe
You only have two items listed in the 'building' introduction. I know you're still in the middle of adding new content, but if I was an average player looking for a good guide, this one might not be as informative as others I could have checked out.
Just saying you might not want to post guides before they're done. I'll hold my vote for the time being, feel free to PM me if you update it. >c<
Are you sure you hit the save AND publish buttons?
Save button is to "save" your guide. These changes will only be visible to YOU. This is useful for when you're in the process of creating/updating the guide, and you have to stop for some reason (e.g. you have to go to bed), but the guide isn't ready to be "published" yet in its current state.
Publish button is to 'publish' your guide, so that everybody can see it. Use this everytime you have created and/or updated a guide, otherwise nobody else will see it.
It's recommended to ALLWAYS press the "save" button, and when you're happy with your creation, press the "publish" button aswell.
Basically all build items and text are combined into one. Not only does this make the guide a wall-of-text, it also makes it harder to see which belongs to what.
When creating a guide, you can create different "Purchase Orders" when creating the build. This allows you to have seperate sets of items, as to make it more clear on what to get.
For example you should have the [
Also, in your actual "text", you talk about both builds in the same paragraph. I can hardly tell what part of the text belongs to which of the 2 builds because of this. Try seperating the information from either build by using a ruler:
The information you provide so far is okay, and describes
- A [ Pro's / Cons ] chapter, describing
- [ Items ] chapter, another way of seperating the text in which you explain the items from the other text, is by creating a seperate chapter for it.
- [ Abilities ] chapter, describing
There's lack of BB-coding. I can see that you know a fair deal about
Here are some tips on basic (Only VERY basic, if you want more in-depth info on BB-coding you'll need to find an article on that) BB-coding to help you get started. I placed them in a spoiler to not make this comment look to long:
Try to check out other guides to see how they handle their coding. Perhaps you might get some ideas from it. However, don't copy exact BB-coding, unless the author has given you explicit permission to do so.