I catch events using SubscribeEvent, but i've seen how someone catchs one using EventHander(Plus, In main class all FML event is catched using EventHandler).  Why So?

I don't speak English. The text was compiled in the Google translator

SubscribeEvent is for our EventBus system, Not sure what you mean by EventHandler as that's not a Forge related class.

11 hours ago, LexManos said:

SubscribeEvent is for our EventBus system, Not sure what you mean by EventHandler as that's not a Forge related class.

I can't undestand why some events caught using EventHandler and other using SubscribeEvent. What's the difference between them?

Please tell us the fully qualified name of EventHandler to help us understand what you're referring to.

For example, SubscribeEvent's fully qualified name is: "net.minecraftforge.eventbus.api.SubscribeEvent"

If EventHandler it doesn't start with "net.minecraftforge", it's likely not a part of Forge.

3 hours ago, Paint_Ninja said:

Please tell us the fully qualified name of EventHandler to help us understand what you're referring to.

For example, SubscribeEvent's fully qualified name is: "net.minecraftforge.eventbus.api.SubscribeEvent"

If EventHandler it doesn't start with "net.minecraftforge", it's likely not a part of Forge.

Event Handler is in the package "net.minecraftforge.fml.common.Mod.EventHandler", and SubscribeEvent is in the package "net.minecraftforge.fml.common.eventhandler.SubscribeEvent"

Game Version is 1.12.2

Ah, its old code that is outdated. Basically EventHandler is for FML specific events. Typically the lifecycle ones. 
On moddern versions its the modBus.