Rename api methods to match SLAMS

[LeStegii]

• Renamed all API methods to fit their SLAMS "counterpart"

• getFoo() --> foo()

• Add deprecated methods

• Fix examples

[Almighty-Satan]

Should setters also be renamed?

[LeStegii]

Should setters also be renamed?

I thought about this, but how exactly would you rename them?

If we choose the design theme of using foo() as the getter and foo(Type value) as the setter, there could be confusion with SLAMS, as there is a value() method and a value(Context context) method, but both of them are getters.

[Almighty-Satan]

What about renaming ConfigEntry#setValue to something like ConfigEntry#set or ConfigEntry#put? I think that's the only setter in the entire project.

[LeStegii]

What about renaming ConfigEntry#setValue to something like ConfigEntry#set or ConfigEntry#put? I think that's the only setter in the entire project.

That would work, yea. Are there any setters in SLAMS that would have to be changed as well then in order to fit the style?

[Almighty-Satan]

That would work, yea. Are there any setters in SLAMS that would have to be changed as well then in order to fit the style?

I don't think SLAMS has any setters (at least not in the API) as messages can only be changed via LanguageParsers. Someone should double-check this tho.

[Almighty-Satan]

Shouldn't this also be renamed?

[LeStegii]

isModified() could be renamted to something like modified() I think.