superfurrycat

Apprentice
  • Posts

    6
  • Joined

  1. The use of /bug is something of a bugbear - no pun intended - for me. From a user perspective logging a bug with /bug takes roughly the same steps, and has roughly the same effect, as writing the bug description to a file in a text editor and then immediately deleting it.

    You fill in the bug details, submit it ... get a "bugged kthxbye" message and that's the last you ever hear of it.

    Does anyone read the bugs? Do they get sent to the devs? Do they get prioritised in any meaningful way? Zombie_Man extols the virtues of /bug but as a user I see nothing to back that up. BaB's post is the only evidence we ever see that anything actually happens to these bugs.

    Take the slashchat bug which was recently fixed (hurrah). I /bugged it immediately when I saw it, which was immediately because I always remap / to chat in every game I play. I'm pretty sure I bugged it on test before that issue went live. Months went by before I saw anyone mention having the same problem and then magically it was fixed.

    It would be nice if there were some ... any ... acknowledgement of the bugs in the system. Something as simple as an automated in-game email that said "Your bug is a known issue" or "We couldn't reproduce your bug" or "We are working on it" would provide some reassurance that the bug tracker was something other than a giant black hole.

    It should be mentioned that this game is no worse in this regard than any other game I've cared about enough to raise bugs (ie SWG).
  2. Thumbs up for chat bind fix. That's been driving me nuts since I13.
  3. Didn't Statesman mention bases when talking about player apartments? Personally I'd love my own little apartment; I used to spend a huge amount of time tweaking my house(s) in SWG.

    The problem with bases is that it isn't a personal thing any longer. Unless you have sufficient rank in your supergroup you don't have the freedom to personalise your base so even if the base looks cool (and some do) it isn't really YOURS.

    Those who do have the necessary rank to run around editing bases then hit the other sticking point: expense, which has already been mentioned in this thread. And let's face it there isn't really a reason to go to the base other than to use the teleporter or grab stuff from the bin.
  4. I'm ineligible for the contest but I spent too long agonising over my entry to let it drop.

    Resolute
  5. Executive summary
    The lfgset command replicates and extends the functionality of the search status dropdown shown in your team window when you are solo.

    It takes one argument: the sum of one or more numbers viz:
    0: Not seeking.
    1: Looking for any team.
    2: Looking for patrol.
    4: Looking for missions.
    8: Looking for Task Force.
    16: Looking for trial.
    32: Looking for arena.
    128: Not accepting invites.

    Usage
    The lfgset command is used with a status number to set your seeking/not-seeking status. The command takes one argument:
    Code:
    /lfg X
    Here, X is a bitfield. If you understand the term "bitfield" then skip over the next section to see the numbers! Otherwise I refer you to this Wikipedia article where it is explained. The discussion is somewhat technical so I will attempt to give an explanation here. Don't worry if you don't understand it at first! The numbers sections lists examples.

    Please forgive the messed up formatting of the tables below. The migration to the new forum software did not preserve them completely accurately.

    Binary and bitfields
    Remember those binary numbers from school? Where we represent everything as a sum of powers of two (1 2 4 8 16 32...) with each unique power occurring at most once in the sum? For example 5 is 4 + 1 and we write it 101 in binary. The following table may refresh your memory:
    Code:
     4 | 2 | 1  
    ---+---+----
     1 | 0 | 1
    Five is equal to four plus one so we write 1 in the four column, 1 in the one column and the result is 101. Similary 18 could be written 10010: 1 in the sixteen column plus 1 in the two column makes 16 + 2 = 18.
    Code:
    16 | 8 | 4 | 2 | 1 
    ---+---+---+---+---
     1 | 0 | 0 | 1 | 0
    A bitfield is basically a binary number where each 1 is not just a power of two but a checkbox! Imagine you categorised your CD collection by whether or not a song was recorded live, whether it was an acoustic rendition and whether it was a remix. Then you could make a table of your songs like this:
    Code:
    song | live | acoustic | remix 
    -----+------+----------+-------
      A  |   0  |     1    |   1
      B  |   0  |     0    |   1
      C  |   1  |     1    |   0
    Here song A is a remix of an acoustic set, song B is a remix of the original cut and song C is a live, acoustic track.

    But don't these look kinda similar? What if we pretended that the table columns were binary numbers and said A=5, B=1 and C=6? That's what a bitfield is.

    The numbers
    The lfgset command understands the following numbers:

    0: Not seeking.
    1: Looking for any team.
    2: Looking for patrol.
    4: Looking for missions.
    8: Looking for Task Force.
    16: Looking for trial.
    32: Looking for arena.
    128: Not accepting invites.

    So, if you use the command /lfgset 4 you set yourself to looking for missions and if you use /lfgset 16 you set yourself to looking for a trial. You can verify this by searching for yourself in the search box. Remember that the Find Member window sometimes lags and you may not see yourself correctly the first time you search!

    Because the argument to lfgset is a bitfield, however, you can flag yourself as looking for more than one type of team. Up for a TF or trial? TF is 8 and trial is 16 so use /lfgset 24 and you will show up when someone searches using either of those two filters.

    Note that the lowest numbered icon will show up next to your name in the search window. If you /lfgset 36 you will show up to someone searching for an arena opponent ... only with the green mission symbol by your name.
  6. Ruffles here. Surprised to find a link to my shot in an ICQ message from a friend. Glad you all enjoyed it.

    More on the character...