wwevo / chrani-bot-tng Goto Github PK

the dom is required by every part of the bot, it simply has no use being optional. will take some doing to move it out as a lot of calls directly path to module.dom.data, and other dom functions, so they all have to be refactored to cut out the .dom part ^^
makes more sense to make it a mixin for the general module

With a fresh database, every first-time storage action needs to be done twice, like switching a view in a widget (which is done by storing a value in a monitored dict).

After that, it all works splendidly. Probably I'm doing something in the wrong order. Needs to be looked into.

I sometimes encounter an empty player entry, without any content or ID elements.
They are probably created because I barely check for data integrity now and get sent by mistake. They are not saved in the database either, afaik

The causing module or modules have to be identified and found, i suspect any of the methods acting on new players joining.

Sometimes after modifying a players dataset, the player_widget table row class might not get set correctly. You can witness it for players logging out. Their table_row will get an empty "class" attribute without any content whatsoever.
This throws off the not(class) css selector causing a wrong color for the entry.

Each module has its own template folder assigned to it

I have to reproduce the jinja2_macros file for each module I want to use the macros in. I'd rather have them stored globally, I have no idea on how to accomplish that.

The actions performed in the modules main loop shouldn't be hardcoded, but rather set in the default options, or config file. That way, the modules become easier to extend and configure.
I could then easily switch out methods of collecting authentication information for example, by loading the admin table from a file instead of the games list admins command, which is currently hardcoded to run once to success.
This should make changes to the environment much easier, with an upcoming alpha or mods changing. A bot user can then just use the settings he wants.