For Riot stuff - they only allow for non-commercial use. So anything official that we hose here does not use the default to licensing.
This image is copyrighted to Riot Games Inc.
However, Riot Games allows the use of their League of Legends intellectual property as long as certain conditions are met, as stated in their Legal Jibber Jabber policy: "you can use League of Legends IP as the basis for a fan project that you're giving away for free or that's only generating ad revenue [...]"
We believe our usage also falls under U.S. fair use law because:
It does not limit the ability of the owner to profit from the image in any way.
It is used solely for the purpose of providing illustration and a guide to Riot Games' products.
Great news. I just noticed that the new champion Kai'Sa has a lot of similarities with one of my champion concept: Aerith, The Scrap Genius. I am glad that Riot saw potentials in my concepts, and used them to develop a new champion. I want to thank you for creating Suggestion Wiki - it's such an amazing platform for post ing our ideas.
I do a mixture of all three things that Teh suggests.
Either put it on the mainspace and get over the fact people will see it in a WIP state, or post it in your userspace and it'll be hidden from the Recent Activity. I would generally only use a blog if it requires communal input.
"When first released on the PBE, only Lethal Tempo's bonus was supposed to exceed the cap. However, the effect disabled the cap instead. This was stated to be a bug and was fixed, but at some point the fix was reverted. It is unknown if the revert was intentional, but at present there is no cap on attack speed while Lethal Tempo is active."
You do not have permission to edit this page, for the following reasons:
- You are not allowed to execute the action you have requested.
- This page provides interface text for the software, and is protected to prevent abuse.
Btw, it's an inline style, so we shouldn't edit it in Common.css like this.
3. (New) The image is also 'broken' as you see above.
I see you have a permission, can you check the following style:
I am the lead admin over at the much smaller, much quieter 100% OJ wiki, and I was curious how exactly you were able to design the Announcements box on this wiki. From what I can tell, what you've done is effectively created a tabber that uses images as tabs, which is something I deeply desire, albiet for a very different purpose than on this wiki. Normally I can figure how most codes work without asking the creator, but in this case its simply too complex. I get that you have template:announcments->announcement/modules->announcements/Hot->annoucements/3 (& announcements/4, etc) but even after adding these pages to my wiki for testing purposes (to later be edited), the images still do not change whats on the page. (only the first button and "other news" should work at this time and it does not change) Any advice would be very much appreciated.
Thank you for your time, and here is a link if you would be willing to help or at least look at it. If not, I can understand that too, as your time is your time.
I just added that .js to my userspace on the Orange Juice wiki and it's working fine, unless I'm missing the issue. Could you describe the problem? Did you remember to import the script into MediaWiki:Common.js? Simply adding the CustomTab.js page won't suffice.
To the clarify the problem: the template renders correctly with the image tabs like its supposed to, and if you hover over the images, they correctly says what link the image should open on the page. The actualy problem however is that if you press any of the images, the template does not reset and change which announcment is under it. (I have made the other announcement templates: 3,4,5,hot,etc).
In short, it looks correct but the announcment displayed on screen never changes. No matter what button is pressed, it will always show the "latest update" section. It will not display "Teaser" or "Promotions", ect when other buttons are pressed.
Yup! That did it, thank you so much! I honestly don't know I passed that since I specifically looked for importJS after he mentioned importing but I somehow missed the page- must have typed it in wrong or forgot the "mediwiki:" portion. And now I feel a lot dumber...
Anyway, thank you guys both so much for spending your time to help me, and for sharing the information with me- I really appreciate it, and I will try to put the new fucntionality to good use on my wiki as well.
Maybe that would be a better term for the CC, since Kassadin/Viktor's effects are technically blocked by crowd control immunity. Is it actually distinct from a silence though, out of curiosity? In slowmo, does it not even briefly grey-out abilities?
But then we still remain with another problem: Assume that Interrupt stays as it currently is, what used to be is named Disrupt, what then of a tip to define disabling spells?, for those cases of "ability-inhibiting crowd control disables this effect", as it helps now Impairment to the cases of "movement-inhibiting crowd control disables this effect".
Well, I've reworded Interrupt to be more similar to how I worded Immobilize. I could rename the crowd control info to say "Disrupt" instead of "Interrupt" and use Disrupt as the Immobilize equivalent, then re-use Interrupt for the CC-type... or I could just leave those two abilities as special cases. -shrugs-
Personally, if it is to find a middle ground, "Disrupt" should be the Immobilize equivalent, "Interrupt" should be the quality of CC and grant a name to the disabling of channels/charges... the names I currently think off are "Muting" and "Defuse".
Its a solution, not the best, but one nonetheless.
I cannot easily/speedily confirm via mobile, but I presume you created dispel? Bad choice of name. While you have identified a buzzword I’ve forgotten to create, that word is already used in League (as well as other games) to mean something wildly differently.
I’ll rename it to Disrupt and then create a proper Dispel. I don’t know why you want three words for it, though. One word can be used as an adjective and a noun - an Interrupt interrupts. Or maybe...
Disrupt and Disruption being separate would work, or Silencing. I honestly didn’t notice a different between Disruption and Interrupt on my phone. My bad for deleting it, then. It just looked like Interrupt without the movement part.
I’m tempted to rollback to use “Interrupt” to refer to all.
I went to add “Disarm interrupts basic attacks.” and had a vision of the future where you would want a new term to describe attack inhibiting effects. You also stated that “Mute” “interrupts abilities”, which is wrong - Mute, as you’ve invented, is the status of being unable to cast. 1) Nothing interrupts casting except death. 2) That is already called “Silence”.
Interrupt refers to the exclusive ability to interrupt channels.
It would make more sense to update all other crowd control effects to list their compounded nature - eg Stun combined the effect of Silence, Root and Disarm, not that a Silence and Stun are in some made up new category. Well, not a new category, but a new word to describe it. Silencing, disarming and immobilising are perfectly fine terms.
It would make more sense to add, for example: “The following effects also Silence.” to the bottom of Silence than to create new pages.
Silence - Cannot cast.
Root - Cannot move.
Ground - Cannot dash.
Disarm - Cannot attack.
Nearsight - Cannot see.
Knockdown - Interrupts dashes.
Interupt - Interupts channeling.
Other effects just combine these. I mean, it’s not perfect - suppression adds “Cannot cast Summoner spells.” But I really dislike inventing new words completely out of thin air (including, in retrospect, my own handling of Interrupt). My goal was more, for example, effects like Fiora that says “if immobilized” or on channeled abilities adding “if interrupted”.
I had to call it Mute because the name used on the Wikia on the Crowd Control page, Disrupt, was now put yet again into the CC. Disrupt should be the ability-inhibiting CC term much like Immobilize is to movement-inhibiting CC, as those are the names in use. If the problem is how the tip its described then feel free to rephrase it.
And the name Mute... I didn't came with a better name, and Interrupt is already in use, so had to invent one. >->
I see myself capable of saying "Want a new term to describe attack inhibiting effects" if it wasn't because there's only a single case. Wouldn't be bad, just not think is time for it yet.
Also, if Interrupt should only reffer to channels and charges (which is already what the CC does, the initial problem of this threat), why does it have section to what interupt dashes and blinks? For a moment was hesitant to create a tip for what interrups mobility.
And that I think of it, wouldn't the Crowd Control tip be more beffiting to cover "Quality of CC", rather than hijacking a tip in use for that (Interrupt)? Is a pop-up meant to describe CC, and detailing what it can disable and/or interrupt would make more sense.
Currently the problems sits in that there's two tips for the description of CC that could be fixed with one, because right now we have one for what CC is (Crowd Control tip) and for what CC does (Interrupt tip), and rather than create a second tip hijacked an existing one in the process that required to create a new tip to cover the loss.
I think we disagree on what the problem is. There was never a “loss” that needed replacing. There’s only two examples of “interrupt” as a type of CC, and both of them are described on their pages as “interrupts channeled abilities”. There didn’t need to be a tooltip for them specifically. I created the “buzzword” Interrupt because there’s many examples of “interrupt” being used as a buzzword (including in every cctip) - and is listed in most channelled abilities, too. The point of tip is “interactive glossary” not “database interfacing”. There was a need to describe what is meant by “interrupt” on every channelled ability - namely what enemies can interrupt you.
I conceded adding Disrupt (initially) because Kassadin and Viktor would still be improved by listing counters to their Interrupt - although that could have also been done by adding a note to Silence saying “An Interrupt a weaker version that only disrupts channels, but does not inhibit casting.” similar to how Polymorph is noted on Pacify. As an aside, “Mute” refers to not being able to speak, and so is not a synonym for being interrupted. How I used “Disrupt” in the above example is why it’s a reasonable synonym and why I swapped them around.
I really don’t see any need to add an Immobilize equivalent for casting - firstly, “silencing effects” already covers it, and secondly because there’s nothing that current interacts with silencing effects (except, maybe, Lucian’s Culling - but only insofar as it doesn’t interact with them).
But yes, an alternative would be to update Crowd Control to have “The following interrupts casting; the following interrupts dashing; etc”.
But is unstoppable different from immunity, in that inmune units cannot be affected at all while unstoppable still tick down the timer of negative effects, such way that if the effects last longer than the unstoppability does affect them?
I would rather refer to the immunity as Unstoppable, due to Unstoppable Force and Unstoppable Onslaught. The crowd control article uses "deferral" for the other kind of immunity, but I'm pretty certain that list isn't accurate/the description isn't quite correct. Warwick doesn't "arrive stunned" when he ults, 'cause otherwise he would be stunned while channeling - seems someone just added all "unstoppable" skills to the referral list, even though I'm confident Riot only mentioned a few specific ones would defer.
That list would need testing before I'd be willing to commit to a term.
Supposedly the difference lies in that Inmunity doesn't allow application and is unaffected, while Unstoppable/Defferal allows application but the unit is unaffected until the buff runs out. But fair enough, is better to test than jump into conclusions and do a tip for the sake of it.