All Projects

Trac Ticket #39 - Originally reported by: Krayon

The WebAdmin interface should support configuring discounts for players and guilds.

Trac Ticket #40 - Originally reported by: Krayon

WebAdmin should support configuring of responses.

Trac Ticket #43 - Originally reported by: Krayon

The WebAdmin interface could include the ability to view messages as stored in the Messages table. This contains a history of messages sent to/from players using the bot’s “msg” command ( and maybe messages sent via the messaging system developed in #12 (FS#66) too ).

Trac Ticket #49 - Originally reported by: Krayon

WebAdmin fields should perform (better) data validation, such as alpha/alphanumeric/numeric etc.

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 #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 #84 - Originally reported by: Krayon

As listed in #77 item 3, a list of the bot’s current inventory would be useful. You could therefore see exactly what it has on it. Potentially, the items list could have a column for currently holding and have a toggle for “only show items currently in inv”.

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

Trac Ticket #41 - Originally reported by: Krayon

WebAdmin should support the viewing of transaction history.

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.

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.

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

From https://github.com/krayon/ratslap/issues/2 :

https://github.com/jpotier wrote:

  I may be tired, but I don't get how to set say key 1 to my button G4.
  Actually, apart from calling
      ./ratslap -p f3-5
  I don't understand how you actually set a modified mode. Should I edit the
  source code and recompile?

https://github.com/thomasluquet wrote:

  Same thing, for me, the documentation it is not really clear for me...

  BTW, i try to make a draw of the mouse and the buttons, is it ok ? (i can
  send you the .odg if you want)

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.

From GitHub Issue #9 by adrfantini:

I have a very weird behaviour here. After having modified many buttons to
suit my needs, I have the following problem.

I cannot assign many software mouse Buttons to many hardware buttons.
Assigning keys seems to always work tho.

Say I am in this situation:
...
  sudo ratslap --p F3
  Left Click (But1):   Button1
  Right Click (But2):  Button2
  Middle Click (But3): Button3
  G4:                  
  G5:                  
  G6:                  
  G7:                  
  G8:                  ModeSwitch
  G9:                  DPICycle
...
Now let's try to modify it with:
  sudo ratslap --modify F3 --G4 Button4
Result:
  sudo ratslap --p F3
  Left Click (But1):   Button1
  Right Click (But2):  Button2
  Middle Click (But3): Button3
  G4:                  
  G5:                  
  G6:                  
  G7:                  
  G8:                  ModeSwitch
  G9:                  DPICycle
Nothing! Let's try assigning keys instead:
  sudo ratslap --modify F3 --G4 LeftAlt+K
  Left Click (But1):   Button1
  Right Click (But2):  Button2
  Middle Click (But3): Button3
  G4:                  LeftAlt + K
  G5:                  
  G6:                  
  G7:                  
  G8:                  ModeSwitch
  G9:                  DPICycle
Works...

In short, I can seem to bind mouse Buttons anymore!

However, some, like sudo ratslap --modify F3 --G7 Button9 work, while others,
like sudo ratslap --modify F3 --G7 Button5 do not.

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.

QELServ needs to be the BEST ... just BEST ... ever!

Summary says it all :)

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.

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

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

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.

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.

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

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

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

Once we have parties ( FS#45 ), we will be able to have party drops.

4 ways this can be done:

1. You drop many bags around with % of loot, first in best dressed.
2. You drop 1 bag but when a player takes items, it gives a % to each in the party instead of all to the one.
3. You don’t “drop” at all, just allocate items straight to the party members.
4. Drop 1 bag. But once it’s picked up, all other party members automatically get a bag under their feet, opened, containing their % of the spoils.

Whilst the most complicated, the 4th option sounds the most attractive and flexible from a player perspective.

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.

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.

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.

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.

When you move in eq potion with cooldown visiblity of cooldown dissapear, but it still has cooldown.

Dropping an inventory item on to an equipped item, should swap with that item. Undecided as to whether it should swap with what you drop it on, or the equipment of the same type you have equipped (ie if you drop a sword onto a shield, should the new sword swap for the shield or your existing equipped weapon).

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

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

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.

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)

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

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.

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

NPCs buying and selling needs to work betterer (and completely).

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?

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

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.

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.

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