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

SE Moth and Pteranodon data mixed up/unnecessary in ark_data.json #25

Closed
mitfry opened this issue Sep 15, 2017 · 4 comments
Closed

SE Moth and Pteranodon data mixed up/unnecessary in ark_data.json #25

mitfry opened this issue Sep 15, 2017 · 4 comments

Comments

@mitfry
Copy link

mitfry commented Sep 15, 2017

Hello!

I noticed this in ark_data.json:

{
"package":"/Game/ScorchedEarth/Dinos/Moth/Moth_Character_BP_Base",
"blueprint":"Moth_Character_BP_Base",
"class":"Moth_Character_BP_Base_C",
"name":"Pteranodon"
},
{
"package":"/Game/ScorchedEarth/Dinos/Moth/Moth_Character_BP",
"blueprint":"Moth_Character_BP",
"class":"Moth_Character_BP_C",
"name":"Lymantria"
},

Ptera's don't exists on SE. Either the name of the first part is incorrect or it can be removed altogether, correct?

@Qowyn
Copy link
Owner

Qowyn commented Sep 15, 2017

Seems like I'm missing a filter for _Base stuff in my extraction program. Moth_Character_BP_Base is like a prototype thing for the real moth, and it seems WC copied the Pteranodon to create it. And then they didn't change the name because that thing will never be seen in the game.

So yeah: it shouldn't be in there.

@mitfry
Copy link
Author

mitfry commented Sep 15, 2017

Thanks for the reply Qowyn!

Glad I was able to point this out. Might make the extraction results a little better :).

Basically we stumbled upon some code leftovers from a lazy WC dev? ;)

@Qowyn
Copy link
Owner

Qowyn commented Sep 15, 2017

Should be fixed now. Also added missing data from Ragnarok.

Maybe a lazy dev, but then again you will never see that creature in the game unless you spawn it in.

@mitfry
Copy link
Author

mitfry commented Sep 15, 2017

Thank you for the update!

I'd say this issue is now solved :)

@Qowyn Qowyn closed this as completed Sep 15, 2017
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

2 participants