Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Damage Source Whitelist not working #4

Closed
Luke616 opened this issue Feb 20, 2019 · 3 comments
Closed

Damage Source Whitelist not working #4

Luke616 opened this issue Feb 20, 2019 · 3 comments

Comments

@Luke616
Copy link

Luke616 commented Feb 20, 2019

Hello,

I love how NoDamI makes faster, lower-damage weapons viable. However, for my personal tastes I'd like to force some damage sources (such as IE wire or magma blocks) to respect damage immunity. Unfortunately, I can't seem to get the dmgSrcWhitelist to work properly - wondering if there is a bug here?

Screenshot of my NoDamI config. The sources circled in red are not giving i-frames in game
image

Testing with IE razor wire
2019-02-20_14 11 33

As the razor wire is not giving i-frames, I die instantly. Here is debug mode telling me the damage source, confirming that it is the same as what I entered in the configs
2019-02-20_14 11 49

Versions:
minecraft 1.12.2
nodami 1.2
forge 14.23.5.2808

Thanks for your time! Please let me know if you need any additional information.

  • Luke
@ProfHugo
Copy link
Owner

Hello, sorry for the late response. I tested it myself with Immersive Engineering's wires, and the whitelist does work for me. Can you send me a copy of your config file? It could be due to invisible spaces/newline characters (my if statement checks if the names are exact so spaces would throw it off).

@Khioni
Copy link

Khioni commented May 1, 2019

@ProfHugo - I have been able to get it to work just fine, no glitches here; no end spaces or extra new lines.
I think it might be a case of extra spaces throwing things off, since the screenclip doesn't seem to show any excessive blank lines, but it could have already been fixed with v1.2.1

@ProfHugo
Copy link
Owner

ProfHugo commented May 9, 2019

I'll be closing this for now.

@ProfHugo ProfHugo closed this as completed May 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants