QDNX Bug Tracker :: https://bugs.qdnx.org/ QDNX Bug Tracker :: QELServ: Recently opened tasks 2012-10-23T17:25:26Z QB#98: Maps don't display properly https://bugs.qdnx.org/task/98 2012-10-23T17:25:26Z Krayon Seems the client paths for 3D objects has changed to a flat directory vs the old tree style. Maps will need to be modified. Seems the client paths for 3D objects has changed to a flat directory vs the old tree style. Maps will need to be modified.

]]> QB#64: Visible no cooldown on potion after moving it in eq https://bugs.qdnx.org/task/64 2010-02-03T13:59:25Z Kain Meiz When you move in eq potion with cooldown visiblity of cooldown dissapear, but it still has cooldown. When you move in eq potion with cooldown visiblity of cooldown dissapear, but it still has cooldown.

]]> QB#63: Channels ACL https://bugs.qdnx.org/task/63 2010-01-28T04:16:02Z Krayon 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. 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.
]]> QB#62: Animations as a result of movement clicks during pending combat https://bugs.qdnx.org/task/62 2010-01-26T15:15:27Z Rob McCathie 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. 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.

]]> QB#61: Global item purge/list/modify https://bugs.qdnx.org/task/61 2010-01-22T23:47:34Z Krayon The ability to purge, modify and list (who has and where) items would be advantageous. It would allow for the easy removal or substitution of an item, on a global scale. Ideally it should handle things like subing a sword for a piece of fruit - which should remove sword, give fruit and stack with existing fruit if req’d. To be able to list all players who are currently in possession of a given sword, and how many etc would be part of this presumably. The ability to purge, modify and list (who has and where) items would be advantageous.

It would allow for the easy removal or substitution of an item, on a global scale. Ideally it should handle things like subing a sword for a piece of fruit - which should remove sword, give fruit and stack with existing fruit if req’d.

To be able to list all players who are currently in possession of a given sword, and how many etc would be part of this presumably.

]]> QB#60: Admin access player storage https://bugs.qdnx.org/task/60 2010-01-22T23:42:42Z Krayon 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 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.

]]> QB#59: Admin access player inventory https://bugs.qdnx.org/task/59 2010-01-22T23:40:59Z Krayon 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. 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.

]]> QB#58: Add lastseen ability https://bugs.qdnx.org/task/58 2010-01-22T23:33:36Z Krayon Add the ability to see when the last time a player was on. This would be a useful feature for players I would think. Add the ability to see when the last time a player was on. This would be a useful feature for players I would think.

]]> QB#56: Add player list command for players https://bugs.qdnx.org/task/56 2010-01-22T23:30:11Z Krayon 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). 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).

]]> QB#54: Add support for banning https://bugs.qdnx.org/task/54 2010-01-22T23:37:27Z Krayon 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? 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?

]]>