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

If you do not know programming this is not the place to start. And more info #527

Open
Jessecar96 opened this issue Jan 1, 2014 · 7 comments
Labels

Comments

@Jessecar96
Copy link
Owner

SteamBot is simply too in depth for most people to start learning programming or C# on. Start with something easier. It's not easy to start with something fairly complicated and think you'll know it right away. If you're looking for a quick way to make some profit with a trading bot look elsewhere, you won't find it here.

Also, this is an issue tracker. It's a place to post bugs and feature suggestions for the repo. This is NOT a place to ask for help or give help to people who ask.

If anyone asks for help here ignore it. Do not respond to their post! It will be deleted or locked when I get around to it. If you respond to someone asking for help you're just as bad as the person asking for it.

This also is obviously not the place to sell your bot, code, or bot making abilities.

I also removed my tutorial video from YouTube. It was old and most parts were outdated. The example repo is gone too. There was also some personal reasons for me taking it down. It won't be back unless I get around to making a new one.

We also have the Subreddit /r/SteamBot for helping. And I will be posting this there as well.

@Lagg
Copy link
Contributor

Lagg commented Jan 1, 2014

and if you persist, you'll get an honorary place at the Gamerprogrammer wall of shame.

@BlueRaja
Copy link
Collaborator

BlueRaja commented Jan 2, 2014

Another good place to ask questions would be StackOverflow. They're more active, and significantly more forgiving about asking beginner-questions.

@deadlyunknown
Copy link

But if you modify the existing codes by yourself, does that consider as "gamerprogrammer"?

@waylaidwanderer
Copy link
Contributor

Only if you actually know what you're doing. You're either a programmer or you're not.

@eqazec
Copy link

eqazec commented Jan 8, 2014

@waylaidwanderer This is a bit off topic, but I am curious. What would you consider to be the most complex part of the SteamBot code? Don't confuse me with someone who doesn't understand C#. I'm just curious about your opinion.

@waylaidwanderer
Copy link
Contributor

There's nothing overly complex about it on the whole, but for someone who is just picking it up and has limited experience with programming languages, you'd find them asking a lot of basic questions which could be answered via Googling or through logic, or most important, trial and error.
Honestly when I first started fiddling around with SteamBot all I had was one semester's worth of experience in C, and no C# knowledge. But I believe it's that one semester that made all the difference, because once you understand the fundamentals, everything else is pretty straightforward, even if it's a different language.

@BlueRaja
Copy link
Collaborator

BlueRaja commented Jan 8, 2014

The most complex part right now is definitely the inventories. Right now there's an Inventory class that can only be used for TF2 stuff, and another GenericInventory class that's used for everything else. The API's for both are completely different. Both involve a number of magic numbers (appid, contextid, defindex, etc.). Each have a separate way of describing items. There are some easily-avoidable-yet-unnecessary pitfalls when using GenericInventory with Trade.

There's no reason we couldn't have a single easy-to-use Inventory class for all item-types, it's just that no one's done it yet.

This was referenced Jan 19, 2014
@SephirothSG SephirothSG mentioned this issue Mar 31, 2014
This was referenced Apr 13, 2014
This was referenced Jul 1, 2014
@FrozenHaxor FrozenHaxor mentioned this issue Aug 15, 2014
This was referenced Sep 21, 2014
This was referenced Sep 28, 2014
This was referenced Oct 12, 2014
This was referenced Dec 15, 2014
Repository owner locked and limited conversation to collaborators Jan 14, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

6 participants