Do you think I could just leave this part blank and it'd be okay? We're just going to replace the whole thing with a header image anyway, right?
You are not logged in.
Pages: 1
Offline
Offline
May I ask you why would you like to write bots?
Everybody edits, but some edit more than others
Offline
You need a lot of motivation and some time to learn how to program, if you want to be self-taught. I don't recommend starting with an EE bot immediately. Just begin with the basics. Ask your questions to google, he's your best friend.
Offline
Ask your questions to google, he's your best friend.
Don’t assume Google’s gender.
Offline
You need a lot of motivation and some time to learn how to program, if you want to be self-taught. I don't recommend starting with an EE bot immediately. Just begin with the basics. Ask your questions to google, he's your best friend.
I started programming with end goals that were waaaay out of my reach, and although I never really met them, I think it was a fairly good way to learn as it provides the motivation you need to learn the things you need to.
I agree with the google bit though
Offline
I started programming by pure trial and error. Krock has been guiding me about efficient method implementations.
Offline
I can't say I've seen a great bot tutorial yet. The first problem with all of them is that they don't emphasise enough the difference between C# knowledge and bot-coding knowledge, where the first is equally as important as the second.
A good tutorial should start by assuming that the reader is already competent in programming (ideally in a C-language or similar). If not, it should force a number of "Learn C#" links down the reader's throat (whether they like it or not) and say "come back when u less nub", and preferably enforce this by assuming a minimum level of competence throughout the tutorial. I spent a good month learning C# before I touched SimpleConnect, and it's crucial to learn the concepts of generic programming along with the language-specific syntax and semantics.
Once our reader is somewhat enlightened, and after hours of fiddling with syntax errors have knocked the stars out of their eyes and convinced them that coding a decent bot is a good hard grind, the tutorial must begin with theory. In the same way that you learn the concept of a loop before coding loops, you have to be able to answer fundamental questions about bots before coding bots;
What is PlayerIO? What is the PlayerIOClient library and why do I need it? What is a PlayerIO Message and what happens when my bot joins a world? What is the EE Protocol and how do I apply it? Which message types are the most important, what do they contain and when/how does the bot receive them?
Then - and only then - should we start with PlayerIO-specific code. The second mistake that many tutorials make is by handing the reader some amount of code without properly explaining its parts. In theory the reader should be able to read through the documentation and find out for themselves, but that wouldn't make it a great tutorial. For example, here's a bad start:
This is a better start:
It takes ages to write a really in-depth bot tutorial, and even this fraction of a fraction above took me a while to write. I can't really blame anyone for not having done it.
One bot to rule them all, one bot to find them. One bot to bring them all... and with this cliché blind them.
Offline
I can't say I've seen a great bot tutorial yet. The first problem with all of them is that they don't emphasise enough the difference between C# knowledge and bot-coding knowledge, where the first is equally as important as the second.
A good tutorial should start by assuming that the reader is already competent in programming (ideally in a C-language or similar). If not, it should force a number of "Learn C#" links down the reader's throat (whether they like it or not) and say "come back when u less nub", and preferably enforce this by assuming a minimum level of competence throughout the tutorial. I spent a good month learning C# before I touched SimpleConnect, and it's crucial to learn the concepts of generic programming along with the language-specific syntax and semantics.
Once our reader is somewhat enlightened, and after hours of fiddling with syntax errors have knocked the stars out of their eyes and convinced them that coding a decent bot is a good hard grind, the tutorial must begin with theory. In the same way that you learn the concept of a loop before coding loops, you have to be able to answer fundamental questions about bots before coding bots;
What is PlayerIO? What is the PlayerIOClient library and why do I need it? What is a PlayerIO Message and what happens when my bot joins a world? What is the EE Protocol and how do I apply it? Which message types are the most important, what do they contain and when/how does the bot receive them?
Then - and only then - should we start with PlayerIO-specific code. The second mistake that many tutorials make is by handing the reader some amount of code without properly explaining its parts. In theory the reader should be able to read through the documentation and find out for themselves, but that wouldn't make it a great tutorial. For example, here's a bad start:
It feels like you have so much of motivation. Maybe you should make your own tutorial instead. I don't have the motivation to make anything to a dying game.
Offline
The real problem has absolutely nothing to do with language structures or libraries.
The real problem is that everybody here thinks of programming as program writing and compiling, an horribly wrong concept. I'm sure almost (to not say just all) all here don't even know about pseudo-code or algorithms.
Offline
*cough* *cough*
https://forums.everybodyedits.com/viewt … p?id=36612
They show you the very basics of connecting n stuff.
These videos expect you to know some basic stuff about programming in general tho :/
Can't say they are anywhere near perfect but the videos of Jabatheblob1 really helped me to start.
Ingame: marten22 My steam: MartenM
Offline
It feels like you have so much of motivation. Maybe you should make your own tutorial instead.
Bah. The day I wake up with that much motivation is the day I'll spend doing the things I should be doing, like coursework.
Having said that, I may decide to write a tutorial bit by bit and release a chapter per week. If there's enough interest, I'll consider it.
1 woot = 1 interest ^^
One bot to rule them all, one bot to find them. One bot to bring them all... and with this cliché blind them.
Offline
1 woot = 1 interest ^^
Inb4 people woot it to make you waste your time (since they're not actually interested).
jk, we'll see how it turns out.
Offline
Latif wrote:Ask your questions to google, he's your best friend.
Don’t assume Google’s gender.
It*
Offline
Devlin wrote:Latif wrote:Ask your questions to google, he's your best friend.
Don’t assume Google’s gender.
It*
They*
Thanks to: Ernesdo (Current Avatar), Zoey2070 (Signature)
Very inactive, maybe in the future, idk.
Offline
Latif wrote:Devlin wrote:Latif wrote:Ask your questions to google, he's your best friend.
Don’t assume Google’s gender.
It*
They*
It*
Offline
Latif wrote:Devlin wrote:Latif wrote:Ask your questions to google, he's your best friend.
Don’t assume Google’s gender.
It*
They*
You know I mean the search engine and not the people who work in the company..
Offline
Or consider using JavaScript instead of C# since web development can get you much farther in life as well as cross platform abilities of running a bot on a website
Offline
Pages: 1
[ Started around 1732235978.0642 - Generated in 0.322 seconds, 12 queries executed - Memory usage: 1.8 MiB (Peak: 2.08 MiB) ]