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.
So about a week ago I had an idea...
Hey, I should remake this so it isn't terrible!
Announcing...
LuaBot 2.0 is in the works, and is availible on GitHub
LuaBot 2 features several improvements over the original...
(Mostly complete) An actual GUI
(Partially complete) An on-screen reference you can click on to insert a reference
(Complete, still adding events) A full event-based structure instead of every script for itself
(Complete) Ability to pause, kill, or re-open running scripts in the editor.
(Complete) An established, well-developed code base for interacting with EE, plus a degree of futureproofing, both from BotBits.
(Unstarted) A debugging system which allows you to pause a script, then explore it's global environment in a dropdown TreeView
Because let's face it, the original was pretty terrible, for both user experience and codemanship/maintainability.
Links!
GitHub: https://github.com/uniquegamer522/LuaBot-2.0-Reborn
Releases: https://github.com/uniquegamer522/LuaBo … n/releases
SomeMost users have been experiencing problems with missing DLLs, we've released a patch to hopefully fix this.
Issues:
Official first release coming once I work out a few minor bugs with MoonSharp not correctly converting types for some of the functions. This has been fixed, forgot to register a few of BotBit's extension classes.
Application crashes immediately on startup. A patch has been released to hopefully fix this, but it's been unconfirmed. If it's still crashing on startup, please check your event viewer logs
See the GitHub readme for basic API references.
FAQ:
Q: The Open/Pause/Stop buttons aren't working! A: Please make sure you double click on a script entry, highlighting it isn't enough. Same goes for the player menu (e.g. kicking)
Q: Something's broken or doesn't work as expected! A: Report it on the GitHub page issue tracker
Q: How do I save scripts? A: Currently there's no file IO, you'll have to save your scripts using a text editor and copypaste.
After approximately a long time of being idle...
I've finally found the time, energy, and inspiration to begin...
Announcing...
the long-awaited sequal..
with an actual GUI...
event-based system instead of threads...
..nope never mind out of inspiration. I'll be back in another month or two.
It's here: LuaBot 2.0! (Hopefully we fixed that missing DLL problem)
Offline
Won't run.
Offline
That's interesting, i'm not sure what would cause that. What version of .NET are you running, and if you run it through a commandline, is there any sort of error shown?
Edit: I've reproduced this on another computer, and I think I screwed up and published the debug build without the debug libs. Once my IDE stops being broken i'll send out a release build.
After approximately a long time of being idle...
I've finally found the time, energy, and inspiration to begin...
Announcing...
the long-awaited sequal..
with an actual GUI...
event-based system instead of threads...
..nope never mind out of inspiration. I'll be back in another month or two.
It's here: LuaBot 2.0! (Hopefully we fixed that missing DLL problem)
Offline
Still not working
Offline
That didn't fix it? How strange, I got it working on my test computer.
Do you have anything in your event viewer?
After approximately a long time of being idle...
I've finally found the time, energy, and inspiration to begin...
Announcing...
the long-awaited sequal..
with an actual GUI...
event-based system instead of threads...
..nope never mind out of inspiration. I'll be back in another month or two.
It's here: LuaBot 2.0! (Hopefully we fixed that missing DLL problem)
Offline
It tells me these files that describe the problem
Offline
Hmm, specifically i'm looking for an error related to the program itself. It should just contain some plaintext, with either a stack trace or DLL blame. Unfortunately I can't really do much with dump files because I don't know how :/
After approximately a long time of being idle...
I've finally found the time, energy, and inspiration to begin...
Announcing...
the long-awaited sequal..
with an actual GUI...
event-based system instead of threads...
..nope never mind out of inspiration. I'll be back in another month or two.
It's here: LuaBot 2.0! (Hopefully we fixed that missing DLL problem)
Offline
In an xml dump I found this very important
- <ProblemSignatures>
<EventType>CLR20r3</EventType>
<Parameter0>LuaBot_Reborn.exe</Parameter0>
<Parameter1>1.0.6235.37577</Parameter1>
<Parameter2>588ad212</Parameter2>
<Parameter3>glib-sharp</Parameter3>
<Parameter4>2.12.0.0</Parameter4>
<Parameter5>54f4ff4c</Parameter5>
<Parameter6>1bb</Parameter6>
<Parameter7>2c</Parameter7>
<Parameter8>System.DllNotFoundException</Parameter8>
</ProblemSignatures>
Offline
glib.. glib..
buh... wu..
it's literally right there in your folder screenshot.
C# what are you doing.
Anyway it's late here, i'll see if I can fix it tomorrow :/
edit: Came back, apparently i'm blind and didn't see the spoiler containing the full XML dump.
Probably should have looked at that. Sorry.
After approximately a long time of being idle...
I've finally found the time, energy, and inspiration to begin...
Announcing...
the long-awaited sequal..
with an actual GUI...
event-based system instead of threads...
..nope never mind out of inspiration. I'll be back in another month or two.
It's here: LuaBot 2.0! (Hopefully we fixed that missing DLL problem)
Offline
I've had the problem with Xamarin Studio where you were forced to reference mscorlib.dll on all of your projects. Try adding mscorlib.dll to the output directory.
Offline
This is why you don't pre-release.
One bot to rule them all, one bot to find them. One bot to bring them all... and with this cliché blind them.
Offline
Tomahawk, technically it's the whole reason of pre-releasing, to fix major early bugs.
Anyway, I've got my suspicions it's being caused by not having gtk+ installed, and i'm trying to figure out how to bundle it.
I mean, you definitely don't want to find those bugs in a full release.
After approximately a long time of being idle...
I've finally found the time, energy, and inspiration to begin...
Announcing...
the long-awaited sequal..
with an actual GUI...
event-based system instead of threads...
..nope never mind out of inspiration. I'll be back in another month or two.
It's here: LuaBot 2.0! (Hopefully we fixed that missing DLL problem)
Offline
Tomahawk, technically it's the whole reason of pre-releasing, to fix major early bugs.
Anyway, I've got my suspicions it's being caused by not having gtk+ installed, and i'm trying to figure out how to bundle it.I mean, you definitely don't want to find those bugs in a full release.
First off, a pre-release software is one which has restricted availability. This means that you reach out to a small pool of beta testers and work with them for feedback on features and to help track down smaller bugs.
What you've released to the whole public is pre-alpha, and until it's functional nobody should have it except you. Once it's buggy but working you can choose to stage an alpha release, where you give the software only to other programmers, along with the source code for it.
Having fixed the "major early bugs" internally or in alpha, you can beta-release it to a small number of external testers who have no idea how bots work. You seem to have got confused between beta and pre-alpha, because that download link definitely shouldn't be active right now.
There seem to be a good few bot programmers awfully keen to release their alpha software to external users. The way I see it is that if you have the motivation to code the bot in the first place, then sit down and fix the thing yourself when it crashes.
One bot to rule them all, one bot to find them. One bot to bring them all... and with this cliché blind them.
Offline
First off, a pre-release software is one which has restricted availability. This means that you reach out to a small pool of beta testers and work with them for feedback on features and to help track down smaller bugs.
What you've released to the whole public is pre-alpha, and until it's functional nobody should have it except you. Once it's buggy but working you can choose to stage an alpha release, where you give the software only to other programmers, along with the source code for it.
Having fixed the "major early bugs" internally or in alpha, you can beta-release it to a small number of external testers who have no idea how bots work. You seem to have got confused between beta and pre-alpha, because that download link definitely shouldn't be active right now.
There seem to be a good few bot programmers awfully keen to release their alpha software to external users. The way I see it is that if you have the motivation to code the bot in the first place, then sit down and fix the thing yourself when it crashes.
A pre release is, as the name suggests, anything before a full release, pre alpha is usually the internal development versions.
Also, although the stages you've explained are probably the most common stages of software development, there aren't any hard rules about exactly what each stage consists of, so it is up to whoever is releasing the software to decide what stage it is in.
It would be more important if this was paid software, but as it is free, as long as it doesn't damage anything, it should be fine releasing it to the public.
Offline
A pre release is, as the name suggests, anything before a full release
How is an active, public download link anything less than a full release?
One bot to rule them all, one bot to find them. One bot to bring them all... and with this cliché blind them.
Offline
not a full release, as in all content may have not been implemented yet.
@MAMETCHl on twitter for the pfp artist, @snuffyowo on twitter for the character drawn in the pfp.
Offline
not a full release, as in all content may have not been implemented yet.
My point was simply that if the bot doesn't even run then it's been released far too early. It's the original creator's responsibility to make something functional to start with, otherwise it's just the testers coding the bot for him/her.
One bot to rule them all, one bot to find them. One bot to bring them all... and with this cliché blind them.
Offline
[ Started around 1732393752.6405 - Generated in 0.128 seconds, 10 queries executed - Memory usage: 1.67 MiB (Peak: 1.92 MiB) ]