Reply to Re: Removing/changing limits in the source code
If you don't have an account, just leave the password field blank.
Yes, I am aware of the backwards compatibility problems that would originate from changing the source code. But, what I'm suggesting is having a seperate version of Dink that we would create with the community's needs in mind. Any d-mod that would be created with this new version would then of course require people to install this new version of Dink on their computer. The goal would be to make the best possible version we can with the possibility of expanding it when needed, so that everyone will eventually switch over, especially those of us starting new projects or for the beginners. I had high hopes for DinkHD to be this version, but unfortunately many limits still remain and the game itself fails to run for some of our community members. It would defeat the point of creating something for the community if some productive members can't even use it.
It is true that we can swap graphics in and out, in fact I do this all the time for my own d-mod in production. At this point I have 5 scripts working towards managing this process, because I already have a library of graphics integrated in the d-mod that far exceeds 999. Let me tell you, managing this is HELL. Also, the init() method can not be used to change or add lines to the dink.ini file that are not load_sequence commands. Therefore changing transparency or attack frames, etc... can not be done in this way. The ultimate goal would be to make everything easier and less of an obstacle for d-mod development in general. Plus, everyone loves "shopping" around for graphics. It is true that the editors would need to be adjusted, but in this case I believe it would be a simple number change (for WDE+).
I would have absolutely no problems betatesting these changes for long periods of time. I would really LOVE to see this happen and am 100% comitted, but unfortunately my programming skills in C are severely lacking for me to lead this project. But I would like to be a part of it for sure and do whatever I can to contribute.
It is true that we can swap graphics in and out, in fact I do this all the time for my own d-mod in production. At this point I have 5 scripts working towards managing this process, because I already have a library of graphics integrated in the d-mod that far exceeds 999. Let me tell you, managing this is HELL. Also, the init() method can not be used to change or add lines to the dink.ini file that are not load_sequence commands. Therefore changing transparency or attack frames, etc... can not be done in this way. The ultimate goal would be to make everything easier and less of an obstacle for d-mod development in general. Plus, everyone loves "shopping" around for graphics. It is true that the editors would need to be adjusted, but in this case I believe it would be a simple number change (for WDE+).
I would have absolutely no problems betatesting these changes for long periods of time. I would really LOVE to see this happen and am 100% comitted, but unfortunately my programming skills in C are severely lacking for me to lead this project. But I would like to be a part of it for sure and do whatever I can to contribute.
