I've updated and ported the Whompa module I originally wrote for IGN bot to BeBot.

The Whompa module has three options:
<pre>whompa cities: Displays a list of known cities
<pre>whompa <city>: Shows the whompas for that city
<pre>whompa <origin> <destination>: Calculates a route from the origin city to the destination city.

* The whompa plugin does not use the Jobe whompas.
* The whompa plugin does not use the grid

Cities can be specified using either the city name or the zone.  The regex used to identify cities and zones was originally the one from Kuren's Helpbot (I believe) but I've done some tweaking over the years.  There may be some common abbreviations for locations which are not included in my match rules.  I don't play an Omni char so I don't know the short-hand used for all of those locations.

For example, either of these commands should work:
you: !whompa oa bor
bot: Old Athen -> Tir -> ICC -> Newland City -> Borealis :: Details

you: !whompa mmd ent
bot: Newland Desert -> Newland City -> ICC -> Omni Trade -> Omni Entertainment :: Details

The module color-codes the cities by Faction based on the colors used for whompa routes in the Atlas of Rubi-Ka (formerly CSPMap), but this feature isn't working correctly at the moment.

The attachment includes the module (a php file) and the help (a txt file).

Let me know if I've missed something.

POD13

*EDIT* 5/17 -- Fixed commpre bug.

The Jobe whompas aren't included by design.  I'm on the fence about adding them, you know, because of froobs.

The Omni route to The Longest Road is in there named, The Longest Road.  This should cause much grief to clanners.  If I'm looking for a route the TLR I really want to go to Bliss but since cities are matched before zones that won't happen. I should rename the Omni route to TLR to Omni-Tek Mine and then a request for TLR will match both Clan and Omni routes.

My define_tablename() has 3 args, but theres only 2 here... are you using another function that I dont' have?

SVN version only got two parameters, $name and $prefix. If you got $suffix there you got the version I used in the beginning, just change $suffix) to $suffix = "false") then.

It should work with 0.2 too, do you have rights management implemented? Then you got to enable the command (didn't check source code of the module myself...).

I posted my first version of rights management somewhere, which allowed enabling and disabling of commands per user group.

But if you don't know about it you most likely don't have it in your bots

No clue what's the problem then, sorry.

yes, this is what i get

To [Eobot]: !whompa
Eobot: Try /tell Eobot !help !whompa
To [Eobot]: !whompa cities
Eobot: Try /tell Eobot !help !whompa
To [Eobot]: !whompa city
Eobot: Try /tell Eobot !help !whompa
To [Eobot]: !whompa bor
Eobot: Try /tell Eobot !help !whompa
To [Eobot]: !whompa bor oa
Eobot: Try /tell Eobot !help !whompa
Cheers,
Tony

Is this defined in 0.2.x?

Code: [Select]

$this->bot->compre

It's $this->bot->commpre in both versions.

Ok, I have a similar problem to that one that tonyuh had.

I am running bebot 0.3.4svn and have dropped the whompa.php into the cutsom/modules folder. When I do a help in the bot I cannot see the whompa command anywhere. When I try and run it in pgmsg the bot just echo's the char name that issued the command and then sends the char a tell to request help from the bot.

I am new to v3 and the new rights management system but from what I could see from the DB the minlevel for the whompa command is guest.

If you need any more info I will happy to provide what I can.

Thanks in advance

Fija