Skip to content
This repository has been archived by the owner on May 20, 2024. It is now read-only.

object of none #93

Closed
UwUTheDog opened this issue Feb 19, 2023 · 8 comments
Closed

object of none #93

UwUTheDog opened this issue Feb 19, 2023 · 8 comments
Labels
duplicate This issue or pull request already exists

Comments

@UwUTheDog
Copy link

image
Get this error when starting it. followed steps properly.

@Maxhem2
Copy link

Maxhem2 commented Feb 19, 2023

There is a warning message that indicates that the directory where the "pip.exe", "pip3.10.exe", and "pip3.exe" scripts are installed is not currently included in your system's PATH environment variable. This means that you may not be able to run these scripts from any location in your command prompt or terminal, and you may need to navigate to the directory where they are installed in order to use them.

To add the directory to your system's PATH environment variable, follow these steps:

Open the Start menu and search for "Environment Variables".
Click on the "Edit the system environment variables" option.
Click on the "Environment Variables" button at the bottom of the System Properties window.
Under "System Variables", scroll down to find the "Path" variable and click on "Edit".
Click on the "New" button and add the full path to the directory where the pip scripts are installed, e.g. "C:\Users\Cows C\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\Scripts".
Click "OK" to save the changes and close all the windows.
After adding the directory to the PATH environment variable, you should be able to run the pip scripts from any location in your command prompt or terminal.

Alternatively, if you prefer to suppress this warning, you can use the "--no-warn-script-location" option when running pip commands. For example, instead of running "pip install ", you can run "pip install --no-warn-script-location ".

@UwUTheDog
Copy link
Author

Did all that and it still gives the error

image

@UwUTheDog
Copy link
Author

image

@Maxhem2
Copy link

Maxhem2 commented Feb 19, 2023

Have you made sure your config is filled correctly?

@UwUTheDog
Copy link
Author

discord.gg/cowsgomoo You can litterly see your self on share screen everythings set correctly. i will litterly pay you to make it work if you think you know better.

@thejoabo
Copy link
Owner

Hello @UwUTheDog , my best guess would be incorrect token or something related to your authorization thought Discord's gateway (which I use to receive all the new events addressed to that token) and, since you are not being authorized, it tries to get key-values from a None type event returned from the gateway (crashing the bot).

I can't say for sure what exactly is going on, but I was able to replicate your issue by setting a wrong value to my token parameter as you can see here:

image

@UwUTheDog
Copy link
Author

Fixed now i had to get my token a diff way it wasnt showing the real one up i recomend this site
https://linuxhint.com/get-discord-token/

@thejoabo
Copy link
Owner

Hello @UwUTheDog , I'm glad it worked out then. Just for closure, there is already a guide about how to get the token and other important topics on this repo: FAQ.

@thejoabo thejoabo added the duplicate This issue or pull request already exists label Feb 22, 2023
@thejoabo thejoabo pinned this issue Feb 22, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

3 participants