Can we only have the people who helped make "wbb" respond please in this thread. ;)
Yea, i have a couple problems. First, it will only open the same open game over and over. So, when you type '---- mapo' it will only host one certain game, no matter how many maps i have set in there to work. Second, it wont say the server the game was killed on.
Example:
[15:31] <Renbot> osbot mapo
[15:32] <Saiyan> hello
[15:32] <Osbot> The map could not be found, starting random map.
[15:32] <Osbot> Baringi.map @ winbolo://24.166.157.6:27503 - open
[15:32] <Renbot> osbot kill 27503
[15:32] <Osbot> ack! ya got me! Renbot just killed port 27503 on
Another example:
[15:34] <Renbot> osbot mapo
[15:34] <Osbot> The map could not be found, starting random map.
[15:34] <Osbot> Baringi.map @ winbolo://24.166.157.6:27507 - open
I would like to know how i can fix the random map generator, and to mention the server the game was killed on..
regards,
-Ren
renbot.winbolo.us
That could be for debugging purposes, SuicidJky. If not, users are easily able to take it out of the script if they fear a backdoor, which I don't think sheeps would do.
well, obviously a regular user such as myself would not have been aware of this unless sj posted it. not to mention it opens up to anyone from dyn.optonline.net .... just gotta change that host mask ... kinda insecure if you ask me, its the kind of thing that should have been turned on if the user requested help in my opinion "here, paste this into this area" Microsoft gets shit for this kind of behavior all the time. "lets make it insecure so our users have a easier time. .... behold the bitching!"
Min
my also interfear with some scripts other ppl use, we all know how bot ppl like to pile every available mirc script into there bot.
bwahah nvm brain fart....
How about adding a feature so that when someone triggers a map they can customize the options, like allowing brains and hidden mines?
How about implementing a command which dictates what version to create the map in? I know some of us dislike playing 1.14 games for whatever reason. I've felt that rushing into a new version or release isn't always a good idea no matter what the software.
From my understanding, it seems like a simple addition. Package the winbolods for both versions, add a couple if-statements, update the documentation and *bam* there you go. The only forseeable problem would involve mIRC hotlinks which can be easily solved by a couple extra lines in the hotlinks script.
So what do ya say?
I have set this up on sheepbot to see the response.
All sheepbot map commands can now be included with "113" at the start to load version 1.13. i.e. sheepbot 113map Dogs Playing Poker, to load a passworded game with the Dogs Playing Poker map.
Since sheeps did his part, now it's time to do mine. I must also ask another favor from ALL bot owners. Please take notice of the following lines.
<Pawnybot> JonnyWar I.map @ winbolo://pawnybot.winbolo.us:27525 - 1.14 strict - password: goodbye
<sheepbot> Chew Toy 3.map @ winbolo://sheeps.winbolo.us:62146 - strict - 1.13 - password: herd
*** Chew Toy 3 @ winbolo://sheeps.winbolo.us:62146 - 1.13 - Strict - Password
That's right; three different forms of output. Although they may all contain the same information, it's just in different output. If someone wants to script something based on the reporting of a game, they would have to code something to make sure it works in three different cases. Anyways, done with my rant, time to post the code.
1) Open up mIRC.
2) Click on the icon on your toolbar that is a green button with "/a" on it.
3) Click on the "Scipts" tab on the box that pops up.
4) Find any code that looks like the following and delete it.
[code:1:81b6d61be9]on ^*:HOTLINK:*winbolo*//*:*:{ }
on *:HOTLINK:*winbolo*//*:*:{..}
[/code:1:81b6d61be9]
5) In it's place, copy the code at the bottom and paste it into your scripts dialog box.
6) Change line #4 to the path of version 1.13 and line #7 to the path of version 1.14.
7) Save it and hit "OK"
8) Double click on any hotlink and it should work as long as the versions are either 1.13 and 1.14
[code:1:81b6d61be9]on ^*:HOTLINK:*winbolo*//*:*:{ }
on *:HOTLINK:*winbolo*//*:*:{
if (1.13 isin $hotline) {
run C:\winbolo113\winbolo.exe $1
}
elseif (1.14 isin $hotline) {
run C:\winbolo114\winbolo.exe $1
}
}
[/code:1:81b6d61be9]
Ahh, very good, Sticks.
And for the occasional person who doesnt look at the code before using it, replace these two lines with the address of the winbolo.exe file, for the different versions:
C:\winbolo113\winbolo.exe
C:\winbolo114\winbolo.exe
If you are not sure where the file is, then I'm not sure how the script will destinguish between v. 1.14 and 1.13.
Jay, thanks for restating my 6th step.
If the users don't know where it is, then that's too bad. They really should learn where they install things to. Users must have both versions installed and installed into separate directories. I'm not sure how the WinBolo install handles installing a new version "over" an old version.
Thanks, sheeps. Not sure how SuicidJky's client reports, also. I'd just like consistancy across all bots with the output looking somewhat like we're used to.
lol........nice script tho!