FutureRP Bug Tracker - Issues

0000137: Dropping in level below the minimum required for an item

Wed, 03 Nov 2010 17:26:55 -0400

I had the feeling this issue was already on the bug tracker, but it seems not.

If a player drops below the minimum level required to equip a certain item, the item should ideally be unequipped.

However, this is not possible most of the times, since there is a possibility that there isn't enough room in the backpack.

Something should be 'tweaked' in order to have items rendered useless instead of un-equipping them, in case the player dropped below the minimum level needed for those particular items.

The information regarding the items' lack of utility would be ideally visible when hovering over them. Something similar to the display on the perishable items.

0000210: Profile description editing / Character count is inconsistent

Tue, 06 Jul 2010 20:07:51 -0400

I am not exactly what causes the count to be incorrect, but that should be inclusion -- or not -- of bbcode tags in character count.

To put it shortly, it is possible to input a description that is said to be shorter than the limit by the front-end, submit it, but receive an error because the backend counts the characters differently, and finds your submission to be too long.

As a note: the error message in this case does _not_ stand out in the interface. For me it is white, as all the other text, and it took me a bit to detect the error. Some distinguishable color on the error message would be nice =)

0000216: Remove CAPTCHA on referral page; replace with more stringent proxy checks.

Tue, 06 Jul 2010 19:51:13 -0400

The CAPTCHA image on the referral page is a hindrance to those using "link exchanges" to garner support for the game and free experience for their accounts.

The incoming potential new players often fail to click the CAPTCHA, leaving the referring player without their reward.

If this security feature is removed, the page is more vulnerable to automation. A mixture of advanced proxy detection and various other tricks will help block would-be exploiters.

0000116: [Feature Request][PMs and forum posts] Choose betwen RTE and plain text editor

Tue, 06 Jul 2010 19:31:26 -0400

[Feature Request]

For the few players who use a non-standard browser which doesn't support the Rich Text Editor, writing PMs and forum posts is a big problem.

To get a linebreak you need to type BR, to get a new paragraph you need BR BR. You can't keep a normal formatting while doing this, it has to be one big annoying block of text.

It would be useful to have a setting somewhere, for instance in member's page >> preferences, where the user can choose the default text-editor: RTE or plain text editor.

0000197: Create Login Page

Wed, 24 Mar 2010 07:59:50 -0400

Create a page which handles the login procedure for existing users. It should provide support for users who have forgotten their password, and a registration link for new users who've clicked the wrong link.

0000202: Implement Pet Kill Functionality

Tue, 23 Mar 2010 11:11:43 -0400

Implement a way for users to kill their pets, effectively removing them from circulation forever.

There should be restrictions on this; perhaps a time-based throttle which prevents a user killing more than X pets per month. This would be primarily to prevent the mass slaughter of unwanted pets.

Killing of pets can be a serious exploitation vector, so detailed logs should be kept to protect the website from distributed kill attacks. Perhaps preventing any user from killing a pet until they have managed to get one into adulthood would be the best avoidance method.

0000205: Implement Pet Pick-up Functionality

Tue, 23 Mar 2010 11:11:29 -0400

Implement a way for users to pick up both abandoned and newly spawned pets, in egg and hatchling stage only.

There should be pick-up restrictions to prevent users stealing everything of worth, and/or overloading the website with their incessant page refreshing.

Picking up items could be throttled with a time-based mechanism, and/or by limiting the number of concurrent pets they can possess.

0000204: Implement Pet Freeze Functionality

Tue, 23 Mar 2010 11:11:15 -0400

Implement a way for users to freeze a pet, thereby preventing any further developments or state changes.

A pet may only be frozen during the hatchling stage - eggs and adults need not be frozen. Frozen eggs could be exploited and frozen adults is needless.

The current sprite image, plus the pet's stage and sub-stage should be locked. The view counters need not be locked, however.

0000203: Implement Pet Abandon Functionality

Tue, 23 Mar 2010 11:11:04 -0400

Implement a way for users to abandon pets they've picked up. Abandoning a pet removes any ownership. If the pet is not an adult or frozen, it should be available for other users to pick up. Otherwise, the pet has actually been "released" rather than abandoned.

0000207: Create Actions Page For Pet Management

Tue, 23 Mar 2010 11:10:20 -0400

Create an Actions page which lists all possible actions available to the user for a specific pet.

This should include, amongst other things:
- Assign name.
- Assign description.
- Kill.
- Freeze.
- Abandon / Release.
- Breed With.

0000195: Create User Profile Page

Mon, 22 Mar 2010 09:51:33 -0400

Create a page which lists the details of a user. This includes, amongst other things:
- User name.
- Custom description.
- List of pets owned.
- Awards and trophies.
- Online status.
- Join date, last online, etc.

0000201: Create Mobile Template

Sat, 20 Mar 2010 19:17:59 -0400

Create an XHTML template, designed for small screens and less powerful devices. The use of Javascript and CSS should be kept to a minimum.

Specific types of mobile browser should be detected and integrated more fully by swapping out style sheets.

For instance, in the case of Apple's mobile Safari, the only real limitation is screen size. There is also a very nice UI design on iPhones that can be adopted to better integrate with the devices.

In the case of an unknown mobile browser, we will attempt to provide some basic CSS styles, but the everything should degrade perfectly to simple non-styled XHTML.

0000206: Implement Pet Sickness (Protection Against Excessive Views)

Sat, 20 Mar 2010 19:16:36 -0400

Implement a series of repercussions for users who appear to be giving disingenuous amounts of views and clicks to their pets.

If the user does not attempt to rectify the situation and/or obscure their pets, they may perish. Lots of genuine views are not exactly bad for the website, as it will usually be funded by advertising.

The detection system could check to see whether the ratio of views (impressions from the sprite image) vs clicks (profile visits) is too steep, which means that the website is serving the sprite image for no good reason and wasting resources.

In addition, if the traffic sources appear to be of low quality, or the pet is merely getting a bit too much attention (from a game-play perspective), a sickness could be triggered.

Punishing users for bringing a great deal of good traffic is not the aim of this system. Rather, encouraging pets to be given the views over time, rather than all at once (for game-play) and preventing cheating or server overloading is the objective.

0000191: Create User Preferences Page

Fri, 19 Mar 2010 11:23:39 -0400

Create a preferences page, to allow the user to change their password and profile description.

In the near future, other options such as email, layout of profile page, etc, may be added to the list.

0000200: Create Standard PC Template

Thu, 18 Mar 2010 13:28:11 -0400

Create an XHTML template, designed for fully-featured web browsers with a standard screen resolution.

Despite being designed for good browsers, the template should degrade very well back to basic non-styled XHTML.

0000199: Create Templating Engine

Wed, 17 Mar 2010 15:48:25 -0400

Create a templating engine capable of detecting the user agent's capabilities and adopting the best template pack for the task.

In particular, it should detect a standard PC browser, or a mobile browser. Because this website will be simple anyway, it should be entirely possible to use only two sets of templates; one for PC, one for mobile browser.

The mobile template pack should use CSS and Javascript to cater directly to Apple's mobile Safari, and degrade to very simple HTML if the browser is really poorly endowed.

0000198: Create Sprite Generator

Wed, 17 Mar 2010 09:46:01 -0400

Create a script which pipes the correct sprite stage/sub-stage sprite to the user, depending on the input URI.

Failure at any point in the process should trigger the script to pipe a generic error image.

This script should also handle a pet's view counters, as a single display of the sprite image counts as a view.

0000196: Create Abandoned Pet Page

Tue, 16 Mar 2010 14:47:02 -0400

Create a page which acts as a spool to feed abandoned pets (non-adult stages) to users. Users should be able to pick up a pet, provided there is room on their profile page.

0000194: Create Pet Profile Page

Tue, 16 Mar 2010 14:47:02 -0400

Create a page which displays the statistics and other details of a particular pet. This should include, amongst other things:
- Sprite image.
- Custom name.
- Custom description.
- Pet-specific caption/description.
- Global pet description.
- Total views, unique views, clicks, unique clicks.
- Actions link for the owner of the pet.
- Lineage and parents.
- Gender, if applicable.

0000193: Create Registration Page

Tue, 16 Mar 2010 14:47:02 -0400

Create a registration page, which is as simple as possible. Currently, no email address will be required, though this may change in the future.

The form should require:
- A user name (<= 25 chars) consisting of [a-zA-Z0-9\_\-]
- A password (<= 64 chars) consisting of any UTF-8 characters.

The registration page should have some anti-bot measures, such as:
- Throttles on the rate/number of registrations per IP.
- Possibly some form of CAPTCHA, eventually.

0000192: Create Home Page

Tue, 16 Mar 2010 14:47:02 -0400

Create a home page which features, amongst other things:

- A brief explanation of the website.
- A selection of newly spawned pets to pick up.
- A registration link for new users.
- A login link for existing users.

0000132: Update Trade Block page to make it more useful

Mon, 08 Mar 2010 18:55:34 -0500

The interface of the trade block is tired and needs an overhaul.

In addition, there is a problem with inactive players clogging up the listings, and some players using it to store excess credits.

These issues will be resolved if the trading system does not remove the assets from a player's account, but checks for them at the point of trade.

There are other alternatives too.

0000169: Create three distinct playable races; artwork & skill sets

Wed, 24 Feb 2010 10:08:42 -0500

We need three good, distinct races for players to chose from.

They need to have a little description, default avatars and a set of unique special skills.

0000161: Add Missing Notifications

Fri, 27 Nov 2009 08:50:03 -0500

There are currently NO notifications for the following events:
- Forming raid.
- Finished raid (incoming & outgoing).
- Guild shout message.

These could be implemented via the generic notifications system, but the sheer volume of such messages might be overwhelming.

In addition, some status changes from raiding are not logged in the guild event log!

0000109: Raiding should force guild members to travel to raiding location

Sun, 08 Nov 2009 11:36:51 -0500

When raiding, guild members must enter the 'raiding zone' which is a radius around the NPC/Territory to be raided.

Each raid has a 'maximum raid party' value which determines the number of guild members that can participate in a single raid.

The leader, or privileged guild member can monitor the positions of guild members, viewing a list of people within the raiding zone.

If there are more than the maximum raid party members in the raiding zone, the leader selects the members he wants to participate in the raid.

Players must be within the raiding zone and active within the last 72 hours to be eligible for raiding.