Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Thank you so much Mr. AntvasimaOkay.
@AKM sama @DontTalkDT @DarkDragonMedeus @Mr. Bambu @Just_a_Random_Butler @Agnaa @Celestial_Pegasus @Wokistan @Ultima_Reality @Elizhaa @Qawsedf234 @ByAsura @Sir_Ovens @Damage3245 @Starter_Pack @Abstractions @Colonel_Krukov @SamanPatou @GyroNutz @Firestorm808 @Everything12 @Maverick_Zero_X @Crabwhale @GrathOfLux @Dereck03 @Planck69
We seem to need your evaluation help here.![]()
Negation refers to the ability to nullify or deactivate certain properties of an object or target, such as in the form of Durability Negation or Power Nullification. The effect of Negation can be categorized as:
1. Temporary: The nullified property returns to its original state after a certain period.
E.g.: Nullifying a barrier temporarily, allowing a character to pass through it until it is naturally restored to its prior function.
2. Permanent: The nullified property is removed entirely.
E.g.: Nullifying a barrier permanently, such that it will not be restored naturally.
Negation directly deactivates or nullifies a target's properties, either for a limited time or permanently, depending on the capabilities of the user.
Bypassing, in contrast, avoids interacting with a target's properties entirely. To reiterate the prior example: bypassing a barrier could involve going around the barrier without directly influencing the barrier in any form. This has similar consequences to Negation, as the property of the target in question can be ignored by the user. However, whereas the Negation of a defensive property may be resisted, Bypassing may be capable of circumventing this resistance by avoiding interference with the property as a whole.
I'm doing what DontTalkDT recommended me to do and I also asked him if he could help make it in-line with the Hax page as he's the best person for this, about the recomendations I don't think I could help much generally as English isn't my main language but I'll do try to fix the grammatical errors.We talked briefly about my thoughts on the topic in the previous thread, so to reiterate - I wouldn't be opposed to this change if we can be adequately and agreeably clear on when a feat would fall under negation and bypassing. I think the circumstances that would fall under the latter would be niche and specific, but I feel it would only be a positive to specify its existence and the implications of such circumstances in practice. I don't personally the explanation confusing, but it's worth checking with others to see if any clarifications may be useful.
I would, however, make recommendations for changes to the proposal blog, both to fix some grammatical errors and for general clarity and professionalism in-line with the rest of the Hax page:
Yeah, I could add two notes for it, though I don't know how to make the notes really in-line with the hax page (Like Note 1 & 2 on the page). Do you think you could help with that?A problem I see here is that we use the "durability negation" for abilities of which 80% probably bypass durability, rather than negate it.
I think in the rule text one can just switch "negation" to "nullification" (as in power nullification) to make the difference more clear. Maybe add a note as well, that durability negation can refer to either.
Interesting question is if a note of such a nature is better put on the hax page or, in rewritten form, on the power nullification page, to warn that bypassing should not be listed as power null (which is the problem with the separation I have seen most frequently).
I'm content with this suggestion, yes. And I think it would be useful to include such a note on both the Hax page and on the Power Nullification page, in forms appropriate for the contents of each page, to explain these concepts. It is relevant to both, after all.A problem I see here is that we use the "durability negation" for abilities of which 80% probably bypass durability, rather than negate it.
I think in the rule text one can just switch "negation" to "nullification" (as in power nullification) to make the difference more clear. Maybe add a note as well, that durability negation can refer to either.
Interesting question is if a note of such a nature is better put on the hax page or, in rewritten form, on the power nullification page, to warn that bypassing should not be listed as power null (which is the problem with the separation I have seen most frequently).
Okay, but can you help me with the revision in-line? I don't really know how to do that like Note-1 and Note-2.I'm content with this suggestion, yes. And I think it would be useful to include such a note on both the Hax page and on the Power Nullification page, in forms appropriate for the contents of each page, to explain these concepts. It is relevant to both, after all.
@Valxxroyz More input should be provided on this matter before any changes are made - but if you wish, you can adjust your draft with these matters in mind and bring it back here for review. If you would like any specific help with doing so, you may contact me on my message wall.
I'm not quite sure what you're asking for help with. If it's a formatting question, the Note 1 and 2 on the page just use bolded text for formatting.Okay, but can you help me with the revision in-line? I don't really know how to do that like Note-1 and Note-2.
I don't mind helping with that, but preferably draft-working should be brought either to my message wall or to DMs to avoid cluttering the thread.Oh, sorry, I need help with wording and the structure for the page.
I can't point to a specific discussion off the top of my head, but I am actually fairly certain this has been brought up before. I'm quite confident there have been contentions before about whether durability/power negation should be applied for an ability which bypasses a mechanism as per the above definition. It just hasn't been structured as a proposal for an adjustment to the Hax page specifically.It is not feasible to enumerate all the different ways that such abilities could operate, and this distinction clearly isn't a particularly obvious one, given how it was never a matter of discussion until now.
There are just too many cases, at a similar level of notability/relevance, such that indexing all of them in this way would be a massive headache. Since this example doesn't stand out from the crowd (as I think our updates to Resistances about how different kinds of higher infinities affect that sort of thing did).We don't need to add every distinction, you're right. But this would be a helpful one to specify by any angle I can think of it from. I think it would just be a clarification with clear benefits and no particular deficits.
This is not unique. Off the top of my head, some similar situations are:I also don't think it's much of a point against the usefulness of the distinction anyway, even if it hadn't been a topic in the past. I think this is a distinction with a lot of practical backing behind it: it realistically has notably different implications for resistances to common abilities in practice, but it is also a subtle enough distinction that it could easily be misclassified (and likely has been before) on profiles, and reading the pages as they currently exist does not give an intuitive impression of how we are supposed to handle these distinctions on profiles.
Sorry for late response, i think with this distinction, it could help other who's not good at english. I've met so many people that still don't understand between the Nullification & Bypass, while those 2 words has different meaning and mechanism.I think we need more discussion; not everyone agreed on whether this was a good distinction to make.
@DontTalkDT @Agnaa @GrathOfLuxSorry for late response, i think with this distinction, it could help other who's not good at english. I've met so many people that still don't understand between the Nullification & Bypass, while those 2 words has different meaning and mechanism.
What do you think?(well giving a note on the Power Nullification pages could work i guess, or we can just put it on the general HAX pages)