All Projects

A party system where you can “party up” with people and go on missions together. Perhaps an NPC interface that allows you to select the people from those around you for your party or something.

NOTE: Different to guilds ;)

The channel system needs to be checked to confirm everything is working properly (active channel might not be working correctly for example).

When equipping an item that is stackable (and you have more than one), it equips ALL of that item, not just one.

If a player takes multiple of a non-stackable item, in one go, from a bag where they are stacked, their carry capacity gets screwed. ATM this is only causing an issue with #airdrop but could potentially cause other issues if we choose to allow bags to be non-stack exempt.

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.

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

Implement a trading system allowing players, NPCs and Creatures to trade items (client has existing trading window).

At some point the client should be “cleaned” of all the truly ridiculous RAW_TEXT scraping code and changed to support simple server messages. These will eventually interfere with “normal” functionality.

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

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

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

Quote from: collardhills on 2008-11-13, 02:50:29

It seems if you click somewhere, and someone/thing is next to you, or gets in your way (even in an open map) you just stop, until the thing moves. On main server, you move around the object/person whenever this happens. Could you implement the same thing here?

This is indeed the case as no actor checking occurs while navigating at this point.  At least not until it finds an actor in the next square in sequence.

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.

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

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.

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.

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)

If you attack someone in a PK area, and whilst in the PENDING fight state they leave the PK area, server lag occurs as the server tries to initiate combat.

At present, the original configuration is lost once you modify the modes of the
mouse. An option to return the mouse to it’s factory defaults would be
advantageous.

First seen on 2010-11-14 23:28 EST (UTC - 5:00), from the error log:

File "/home/qelbot/adversary/bot.py", line 848, in process_pm
  price = get_selling_price(requestor, item_name)
File "/home/qelbot/adversary/bot.py", line 1773, in get_selling_price
  my_db.execute(sql,(v.guild, item))
File "/home/qelbot/adversary/database.py", line 44, in execute
  self.cursor.execute(sql, args)
File "/usr/lib/python2.6/site-packages/MySQLdb/cursors.py", line 173, in execute
  self.errorhandler(self, exc, value)
File "/usr/lib/python2.6/site-packages/MySQLdb/connections.py", line 36, in defaulterrorhandler
  raise errorclass, errorvalue
_mysql_exceptions.OperationalError: (1267, "Illegal mix of collations (latin1_swedish_ci,IMPLICIT)
and (utf8_general_ci,COERCIBLE) for operation '='")

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?

When the bot has an empty inventory, it will continually loop. It’s particularly bad as you can’t stop it from the WebAdmin and it spams the server with reconnect after reconnect.