dachgruber / splittermondbutler Goto Github PK

Possible exceptions should always get carried through the functions to the calling function in the controller.
The view already has a method for exception displayment, but could use some rework as the normal user isnt interested in the stacktrace (but still wants to be notified if things go south!)

-save a list of objects used in bullshit bingo
-add a set of commands only accessible to the gamemaster to access the list
-add a function for ths user to roll a new bullshit bingo

When starting the battle, the TickBar should display the next few moves with their tick-number. This simply doesnt show up

I assume that the getNextMoves() Method of the new TickBar is bugged

maven could improve the .jar-implementation as well as compatability with other user

es wird eine neue Methode gebraucht, um Niks Bullshit-Bingo zu realisieren

this could use some cleaning up, documentation and performance upgrades

as Java 11 doesnt support the case with -> from @SpuelMett , the project should be updated to run on the newest version

currently every type of item on the tickbar gets its own ArrayList with an extry ArrayList for the position. A new class should be implemented to simulate an marker on the actual tickbar with name and pos, so that the tickbar doesnt care about player, enemy, etc anymore.

The new class could act as a parent class for something like TickBarPlayer, TickBarEnemy etc to support different data types and different displayment options

the bot should support a silent roll to the gamemaster, so that the other players cant see the results

bullshitbingo will reviece a complete internal overhaul with new features, save functionality and improved moduality

As documentation is key, the user should be able to get some simple instructions of how to use the commands. A designated !help along with the actual instruction could be used to aquire information for how to use the tickbar, how to use the rolling function etc.

the long if....else if....else if.... could be replaced with a switch case statement. Should look into that

need to rework the check method in view.rolltemplate

The current View package is a huge clusterfuck, which needs cleaning, documentation and restructuring. While at it the different template classes should get a upgrade, because the current implementation is ugly and not modular for the future

as stated in #33 ,items should include rarity. This is a great way to implement further rnd chaos to the system.

As a epic/legendary item will be very special, the corresponding message should also be special in some way. This could include images, gifs, audio (maybe in the future) or simple colors/reactions.

The tickbar should be displayed in mentions, not in their usernames.

An easy fix would be to replace the discord name string with their corresponding nickname, but handling players as users could be beneficial for future implementations

some weird black magic is happening at the command seperation when whitespace is included.

!r 2W10 works as well as !R 2w10, but having 'r' and 'w' both lower or uppercase breaks stuff.

currently the packages are named in the wrong way. Also, the model/controller packages should include sub-packages for the different features (dice, tickbar, bingo etc)

Seen by RollButler.Net. The simple !r command should support cmds without blanks inbewtween, for example !r2W10+4, !r 4W6 etc

a command is needed so that the gm (and only the gm) should be able to upload a new txt file for bullshit bingo

The new Tickbar has some issues properly displaying the enemy names

The code needs futher documentation, so that other contributers aren't getting a stroke

Before starting the battle, the tickbar list command - !tick list - shouldnt list the default embed, but should send a customized overview of the joined players. Therefore the gm could always see who wants to fight and who is still missing

the items are unique and shouldnt be distributed several times. As that the items should be loaded from the table, updated and then written in the bullshit.txt once again

items in the bingo should be picked by their rarity/probability. This opens up new possibillities for the gm as epic/legendary items can be much harder to get - therefor much better and much more useful!