XPath Error Checking

Ever wonder what's wrong with your xpath? Why it just doesn't work right? Curious what your "new" xml's look like after an edit?

1. F1 to bring up the console.
   
2. exportcurrentconfigs to export the configs.
   
3. appdata/7DaystoDie/Saves/<worldname>/<savegamename>/Configs is where they export to
   

...this way, you can check out what the xpath changes are ACTUALLY doing to the xml's.

 

[Bipolar Bear]

Good to know, thanks for posting this!

 

[Red Eagle LXIX]

I also use this URL which allows one to narrow by Text or Node the found result for checking the Xpath before application:

http://xpather.com/

 

[Guppycur]

Ooh nice red.

 

[Guppycur]

Please sticky, but in tutorials.

 

[Sinz]

Wow, I was wondering why this wasn't a thing. Turns out it is.

Thanks for that Guppy

 

[Quantum Blue]

Guppy / RE: Both are very helpful. THank you very much.

As a 7D2D noob modder, this really would be awesome in the tutorial section. (As Guppy suggested.)

Thanks

 

[stasis78]

If you are on OS X then I highly recommend pathology. It’s on the App Store and only a few bucks. You can check your xpath against the vanilla config files very quickly to see what it’s matching.

 

[Robeloto]

Very useful! Thanks for this!

 

[Kartoffeluser]

Good to know Thx

 

[khzmusik]

+1 for making this sticky, it's incredibly useful.

 

[njugul]

Just get "XML Tools" for N++ and use the "Evaule Path" function.