-
Notifications
You must be signed in to change notification settings - Fork 36
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
Changes in FSD? #39
Comments
I had a bit of time this morning waiting for a hurricane to pass over my area, found out a bit more how reverence works. A lot of it is still over my head, however I have a better understanding of it. There are still a few things that produce errors when it comes to int/uint functions. I've looked at the C code but don't immediately understand what may cause it. I'll open another issue on that later. But, for the icons / graphics themselves, which this issue is about, I noticed this:
This is the iconIDs.schema res file. Note how there is an IDGenerator pointing to a webserver - I am assuming that the client points to this to get the icon information that is missing, and reverence doesn't handle this at all from what I can see. Same with the graphics . I've tried to set up packet capture to capture traffic on this host (10.91.255.3), with no luck so far. |
Heh, that's new. Yeah, the FSD stuff has been broken for a while. It's probably the most complicated part of this whole thing; it's a rather obscure format. Sadly, I currently lack the motivation to invest the large amount of time I'd need to figure out the format again to fix the problems with it (CCP seems to keep changing it, grrr) Also, even if the FSD decoder was fixed, I would not likely make reverence access any game servers. That particular server is clearly not an API for 3rd party developers to use. (Maybe if CCP said it was ok, I'd consider it) |
Yeah, I don't expect for it to get fixed. I am mostly playign around with it and looking at the various formats CCP uses. I am interested to know where this data comes from / is saved though. I feel like it has to be cached somewhere - they wouldn't make an api call every time they need icon info. |
cfg.icons
When trying to fetch icon data (which is specified by reverence as being in FSD format):
Results in the following for the vast majority of the data:
Note that
iconFile
is an empty string. There are entries that are used for clothing assets it seemed, but the values seem to have encoding issues?This seemed to work fine a few days ago. Not sure if the FSD format changed or if the data was moved somewhere else
cfg.graphics
I don't personally use this resource, but I figured I would try to test it. This returns one complete value as far as I can tell, then exception happens:
The text was updated successfully, but these errors were encountered: