Page 13 of 32 FirstFirst ... 3 11 12 13 14 15 23 ... LastLast
Results 121 to 130 of 314

Thread: Two Crazy Random Summer

  1. #121
    Developer Veracity's Avatar
    Join Date
    Mar 2006
    Location
    The Unseelie Court
    Posts
    12,090

    Default

    Revision 19269 fixes reward parsinbg for the Accordion Thief Nemesis quest in the Barracks.

  2. #122

  3. #123
    Developer Veracity's Avatar
    Join Date
    Mar 2006
    Location
    The Unseelie Court
    Posts
    12,090

    Default

    Thanks! Revision 19270.

  4. #124

    Default

    Revision 19263 gets rid of the manually inserted "Clownosity" bitmap modifier and replaces it with the desc-parsed "Clowniness" numeric modifier.

    The former was 1 or 2 (or 3, although that did not work), whereas the latter is 25, 50, or 75.
    You can still maximize for "4 Clownosity".
    You can also maximize for "Clowniness".
    The green side pane still shows "Clown: 2/4", for example.

    Since Clowniness shows up in the item descriptor in TCRS, clown items will now have the appropriate modifier.
    (This means I have to manually add "Clowniness" to the appropriate items for all the data files submitted before I submitted this. Sigh.)
    Originally Posted by Veracity View Post
    Oddness in Clowniness Maximizer: Playing as Sauceror/Wallaby TCRS:
    Or else maybe I don't get the Maximizer...
    I tried "100 clowniness" and got +5000, etc. I tried "clowniness" and got actual values. I tried 1,000,000 clowniness and got 50,000,000 clowniness for items...

    I don't see this with clownosity, and it seems to interfere with the "stop once you get to 100" part of it...

    clownosity_-tie.png
    clowniness.png
    1000000_clowniness.png
    100_clowniness.png

  5. #125
    Developer Veracity's Avatar
    Join Date
    Mar 2006
    Location
    The Unseelie Court
    Posts
    12,090

    Default

    Good grief. I'm pretty sure I don't understand the maximizer. Perhaps Darzil would be willing to cast his eyes over this?
    If not, I will look at it when I have enough time to dive deep into it...

  6. #126
    Developer
    Join Date
    Apr 2010
    Posts
    5,134

    Default

    Sounds expected. The number before it is the weighting. So 100 Clowniness means 100x Clowniness.

    What you want, I think, is something like min 100 Clowniness. Not sure if right syntax, as away from PC, but check the help

  7. #127
    Developer Veracity's Avatar
    Join Date
    Mar 2006
    Location
    The Unseelie Court
    Posts
    12,090

    Default

    Looks like "clowniness 100 max" will do it.
    Like Jon Snow, I know nothing.

  8. #128

    Default

    OK, right now there's a entry in the default list of maximizer items for 4 clownosity, -tie. Should we replace or augment that with clowniness 100 max, -tie

    I did check the help.
    Clowniness is different from what's in the help for "Other Modifiers".
    The only bitmap modifiers that currently appear useful for maximization are Clownosity and Raveosity, so they are allowed as a special case. 4 clownosity, 7 raveosity are the defaults checked for if no value is given.

    It then talks about Beeosity but not Surgeonosity.

    For Clownosity, putting a number in front of the item is interpreted as the max. For Clowniness, the number is unhelpfully multiplied.
    X Clownosity = Clownosity X max, equip <Item> (+1)
    X Clowniness = Clowniness, equip <Item> (X x 25 per Clownosity).

    So it looks like the special case from "-osity" effects isn't being used by Clowniness.

    I tried to run it the other way, .01 clowniness max 4, but it looks like it has rounding errors.

    When I get there in this new run, I'll look at surgeonosity. At this point in the run, it's not working. I recall it not working when I was in the hospital before, if anyone gets there first...

  9. #129

    Default

    Sauceror, Wombat. This should finish out the Sauceror/Gnome combinations.
    TCRS_Sauceror_Wombat.txt
    TCRS_Sauceror_Wombat_cafe_booze.txt
    TCRS_Sauceror_Wombat_cafe_food.txt

  10. #130
    Developer Veracity's Avatar
    Join Date
    Mar 2006
    Location
    The Unseelie Court
    Posts
    12,090

    Default

    OK, right now there's a entry in the default list of maximizer items for 4 clownosity, -tie. Should we replace or augment that with clowniness 100 max, -tie
    Originally Posted by MCroft View Post
    We could. But we don't have to; I left Clownosity in for backwards compatibility. It's no longer a real "bitmap" modifier, but is derived from the "numeric" modifer, Clowniness. It should work as before.

    Clowniness is different from what's in the help for "Other Modifiers".
    Clowniness is not a "other" modifier. It is a "numeric" modifier. Clownosity is now a pseudo-modifier which behaves like a bitmask modifier.

    The only bitmap modifiers that currently appear useful for maximization are Clownosity and Raveosity, so they are allowed as a special case. 4 clownosity, 7 raveosity are the defaults checked for if no value is given.
    That is still true.

    It then talks about Beeosity but not Surgeonosity.
    Surgeonosity is a numeric modifier, like Clowniness. Therefore, you have to use things like:

    surgeonosity 4 min
    clowniness 100 in

    So it looks like the special case from "-osity" effects isn't being used by Clowniness.
    Correct. Clowniness is a regular numeric modifer. It's a percent, just like Item Drop, Initiative, etc.

    When I get there in this new run, I'll look at surgeonosity. At this point in the run, it's not working. I recall it not working when I was in the hospital before, if anyone gets there first...
    Yeah. I just got there. It was already a numeric modifier, but we weren't parsing it out of the item descriptions. That means it didn't get added to the TCRS adjusted modifiers.

    I fixed it in revision 19273 and fixed the (22) already submitted class/sign data files.

    This is interesting, in that if your local file exists, we will not fetch a new one from the svn repository. That was intended to allow you to have a more recent local file take precedence over one in the repositry, but it's not what we want in this case.

    On the other hand, I noticed that Sauceror/Packrat seems to have been generated with a very early version of "derive" which didn't get all the modifiers, due to KoL HTML errors. I'll start a run in that, by and by, and will subnit the corrected file - but after I derive until I submit, I will not want the repository file to overwrtie my file...

    So, sometimes the repository file is better (updated) and sometimes the local file is better.

    Pondering.
    Ph'nglui mglw'nafh Cthulhu
    R'lyeh wgah-nagl fhtagn.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •