bug-fix transfer feature

[ankitsmt211]

• default avatar if user do not have one
• remove embed from warning message to user
• minor fixes

if avatar is missing:

if present:

User warnings:
Before:

Now:

[ankitsmt211]

There's one more instance like this, where author is nullable so i can't use effectiveUrl. Any suggestions around this? or should i leave em as it is?

[Zabuzard]

According to the JDA doc, the avatar url param is Nullable:

Why again did our previous code crash? null should be supported here by JDA.

[Zabuzard]

The bug was not giving null to setAuthor(...), it was about us invoking a method on sth that was null, see:

[ankitsmt211]

The bug was not giving null to setAuthor(...), it was about us invoking a method on sth that was null, see:

you are right about that, i'll discard other changes but i still think effectiveAvatar is better otherwise we get this

With effectiveAvatar, its either userAvatar or a default one.

[Zabuzard]

sure thing

[ankitsmt211]

Changes are not significant, i have replaced avatar url only in all files. Few more bug fixes in TransferFeature class. I have tested the changes in transfer-feature and report, mute, audit, ban. Like it should, displays a default avatar if none is present for user. I couldn't verify scam blocker and log routine, but i assume it works.