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.
I needed a way to implement a more formatted version of the EE Protocol in my program, so I decided to create from scratch a c# .net "dll" that would do so,
As I started adding a few send messages and a few recieves, I realized that it'd take a lot more time, so I decided to post it on github for the community to edit.
If you read the readme you'll know just about all of it.
Link: https://github.com/SirJosh3917/MDEE
Also if you don't want to make a fork, post an issue saying your name on these forums and I'll add you.
Offline
I needed a way to implement a more formatted version of the EE Protocol in my program, so I decided to create from scratch a c# .net "dll" that would do so,
As I started adding a few send messages and a few recieves, I realized that it'd take a lot more time, so I decided to post it on github for the community to edit.If you read the readme you'll know just about all of it.
Link: https://github.com/SirJosh3917/MDEE
Also if you don't want to make a fork, post an issue saying your name on these forums and I'll add you.
I don't get the point of this, why would we need a C# implementation of the EE Protocol? It's already simple enough using the send/recieve message commands provided by the PlayerIOClient DLL and just reading the EE protocol documentation. Nobody wants an extra DLL in their bot download (since we can't exactly implement the DLL into our projects without it being external). We don't need something to make us coders lazier by using a library. I think this would be useful for newer bot programmers though, Not much useful for the ones who are advanced in all of the protocols and don't need any more libraries to help us.
Hey look a bunch of stats about me
Offline
ninjasupeatsninja wrote:I needed a way to implement a more formatted version of the EE Protocol in my program, so I decided to create from scratch a c# .net "dll" that would do so,
As I started adding a few send messages and a few recieves, I realized that it'd take a lot more time, so I decided to post it on github for the community to edit.If you read the readme you'll know just about all of it.
Link: https://github.com/SirJosh3917/MDEE
Also if you don't want to make a fork, post an issue saying your name on these forums and I'll add you.
I don't get the point of this, why would we need a C# implementation of the EE Protocol? It's already simple enough using the send/recieve message commands provided by the PlayerIOClient DLL and just reading the EE protocol documentation. Nobody wants an extra DLL in their bot download (since we can't exactly implement the DLL into our projects without it being external). We don't need something to make us coders lazier by using a library. I think this would be useful for newer bot programmers though, Not much useful for the ones who are advanced in all of the protocols and don't need any more libraries to help us.
I need it for my program im making, a bot creator. So it can easily load in messages for players and tell them what it is.
I agree with you, but the dll is going to be used for my bot creator so the program can tell the player all about it, they fill it out, and it has the correct message.
Plus it'd be nice for something else.
Offline
Joshua708 wrote:ninjasupeatsninja wrote:I needed a way to implement a more formatted version of the EE Protocol in my program, so I decided to create from scratch a c# .net "dll" that would do so,
As I started adding a few send messages and a few recieves, I realized that it'd take a lot more time, so I decided to post it on github for the community to edit.If you read the readme you'll know just about all of it.
Link: https://github.com/SirJosh3917/MDEE
Also if you don't want to make a fork, post an issue saying your name on these forums and I'll add you.
I don't get the point of this, why would we need a C# implementation of the EE Protocol? It's already simple enough using the send/recieve message commands provided by the PlayerIOClient DLL and just reading the EE protocol documentation. Nobody wants an extra DLL in their bot download (since we can't exactly implement the DLL into our projects without it being external). We don't need something to make us coders lazier by using a library. I think this would be useful for newer bot programmers though, Not much useful for the ones who are advanced in all of the protocols and don't need any more libraries to help us.
I need it for my program im making, a bot creator. So it can easily load in messages for players and tell them what it is.
I agree with you, but the dll is going to be used for my bot creator so the program can tell the player all about it, they fill it out, and it has the correct message.
Plus it'd be nice for something else.
Make the UI like in scratch, drag and drop bot building.
Thank you eleizibeth ^
I stack my signatures rather than delete them so I don't lose them
Offline
We don't need something to make us coders lazier by using a library.
Why not use the stuff given to you if it cuts down time?
Not much useful for the ones who are advanced in all of the protocols and don't need any more libraries to help us.
I beg to differ here. A source version (I do agree that a DLL would be less useful) would allow you to fix protocol changes way me organised. I also think (not sure and haven't tried it out) you can send custom messages, so using a method where the protocol is centralized also helps you manage those custom messages.
Also been thinking of a way to make an implementation that would make your bot fix itself with small protocol changes (using the types of the objects and moving them up in ID until their type matches the type at given ID). Obviously wouldn't nearly be 100% fail-proof. But it should make bots at least a bit more durable (unless another big update comes out, obviously.
Actually think I'm gonna make exactly that next week...
Make the UI like in scratch, drag and drop bot building.
From what I can tell that would be terribly hard. But then again I hate C# (or any) Graphics... Maybe there's a lib for that.
Offline
[DllThing]
First off, this isn't finished; second, you haven't compiled into a DLL; third, it isn't a valid tag : use [Idea] or [Alpha]
Koya wrote:Make the UI like in scratch, drag and drop bot building.
From what I can tell that would be terribly hard. But then again I hate C# (or any) Graphics... Maybe there's a lib for that.
It's perfectly do-able.
Thank you eleizibeth ^
I stack my signatures rather than delete them so I don't lose them
Offline
... (stuff)
Make the UI like in scratch, drag and drop bot building.
I have completed some of the skeleton for the bot, and now I want to make the UI (which as you said, is like scratch). My question is to you, do you have any possible pointers, guides, or tips for me?
I'll keep looking on google for those though.
Offline
Koya wrote:... (stuff)
Make the UI like in scratch, drag and drop bot building.I have completed some of the skeleton for the bot, and now I want to make the UI (which as you said, is like scratch). My question is to you, do you have any possible pointers, guides, or tips for me?
I'll keep looking on google for those though.
I'm not 100% sure how to do it with C#; as a web developer I'd use Node.js w/ app.js and find out how to compile a C# program without VS
Thank you eleizibeth ^
I stack my signatures rather than delete them so I don't lose them
Offline
ninjasupeatsninja wrote:Koya wrote:... (stuff)
Make the UI like in scratch, drag and drop bot building.I have completed some of the skeleton for the bot, and now I want to make the UI (which as you said, is like scratch). My question is to you, do you have any possible pointers, guides, or tips for me?
I'll keep looking on google for those though.I'm not 100% sure how to do it with C#; as a web developer I'd use Node.js w/ app.js and find out how to compile a C# program without VS
Nor am I, but I do know how to compile a c# program without VS, since this program will be compiling bot code into a .exe - so that way the program isn't simply an "interpreter"
I think I might leave the project maker at a somewhat-scratch version of what you're saying, but it won't be as "scratchy" so to speak.
Offline
[DllThing]
First off, this isn't finished; second, you haven't compiled into a DLL; third, it isn't a valid tag : use [Idea] or [Alpha]
He's perfectly fine to use WIP/Idea and DLL as tag (dllthing would be a bit unprofessional), since he's planning to distribute it as an DLL once finished (I assume).
I'm not 100% sure how to do it with C#; as a web developer I'd use Node.js w/ app.js and find out how to compile a C# program without VS
My suggestions if you wanna stick to js: Use browser inside C# winform (though then it's rather hard to communicate with the js (I think)), or, better suggestion, use ASP.NET. You'd have to run the bot from your browser though (no need to actually host it, obviously you can use localhost).
Offline
Koya wrote:ninjasupeatsninja wrote:Koya wrote:... (stuff)
Make the UI like in scratch, drag and drop bot building.I have completed some of the skeleton for the bot, and now I want to make the UI (which as you said, is like scratch). My question is to you, do you have any possible pointers, guides, or tips for me?
I'll keep looking on google for those though.I'm not 100% sure how to do it with C#; as a web developer I'd use Node.js w/ app.js and find out how to compile a C# program without VS
Nor am I, but I do know how to compile a c# program without VS, since this program will be compiling bot code into a .exe - so that way the program isn't simply an "interpreter"
I think I might leave the project maker at a somewhat-scratch version of what you're saying, but it won't be as "scratchy" so to speak.
It's quite easy if you use relative positions and drag-n-drop pictureBoxes, or maybe even just hand-drawing the whole window with GDI+ (I hate doing that but I had to do it on one project commission, Don't know where I put the code anymore though)
Hey look a bunch of stats about me
Offline
[ Started around 1732741915.637 - Generated in 0.108 seconds, 10 queries executed - Memory usage: 1.65 MiB (Peak: 1.87 MiB) ]