All Projects

Trac Ticket #58 - Originally reported by: Korrode

Right now there is a “Stackable” entry for each item in the DB. This has to be set manually atm. If not set correctly it can make the allocated slots info output from the “status” command look confusing. (i.e. more than 36 slots allocated. 36 is maximum in EL).

Please make the bot determine if an item is stackable and set it as such.

Until that is done, if you can be bothered, remove “Stackable” column from WBI and allocated slot info from “status” command output.

Trac Ticket #67 - Originally reported by: Krayon

Bot causes exception when it fails to receive online players list. This can happen if the connection is reset for example (”Connection reset by peer”).

Example:
urllib2.URLError: <urlopen error (104, “Connection reset by peer”)>

Trac Ticket #68 - Originally reported by: Krayon

When the bot fails to connect to the server, or the connection is severed, the bot causes an exception.

Example:
socket.error: (110, “Connection timed out”)

Trac Ticket #75 - Originally reported by: Krayon

The WebAdmin should keep access logs with login/logout etc and times they occur. Perhaps even what modifications took place.

Trac Ticket #82 - Originally reported by: Krayon

Some bots have more than one owner. We need to ensure that they can ALL use owner commands etc. The owner list should therefore be something like a comma separated list. Alternatively it COULD be an Admin table attribute or a separate table. Either way it should be easily known if a player is an owner.

Trac Ticket #86 - Originally reported by: Korrode

Add total item gc value to “status” output.

(display gc bot would have if all items sold)

(currently running v0.10.0045)

Trac Ticket #87 - Originally reported by: Anonymous

Would be nice if we had the option to have bots add /bot name inv/wanted at the end of each advert. this wouldnt take up much space on #jc 3 adverts.

In light of FS#95, it would be good to have the ability to forcibly kill the bot no matter what state it’s in. It would also be useful if the bot had better monitoring and handling of itself ( FS#97 ).

The bot startup script should better monitor the state of the bot and kill it if necessary. See FS#95 and FS#96 regarding this also.

Seems the client paths for 3D objects has changed to a flat directory vs the old tree style. Maps will need to be modified.

Currently, when the user issues a tell/ask command, the bot doesn’t parse out any punctuation IMMEDIATELY following the nick. This should be done for characters that are illegal for IRC nicks ( TODO: verify this list ).

The built dist package is named “ratslap-0.2.0.tar.gz” regardless of architecture.

Would be nice to be able to save and load profiles.

QB#118 shows that unrecognised parameters (such as “button5”) fail silently,
assigning 000000h instead of reporting an error.

We should have a musl build for a lean standalone binary version.

Change “Getaway thing” to “Sand bomb” and make it so when you flee off opponents they can’t move/attack for 2 seconds, and when you use the “Sand bomb” they can’t move/attack for 5 seconds.

Sand bomb can have 60 sec cooldown (to start with, it may come down a little)

Equipment should support being degraded. At the moment we have break percentages but once these kick in the item is simply lost. We should support the item transitioning to another state, optionally allowing for a modification of it’s stats.

Creature’s can currently spawn anywhere within their given rectangle. This includes levels that aren’t necessarily possible to get to or from (say for example, a table). This means the creatures are currently taking up a useless slot, limiting the number of creatures people can fight, and using up unnecessary thinks, trying to find a way out.

Placement should be more intelligent, perhaps opting for something within a few height levels of norm, or of the spawns center.

We need storage fully functioning. The design for categories isn’t decided as yet. User defined perhaps? The problem with custom is the tediousness of defining each item’s category (unless you have it manual category selection but that’d suck).

The mode names should be simpler than “F3”, “F4” and “F5”. They were only named
this way as that was the hex code for the mode, hardly user friendly.

As we get players, we will get trouble makers, that much is already clear. We need the ability to ban users for a configurable amount of time, as well as preset amounts. These SHOULDN’T effect the forum bans however a ban on the forum SHOULD be a ban in game also (I think).

Something like this might do:

#ban PLAYERNAME [[[Y:]D:]H:]M REASON

eg.

#ban testuser 1:4:6:3 Because you're a tool

This would ban ‘testuser’ for 1 year, 4 days, 6 hours and 3 minutes because he’s a tool. He would be informed of such when trying to login.

Other examples:

#ban testuser 5 Come back in 5 minutes when you've learned to behave
#ban testuser 7:0 You're gone for 1 week buddy!

Should we support banning per player or per forum account (given that 1 forum account can have multiple players)?

Should we have pre-sets like: #ban7 for 7 days, #banwarn for 1 hour, #banladen for life?