• Peter: Event Planning - Part Deux

    Characters: Rittal[85] Mieville[80] Terlan[80] Caltera[67] Dynia[67]
    Created: 2008-10-28 23:31:45 Edited: 2009-04-11 00:52:59

    http://redmine.midnightsyndicate.eu/issues/show/15

    Right so summing up previous posts and ideas. We want an event system, where anyone can create a new event. We want the system to permit people to be invited to a event, also for people to be able to "apply" for an event.

    We want to make position filling easy, so we want to allow characters to be able to be marked as certain types of character, Tank, Off Tank, Healer, DPS, Melee DPS and Casting DPS. Potentially in several, perhaps once dual specs comes in you could have a Priest in Healer, DPS and Casting DPS. Where as a warlock would just be in DPS and Casting DPS.

    Templates would be provided for 5-mans and 10-mans, perhaps even custom templates for Kara, etc.

    5-man example: 1 Tank, 1 Healer, 3 DPS
    10-man example: 1 Tank, 1 Off Tank, 3 Healers, 5 DPS
    10-man example 2: 1 Tank, 1 Off Tank, 3 Healers, 2-3 Casting DPS, 2-3 Melee DPS

    The event organiser can then either invite people, or just leave it open for people to apply. The code or system should contain the ability to have reserves even if they are not used.

    Characters are either invited, or made available to the event by the owner. They are then dealt with by the organiser. The following lists the states a character can be in to the event, and how that can be altered. 

    State          States User Can Change To    States Organiser Can Change To (Before)

    Invited        Accepted / Withdrawn         Withdrawn                              

    Available      Withdrawn                    Accepted / Reserve / Declined          

    Accepted       Withdrawn                    Available / Reserve / Declined         

    Reserve        Withdrawn                    Available / Accepted / Declined        

    Declined                                    Invited                                

    Withdrawn      Available

    A further state of "Participated" exists which all "Accepted" characters are moved to automatically at the end of the event, the organiser can make any character Participated. This may be a flag instead of a state so it can be seen who turned up or who didn't.

    If the user has asked for it, this system can generate a large quantity of email about an event and state changes.

    Users when they put forward characters can specify how much they "want" to do this instance, Mike suggested four levels, I'd come up with three.

    1 - Need (Need a quest)
    2 - Greed (Want loot)
    3 - Available If Needed (Happy to fill a space, but also happy to sit out)

    Until the user is accepted or reserved the user can alter the "want" level.

    Site may be able to suggest who is "more worthy" of going on a run base upon number of previous participated dungeon events, perhaps percentage of those in a period of time they've done, % last week, the most recent one, etc. Using be.imba.hu we could do it on gear if there was a target to meet.

    I think that's everything, comments, etc.

    P.
    "I may not have gone where I intended to go, but I think I have ended up where I needed to be." -- Douglas Adams

    • Peter: Re: Event Planning - Part Deux

      Characters: Rittal[85] Mieville[80] Terlan[80] Caltera[67] Dynia[67]
      Created: 2008-10-28 23:45:35

      Oh yah one other minor little feature is that the characters should be able to write a brief comment to go on when they make themselves available.
      "I may not have gone where I intended to go, but I think I have ended up where I needed to be." -- Douglas Adams

    • Peter: Re: Event Planning - Part Deux

      Characters: Rittal[85] Mieville[80] Terlan[80] Caltera[67] Dynia[67]
      Created: 2008-10-31 13:28:47

      For Dan more then me really as he's looking at this. Table/Data structures:

      Events
      ------
      id
      name
      description
      start
      duration
      dungeon_id
      user_id (organiser)
      guild_id (couldn't decided if this was needed, probably should be optional)
      closed (closed events mean people have to be invited)

      post_id (Forum post that is about this event, probably automatically created, and an adaptation of the forum code to display a short summary at the top of a post. I wasn't sure if this should be on the post, or on the event. The former would be easier for forum display and tracking, but it would mean two forum posts could be about the same event.... which may not be a bad thing.)

      CharacterTypes
      --------------
      Using a nested set we could have structures, i.e. Spell DPS and Melee DPS under DPS as a whole, with Any at the top.

      id
      lft
      rgt
      parent_id
      name

      CharacterTypeCharacter
      ----------------------
      Allow users to specify which character types they are, they inherit those that are bellow their selected one, so Spell DPS gets DPS and Any. Characters could be multiple types... once duel spec comes in, a priest could be Spell DPS and Healer.

      id
      character_id
      character_type_id

      EventPositions
      --------------
      The number of each type needed for a party.

      id
      event_id
      character_type_id
      min
      max

      CharacterEvent
      --------------
      The link of a character to an event.

      id
      character_id
      event_id
      status (Invited, Available, Withdrawn, Accepted, Reserve, Declined)
      participated (Did they participate?)
      want (level of want the user has for this run)
      event_position_id.
      ^^
      I did contimplate a link into EventPositions to say which position you were going in for... Or perhaps it could be nil. Or maybe it's not needed, but if you were filling a big raid it'd be needed I guess.

      Dan if you want to chat after lunch it'd be good to get this right the first time. :)
      "I may not have gone where I intended to go, but I think I have ended up where I needed to be." -- Douglas Adams

    • Carrot: Re: Event Planning - Part Deux

      Characters: Glorif[85] Heclan[73] Nathrezim[37] Cuchillo[23]
      Created: 2008-11-09 13:40:44 Edited: 2008-11-09 13:58:47

      Once again, more for my own sorting-out, mentally, but throw out objections if you have any: 


      Signup State    Set By        Admin Change To              User Change To

      

      Invited         Event Admin   Rejected                     Signed-Up, Withdrawn

      Signed-Up       User          Rejected, Accepted, Reserve  Withdrawn

      Withdrawn       User          Invited                      Signed-Up

      Rejected        Event Admin   Invited                      --

      Accepted        Event Admin   Rejected                     Withdrawn

      Reserve         Event Admin   Rejected                     Withdrawn

      Participated    Event Admin   Rejected, Accepted, Reserve  --

      Wash: This is going to get pretty interesting.
      Mal: Define interesting...
      Wash: Oh god, oh god, we're all going to die?