Aldebaran is a cross-platform (Discord and Revolt) multi-purposes bot which offers useful features to DiscordRPG players along with many commands of all kinds, from fun to utilities.
Describe the bug &setprofile does not work. It does not show anything.
To Reproduce
Steps to reproduce the behavior:
Use &setprofile (without using &profile earlier)
Expected behavior
Set the profile correctly.
Aldebaran details:
Version: 2.0.1
Additional context &setprofile was not correctly updated with the 1.11 update. The user's profile needs to be fetched in &setprofile before being used.
Is your feature request related to a problem? Please describe.
Users get confused when they try something like &uconfig sidestimer on and get an error message.
Describe the solution you'd like
I suggest making those error messages mention how those things are case-sensitive and provide an example of how to type it correctly.
Describe alternatives you've considered
Making them not case-sensitive I guess, but the first suggestion should be easier to implement.
Is your feature request related to a problem? Please describe.
Some people don't like how the bot prompts you to cancel the timer whenever you do your sides.
Describe the solution you'd like
Maybe an option like &uconfig sidestimerPrompt off.
Describe alternatives you've considered
Someone else suggested just turning it off globally and have a separate command to cancel the timer, to maybe help with ratelimits.
When using any command that pulls a picture from nekos.life, such as xrandom, it does not pull a picture and displays [object Object] instead.
Use xrandom, xkitty, xneko, etc command.
Bot posts an message containing "object Object" and the correctly programmed dialog associated with the command used.
Expected behavior
It seems that object Object is a placeholder for the picture and it is supposed to display a picture relating to the command used from a pool of pics on nekos.life. If I were to take a stab at solving it, try checking if the bot is still authorized to pull from that site.
Describe the bug
If you use a real currency and a fake one, it will always tell you the one on the left doesn't exist, even if it's actually the one on the right.
The custom timers would be a way to let the users create their own timer, they can change their name and choose whether they want it to be triggered every x amount of time of if they want it to be triggered by text sent by a bot in channel (should allow regular expressions). Either way, the user needs to start the timer and stop it by themselves (the timer should stop by itself after a certain amount of time if there is no user response for a long time, this duration is variable depending on the timer cooldown). The user can also choose whether they want to the timer sent in their DMs in the server channel. To prevent spam, administrators of the server will be able to disable timers in channel through &gconfig serverTimers off.
Describe the bug
Trying to use &osurecent produces no info. Only responds with "the user you specified does not exist, or at least in the mode specified."
To Reproduce
Try to do like &osurecent Ciborn.
Expected behavior
Showing the user's most recent play.
Aldebaran details:
Version 1.11.0
Additional context
Even if you set a username in &uconfig, it still produces no info.
Is your feature request related to a problem? Please describe.
Now it's cool that &skills shows item drops info 'n all, but it doesn't show the skill xp you'll get when you go full mineboost for example.
Describe the solution you'd like
Showing skill xp gain when going full sideboost(put all your attribute points on, for example, mineboost).
Describe alternatives you've considered
Mathing it manually myself with &math. What do I look like? A nerd? Pfffft
Describe the bug
The bot doesn't respond to item names that aren't saplings. The example the command gives for proper usage when you do &plantcalc on its own (&plantcalc 1 24 olive) also tells people to use the wrong item, and therefore doesn't work.
Describe the bug
1.) You can set the timer to 0 seconds to make the bot smash into the ratelimit (and causes a bunch of SQL errors).
2.) The -c flag makes it not send messages at all.
3.) The documentation is very poor.