Closed tboy1337 closed 1 month ago
because there's no emoji in this line.
Just seems like it should for continuity but the main issue is the other missing icons/characters.
i'm not sure what you mean.
4th line down from the top, look at the character to the left of Getting basic account data.
then carry on looking down, there are a lot of them.
most likely this is because the system in which the script is running does not support emoji. it's termux or what?
Windows 10 running python 3.12.5, I run main.py through python.exe through CMD (python main.py
).
indeed, maybe it's the standard windows terminal that doesn't support emoji.
I'm using this terminal by default, it supports emoji.
Yea i guess i should probably start using it lol
just tried it, it fixes the emoji issue but creates another one so i can live with it lol.
what's the new problem?
I’m running the updater i made alongside the bot (updater.py), i have 16 bots plus 16 updaters, i run the updater with py.exe and the bot with python.exe so there are two different taskbar window groups which i can tile and see what is actually going on but when i open them all with terminal they have the same taskbar window grouping so I cant tile it without the windows being too small.
I don't quite understand why you need a separate Updater for each bot, try to learn what symlink is. I sketched a small bat script that creates a specified number of clones and creates symbolic links to the necessary files for each clone, all you need to do is put the config file separately in each clone folder and run the bot from the clone folder. in this case you will only need 1 updater process for the main folder where the fork itself is located. and if necessary you will need to terminate all running bot processes and restart them.
the advantage is that symlink will always point to the file as long as it exists, even if you delete the original file and create another file named as original, symlink will link to it.
@Fy0urM what do you mean by fork in the code? Also will my updater work with this set up? Will it create differently named clone folders?
fork means your copy of someone else's repository, I forgot that you work with your own repository. but it doesn't matter, it is enough to have one folder with the main repository as a base and updates, and to run bots from the created “clones”. symlinker creates clone folders in the format bot#
where #
is the number of the clone.
In bat you set the required number of clones,
set “botsCount=3”
.
the loop runs from 1 to botsCount and creates a clone folder for each iteration.
but most likely you will have to modify your updater to close all clone processes when you need to update and run each clone looking in the clones folder.
this is just my suggestion, nothing more. i don't insist on using it. it just seemed to me that having 1 updated repository is easier than constantly checking for updates for each bot.
Ah i see, ok thanks for the code, i was just wondering why fork, maybe master would be a better name for it. Currently the updater looks for the process running from the same folder as itself, it took a while to get it working so idk if i want to start again to get it working lol.
Some of the characters are not showing correctly, also
Not enough coins to buy a daily combo.
message doesn't have an icon.