I read the short descriptions of Implications and Alias, I even requested some in the past for a few things.
But when it comes to it's definition or rather what it actually does for the site, I am not entirely sure.

How does one make multiple Implications for a tag?

for instance, if you have Renamon, that would also imply fox and digimon.
But when you'd request an Implication is says
From: ______
To: ______

And oddly, it confuses me...it makes me feel like I'm trying to change Renamon to something else when really I just want to suggest more tags that should be added automatically when tagging Renamon (FYI I'm still using Renamon as an example I'm not really inquire Renamon)

For Alias it's changing one name to another that relatively means the same, right?

An alias means that one tag is replaced with another. The one in the "From" field becomes the one in the "To" field.
An implication means that every time the tag in the "From" field is added, the tag in the "To" field gets added as well.

Both request forms just reuse the same input fields for the sake of simplicity.

However, if you need to add several implications at the same time, the best option would be to use a Bulk Update Request.
It uses its own syntax that you can read about by clicking on the "Help" link under the "Script" field on that page. But the basic gist of it is this:

alias aaa -> bbb
imply aaa -> bbb

The first line creates an alias, the second - an implication.

bitwolfy said:
An alias means that one tag is replaced with another. The one in the "From" field becomes the one in the "To" field.
An implication means that every time the tag in the "From" field is added, the tag in the "To" field gets added as well.

Both request forms just reuse the same input fields for the sake of simplicity.

However, if you need to add several implications at the same time, the best option would be to use a Bulk Update Request.
It uses its own syntax that you can read about by clicking on the "Help" link under the "Script" field on that page. But the basic gist of it is this:

alias aaa -> bbb
imply aaa -> bbb

The first line creates an alias, the second - an implication.

I see, I think I get the concept now, however I don't think I understand Bulk Updates now.

unalias aaa -> bbb
unimply aaa -> bbb
alias aaa -> bbb
imply aaa -> bbb
update aaa -> bbb
category tag_name -> category_name

can you please explain this better to me? maybe with an example?

closetpossum said:
I see, I think I get the concept now, however I don't think I understand Bulk Updates now.
can you please explain this better to me? maybe with an example?

Not quite sure what's there to explain. But okay.

1. unalias aaa -> bbb If you want bbb to stop being aliased to aaa. For example, if I wanted catgirl to stop being aliased to cat_humanoid, I would add this to the script: unalias catgirl -> cat_humanoid.
2. unimply aaa -> bbb Similar to above. If I wanted cattle to stop implying bovine, I would use this line: unimply cattle -> bovine.
3. alias aaa -> bbb. Creates an alias. If I wanted undressed to be aliased with nude, I would use this: alias undressed -> nude.
4. imply aaa -> bbb. Similar to above. If I wanted chubby_female to imply female, I would use this: imply chubby_female -> female.
5. update aaa -> bbb. This is a very situational tag. It replaces all instances of tag aaa with tag bbb, but does not create an alias. It's rarely ever needed.
6. category tag_name -> category_name. Kind of self-explanatory - changes the tag's category. This is mainly used for categories that can only be changed by staff members, for example, thread #28498 is a request to set the category of patreon_reward to invalid.

The BUR is handy because it allows you to have any number of requests like these, rather than doing them one at a time through alias / implication requests.

bitwolfy said:
Not quite sure what's there to explain. But okay.

1. unalias aaa -> bbb If you want bbb to stop being aliased to aaa. For example, if I wanted catgirl to stop being aliased to cat_humanoid, I would add this to the script: unalias catgirl -> cat_humanoid.
2. unimply aaa -> bbb Similar to above. If I wanted cattle to stop implying bovine, I would use this line: unimply cattle -> bovine.
3. alias aaa -> bbb. Creates an alias. If I wanted undressed to be aliased with nude, I would use this: alias undressed -> nude.
4. imply aaa -> bbb. Similar to above. If I wanted chubby_female to imply female, I would use this: imply chubby_female -> female.
5. update aaa -> bbb. This is a very situational tag. It replaces all instances of tag aaa with tag bbb, but does not create an alias. It's rarely ever needed.
6. category tag_name -> category_name. Kind of self-explanatory - changes the tag's category. This is mainly used for categories that can only be changed by staff members, for example, thread #28498 is a request to set the category of patreon_reward to invalid. The BUR is handy because it allows you to have any number of requests like these, rather than doing them one at a time through alias / implication requests. [/quote] Okay, I understand it all now. Thank you kindly Bitwolfy, ever the reliable!

closetpossum said:
Okay, I understand it all now. Thank you kindly Bitwolfy, ever the reliable!

No problem, I'm happy to help.

bitwolfy said:
The BUR is handy because it allows you to have any number of requests like these, rather than doing them one at a time through alias / implication requests.

In addition to what bitWolfy says here, a BUR has the further advantage of being editable before it's approved or rejected.

clawstripe said:
In addition to what bitWolfy says here, a BUR has the further advantage of being editable before it's approved or rejected.

thanks for the info, it'll be useful one day.