Anonymous | Login | Signup for a new account | 2025-06-21 13:51 UTC | ![]() |
My View | View Issues | Change Log | Roadmap | All Projects Issue Support Ranking | Rules | My Account |
View Revisions: Issue #1799 | [ Back to Issue ] | ||
Summary | 0001799: Overhaul of the join queue | ||
Revision | 2014-05-10 03:29 by Watermelon | ||
Description | The join queue we currently have works, but is quite limited (especially in the way of team stuff). As I'm trying t solve another ticket, the join queue's limitations are getting in the way. I figure instead of adding more code to correct for the current mess, I would re-write it from the ground up in a properly structured class. This leads to four things: 1) Code clarity and new ease of use 2) Allow me to do another ticket without adding more hacky stuff on top of the current implemtation (see linked ticket) 3) Allow saving of positions in line, which annoys people who are waiting to get into (for example) a duel server for 20+ minutes and accidentally timeout/disconnect [this occurs more frequently than one would think] 4) Can be used in the event system now easily (see linked ticket) |
||
Revision | 2014-05-10 03:35 by Watermelon | ||
Description | The join queue we currently have works, but is quite limited (especially in the way of team stuff). As I'm trying to solve another ticket, the join queue's limitations are getting in the way. I figure instead of adding more code to correct for the current mess, I would re-write it from the ground up in a properly structured class. This leads to four things: 1) Code clarity and new ease of use 2) Allow me to do another ticket without adding more hacky stuff on top of the current implementation (see linked ticket) 3) Allow saving of positions in line, which annoys people who are waiting to get into (for example) a duel server for 20+ minutes and accidentally timeout/disconnect [this occurs more frequently than one would think] 4) Can be used in the event system now easily (see linked ticket) |
Copyright © 2000 - 2025 MantisBT Team |