Hi everyone,
I have been reading for a while this message board so I think it's about time that I post something. My question may have been asked many time, for this I'm sorry, but maybe not from my perspective.
First I need to mention that my background is programming but not working for the gaming industry. Like many of you, I would love to develop a game for the nes, but I lack the knowledge in low level assembly for the 6502.
I want to approach the issue from a programmer's perspective. The best way to learn what you don't know is to work on a project with a goal. I'm trying to visualize how to design my application and learn 6502 at the same time from it but I'm not sure how.
I could just make a huge blob, experiment here and there and there is good chance that it would work. That would make me learn 6502 at the same time but my issue with this approach is that is great for testing and R&D but hell to maintain and to scale later.
Maybe with 6502 coding it may be hard to separate in re-usable code module? I saw one example with the Neo-toxin code, which seems to separate in specialized module (I just did a quick glance, didn't look at all of it) but the architecture used with the VM and everything seems over complicated to use for someone that is just starting to code on the nes.
How do you approach the architecture of your game? What drove you to chose this approach over another? Do you put much thought into it or you just try and see what happens?
Thank you in advance for your comments.
P.S> If something I said is not clear don't be afraid to point it out. I wrote this message during a lunch break and maybe my question is very vague because of that.
I have been reading for a while this message board so I think it's about time that I post something. My question may have been asked many time, for this I'm sorry, but maybe not from my perspective.
First I need to mention that my background is programming but not working for the gaming industry. Like many of you, I would love to develop a game for the nes, but I lack the knowledge in low level assembly for the 6502.
I want to approach the issue from a programmer's perspective. The best way to learn what you don't know is to work on a project with a goal. I'm trying to visualize how to design my application and learn 6502 at the same time from it but I'm not sure how.
I could just make a huge blob, experiment here and there and there is good chance that it would work. That would make me learn 6502 at the same time but my issue with this approach is that is great for testing and R&D but hell to maintain and to scale later.
Maybe with 6502 coding it may be hard to separate in re-usable code module? I saw one example with the Neo-toxin code, which seems to separate in specialized module (I just did a quick glance, didn't look at all of it) but the architecture used with the VM and everything seems over complicated to use for someone that is just starting to code on the nes.
How do you approach the architecture of your game? What drove you to chose this approach over another? Do you put much thought into it or you just try and see what happens?
Thank you in advance for your comments.
P.S> If something I said is not clear don't be afraid to point it out. I wrote this message during a lunch break and maybe my question is very vague because of that.