Skip to content
TORNLIFE More

What did Chedburn say about chaining?

Chedburn's chain comments in the sources are mostly short forum replies: the chain report's best-hit statistic is not a bug[1], the attack auto-timeout is hard to synchronize and is better long than short[2], and the chain timer could be shown on the attack screen but would be hard to build[3]. Most of the rest are bug-triage questions.

Design and feature comments

  • April 2020: Chedburn suggested the chain timer could show on the attack screen beside the chain count, e.g. "56 (04:32)", by changing the 5:00 attack timer to seconds. He expected it would not be simple, as the live-updating chain system would need rebuilding.[3]
  • December 2022: he said the chain report's "best hit" statistic is not a bug or issue. There is not enough space for a "Best non-bonus hit", and he likes that it shows the highest bonus achieved.[1]
  • August 2022: on a chain that broke when a 30-second timeout took 34 seconds, he said it is very difficult to synchronize the timeout perfectly, and that it is preferable for it to run slightly longer than to time out before it says it will.[2]

Respect and chain length

In March 2018 a player argued that the new respect update hurt low-level factions. Chedburn asked whether a faction of new, low-level players was producing total respect 39% less than a veteran HoF faction on a chain of the same length. It was a question, not a ruling.[4]

Bug-triage replies

  • January 2018: he asked whether faction members' hits were not increasing the chain.[5]
  • February 2021: he asked whether overseas raid hits were not registering as 'Overseas' in chain reports.[6]
  • April 2023: he explained that the chain report API has two errors. One means the chain existed but the report was pruned, the other that the chain does not exist. He saw no harm in keeping them separate.[7]

Chaining 2.0 (2017)

A player thread from 7 November 2017 says Chedburn stated that Chaining 2.0 would be released that day. This is second-hand, not a Chedburn post.[8]

No Chedburn announcement or patch notes on chain mechanics, and no statement on chain abuse, hit farming or chain watching, were found in the sources. Other staff members are not covered.

Current
The latest chain comments found are from 2023, on the chain report API errors.
Historical
Comments run from 2017 (a second-hand Chaining 2.0 relay) through 2018 respect and bug replies and 2020 to 2022 design replies.
Change
No Chedburn post in the sources announces a change to chain mechanics.
Sources 8
  1. Developer Best Hit Chain Report Statistic Redundant — Chedburn ·
    Why TornLife says this
    I don't think this is a bug nor an issue. There's not enough space to fit "Best non-bonus hit" nor who would have made it
  2. Developer chain broke even though it should not of — Chedburn ·
    Why TornLife says this
    It's very difficult to synchronize it perfectly, and obviously it's preferable to have it slightly longer if necessary rather than timing out before it says it will.
  3. Developer [250 R+] Chain count on attack screen — Chedburn ·
    Why TornLife says this
    The chain area could say "56 (04:32)" perhaps. Although I expect it would not be simple, as I think we'd need to rebuild the live updating chain system to achieve it.
  4. Developer Faction Wars even more Unfavourable to New Players — Chedburn ·
    Why TornLife says this
    Are you saying that a faction of new / low levelled players is producing total respect of 39% less than a veteran HOF faction on a chain of the same length?
  5. Developer Issue Caused By Latest Changes — Chedburn ·
    Why TornLife says this
    Bugs & Issues · Chedburn [1] (developer) · 2018-01-26 Hmm, I have no idea how that could be possible. You're saying your faction members made hits but they were not increasing the chain?
  6. Developer chain report not counting overseas — Chedburn ·
    Why TornLife says this
    Bugs & Issues · Chedburn [1] (developer) · 2021-02-06 I'm not 100% clear on this, are you saying that overseas raid hits were not being registered as 'Overseas'? Thanks.
  7. Developer Inconsistent API error results for chain reports — Chedburn ·
    Why TornLife says this
    One error is to say that the chain did exist, but the report has been pruned, the other error is to say that the chain doesn't exist at all.
  8. Forum From Ched Himself — Surge ·
    Why TornLife says this
    According To Chedburn He says Chaining 2.0 Would be released today.

On TornLife

More Ranked Wars answers ›