CurseForge.com

CurseForge

1889 - Substitution Token for TOC Interface Version

(I thought i already suggested this - but couldn't find the ticket)

What is the enhancement in mind? How should it look and feel?

## Interface: @InterfaceVersion@

Allow specification of supported interface versions (plural) via the web interface.

This would avoid the bazillion TOC bumps on a patch day - plus its 'opt-in' by nature (since you have to deliberately add it).

Also it allows you to specify that your version works on the PTR in advance of patch day.

I realize that the actual solution would need to allow the working copy to show a valid version as well.

Perhaps add support in the #@debug@ / #@end-debug@ to handle toc keywords by prepending X-, as well as #@no-debug@ / #@end-no-debug@ tokens.

In a working copy

#@debug@
## Interface: 30000
#@end-debug@

#@non-debug@
## X-Interface: @InterfaceVersion@
#@end-non-debug@

In a packaged zip:

#@debug@
## X-Interface: 30000
#@end-debug@

#@non-debug@
## Interface: 30200
#@end-non-debug@

Or something cleaner...

Then in the web interface have checkboxes for each interface version (adding new ones as they become relevant).

User When Change
Torhal Tue, 14 Jun 2011 16:15:23 Changed status from New to Declined
Torhal Fri, 03 Jun 2011 17:04:13 Changed assigned to from None to prencher
Ackis Tue, 01 Feb 2011 18:02:29 Changed assigned to from ckknight to None
sylvanaar Tue, 06 Oct 2009 13:35:27 Changed name from Substitution Toke for TOC Interface Version to Substitution Token for TOC Interface Version
sylvanaar Tue, 06 Oct 2009 13:35:06 Create

You must login to post a comment. Don't have an account? Register to get one!

  • 7 comments
  • Avatar of mikk mikk Fri, 25 Feb 2011 21:14:21

    I don't like full-auto at all, it will just be used when it shouldn't be.

    What the packager COULD do is allow maybe something like this

    ## Interface: 40000
## Interface: 41000

    2 lines. Know about current WoW TOC somewhere centrally and apply some basic smartness + repackage when the central TOC number gets revved.

    We often get testing done on PTRs and can say with reasonable certainty ahead of time that, yes, this will work on the next major patch. Indicating this ahead of time would be useful.

    Personally I'm way too busy actually PLAYING the new patch to sit around and bump tocs when it actually hits live. But if I can tocbump a few days/weeks ahead I might actually get it done :)

    Last edited on 25 Feb 2011 by mikk
  • Avatar of BigRedBrent BigRedBrent Sun, 21 Nov 2010 14:03:32

    This wouldn't even be necessary if Blizzard would add an extremely simple fix on their side: http:forums.worldofwarcraft.com/thread.html?topicId=26850279128

    Check out the addon SpellFlash to help improve your gameplay in World of Warcraft!

  • Avatar of x87bliss x87bliss Thu, 25 Mar 2010 21:35:13

    TOC Version changes don't happen every patch - on the patches they do happen there's usually significant changes to the API which warrant the change.

    A "TOC Bump" should be something performed by an addon author ONLY after testing their addon with the new client version, and not as a method to force the users to test the addon.

    There is plenty of information out there already for end-users to enable "loading outdated addons." Therefore, they should be the ones to enable the option at their discretion, as opposed to being misled by an automated TOC Bumping system.

  • Avatar of sylvanaar sylvanaar Mon, 22 Mar 2010 05:19:25

    Wow -30, i should get an award or something.

  • Avatar of Zasurus Zasurus Sat, 06 Feb 2010 01:46:01

    I think you are correct in that something needs doing about patch day but I think your method is not the right way to go about it.

    I believe the TOC file should remain hardcoded as that is what version THIS version of your addon has been tested on…

    It's there for a reason and I also believe you should use it like it is meant to be used. If your version hasn’t' been tested for the new version then it is a beta (or alpha) so only people who want to take the risk and voluntarily download the beta/alpha test it and people who don't know what beta's are or don't want to take the risk of ruining there raid night because your addon goes tits up on the last boss have the old version automatically disabled by the patch (which is why it does un-tick the load out of date addons for every new patch). :-)

    ALTHOUGH I DO believe that the current way we deal with patch days is in-surfactant and does cause a panic of patching AFTER the faeces has hit the fan (everyone has the old addon and the new patch so they stop working).

    I have proposed a better way in another ticket: http://www.curseforge.com/projects/curseforge/tickets/2178-suggestion-to-solve-the-problem-of-patch-day/

    Thought I would try to explain why I think everyone will vote -3 to this ;-) Hope I didn't offend you as I LOVE so many of your addons! :-D I can't live without Prat 3.0! Keep up the good work

    Zas

    P.S. I HAVE read this ticket before and it had -3's all on it then so I guess you got voted into the bin last time as well ;-)

  • Avatar of Ackis Ackis Tue, 06 Oct 2009 20:52:48

    I voted a -3 for this. The ToC is meant to state which game this works for, etc... the ToC changing on patch day isn't a huge issue IMO.

    I'd rather stick with the hard code ToC than run into the issues associated with auto-updating it.

  • Avatar of sylvanaar sylvanaar Tue, 06 Oct 2009 13:45:50

    Admittedly this is more useful for addons which work on multilple interface versions.

  • 7 comments

Facts

Last updated on
14 Jun 2011
Reported on
06 Oct 2009
Status
Declined - We decided not to take action on this ticket.
Type
Enhancement - A change which is intended to better the project in some way
Priority
Medium - Normal priority.

Reported by

Possible assignees

Votes (Total: -57, Average: -3.0)