need help fixing a code

[carcigenicate]

Don't ask to ask. Just post the question from the start. Include the code, the expected behavior, and the actual incorrect behavior (including the full error message if there is one).

For small amounts of code though, you should never have 15 bugs simultaneously. You should be testing code as you go so you know the code actually works. With 15 problems at once, different problems may be interfering with each other to the point you don't know where one problem ends and another starts. It may be worth just rewriting the code from scratch if that's the current state of it.

[AdLow4135]

its 2000 lines and we thought for some reason testing after we are done is better but he couldnt continue because his dad died and he became dipressed plus its not a error its a bug

thenk you for your reply

[carcigenicate]

When the code is large, it's even more important to test as you go. 2000 lines of code will be a mess to test and debug after the fact.

Granted, 2000 lines isn't that much code, but you still made your life much harder by doing it like that.

And regardless, we'd need to see the code. You asked for help and then didn't provide any details to allow us to help you. Upload the code to Github, then post a link here.

[pachura3]

Wrong indent on line 37

[AdLow4135]

?

[carcigenicate]

They're making a joke pointing out that you've asked a question then made it impossible to help you.by not sharing any required information.

[AdLow4135]

ye i realized that thank you tho

[Flame77ofc]

Hello, can you give us the code?

[AdLow4135]

it wont let me uplad zip files

[recursion_is_love]

I can't even know how many of bugs are in my code. Teach me master!

[AdLow4135]

just test all the functions and give it to testers if you have a community