Maintenance for YAGL?
Posted: 02 Nov 2023 12:58
I would like to gauge how many people are actively using YAGL and how much demand there is for maintenance. I would be very grateful if any occasional or regular users would respond to this post.
I created YAGL some years ago because I was fascinated by the NewGRF specs and thought I might make something a little more user friendly than NFO/grfcodec. NML is clearly the way to go for new GRFs, but YAGL seems to have a niche for older GRFs written in NFO or for which the original source is lost. There wasn't a lot of interest (nobody asked for it, but I had fun doing it), so I basically just stopped working on it and moved to other projects. I'm grateful to those who have contacted me now and then with various issues, but this has been a very slow trickle. This post was prompted by the most recent query. I think I got to pretty much complete coverage of the specs as they stood at that time, but naturally they have evolved a bit. I'm not an active OTTD player at the moment and, perhaps a little ironically, have no interest in creating GRFs myself, so I haven't been keeping up.
I would quite like to make some effort to keep YAGL up to date, as time allows, but I don't think I want to trawl through the specs trying to diff them with whatever version I used in the past. That would be a difficult and tedious exercise. It would be simpler if users made specific feature requests: something in the more recent specs which YAGL doesn't currently handle. Very few bugs have been brought to my attention, but if you have a GRF which won't decode properly, please upload it so I can reproduce the issue. Feel free to open issues on the GitHub project (link below). You can always clone the repo and try out some changes yourself (I hope my code is not too awful).
Thanks.
I created YAGL some years ago because I was fascinated by the NewGRF specs and thought I might make something a little more user friendly than NFO/grfcodec. NML is clearly the way to go for new GRFs, but YAGL seems to have a niche for older GRFs written in NFO or for which the original source is lost. There wasn't a lot of interest (nobody asked for it, but I had fun doing it), so I basically just stopped working on it and moved to other projects. I'm grateful to those who have contacted me now and then with various issues, but this has been a very slow trickle. This post was prompted by the most recent query. I think I got to pretty much complete coverage of the specs as they stood at that time, but naturally they have evolved a bit. I'm not an active OTTD player at the moment and, perhaps a little ironically, have no interest in creating GRFs myself, so I haven't been keeping up.
I would quite like to make some effort to keep YAGL up to date, as time allows, but I don't think I want to trawl through the specs trying to diff them with whatever version I used in the past. That would be a difficult and tedious exercise. It would be simpler if users made specific feature requests: something in the more recent specs which YAGL doesn't currently handle. Very few bugs have been brought to my attention, but if you have a GRF which won't decode properly, please upload it so I can reproduce the issue. Feel free to open issues on the GitHub project (link below). You can always clone the repo and try out some changes yourself (I hope my code is not too awful).
Thanks.