All Projects

Creatures move in a very stupid way and inevitably end up stuck and/or blocking paths etc. Whilst paths will be fixed in maps by making them wider, creatures should probably not stop on any narrow area anyway and should, in general, “think” about where they’re going

Channels should have support for simple ACL. They can have a “list” that will function as either a blacklist OR a whitelist.

• First person to join get’s “op” status.
• The channel has a BLANK list, defined as a BLACKLIST.
• op can at any time add a name to the BLACKLIST. By doing so, that person cannot join the channel.
• If the list is empty, op can add a name as a WHITELIST entry, thereby making the list a WHITELIST. From that moment on, ONLY whitelists are allowed to join and anyone (other than op) that is currently in the channel will be removed.
• List can only be changed from WHITE to BLACK when it’s empty.
• op can at any point change someone else to op. They swap effective positions so if the new op was on the WHITELIST then the old op is added and the new op removed (op doesn’t need to be WHITE).

Undecided behaviour:

In the event that the op leaves, one of these should happen:

• the (WHITE/BLACK)LIST is cleared.
• if WHITELIST, the first person in WHITELIST becomes op, otherwise list is cleared.

Trac Ticket #31 - Originally reported by: Krayon

The bot should support the ability to log guild channel (or any channel for that matter), #GMs, #IGs etc for later retrieval by direct interaction (PM) or the web based interface.

Trac Ticket #30 - Originally reported by: Krayon

The bot should have a table of item abbreviations. When someone wants to buy/sell an item, they can then use the abbreviated name for that transaction.

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.

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”)

Despite the changes for  FS#47  the CLIENT doesn’t sent the right number of items to pick up as it expects items in bags to be stacked.

Since stacking in the bag is reasonable, and because it’ll save a client modification at this stage, bags should be made to support stacking of non-stackable items.

If whilst in pending combat state (i.e. you just clicked to attack a player/creature from a few steps away and start moving towards them, but combat hasn’t actually started yet) you click to move elsewhere, just after the combat animations start you then do a ‘step or two’ of the move animation in the direction you clicked, then flick back to combat animations fighting your opponent.

It looks weird and can mess up the rotation of the combat participants.

Admins need the ability to see (and modify) a player’s storage. This would allow them to remove items, add items etc. They would most likely have to use a bag as a go between but that would be acceptable.

Admins need the ability to see (and modify) a player’s inventory. This would allow them to remove items, add items etc. They would most likely have to use a bag as a go between but that would be acceptable.

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)

Trading should support transferring items to/from storage as well as inventory.

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?

It’d be good for players to be able to get a list of who’s online. Perhaps if we require a PATTERN when more than say 20 are on, that would hopefully stop too many people abusing it.

Perhaps the easiest way would be to stop once you get to 20. So:

#online

Would list ALL the players if there were ⇐ 20 online at that point, however if there were thousands, it’d only return the first 20 (in order of Actor ID I guess).

Add the ability to see when the last time a player was on. This would be a useful feature for players I would think.

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 ).

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.

At the moment, all actors can see all other actors on the map they are on. Instead they should have a limited range of vision.

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

( from: http://qelserv.quadronyx.org/forums/index.php?topic=15.msg318#msg318 )

If you attempt to flee during combat preparation and actually succeed, the battle still takes place.