|
|
Post by mikiex on Apr 30, 2014 16:59:39 GMT -5
Veccy Bird source code Veccy Bird 1.5 SourceNow please remember this is the first game I wrote and first ASM code I've ever written - so do not expect a masterpiece  I'm slightly embarrassed by the sate of it, but thought I would release the source code anyway. Its also commented for me... so doesn't explain stuff fully or anything, there maybe unused memory locations, commented out stuff etc. |
|
|
|
Post by jfmateos on May 1, 2014 0:56:30 GMT -5
Thank you very much for sharing it
|
|
|
|
Post by Rapetou33 on May 1, 2014 11:52:28 GMT -5
Thanks a lot ! That is really useful !
|
|
|
|
Post by cNp on May 1, 2014 14:59:58 GMT -5
Thanks MikieX, will be good to read through!
cNp
|
|
|
|
Post by christophertumber on May 1, 2014 18:34:54 GMT -5
Oh, hai, thanks for the shout-out in credits! I think your code is considerably neater and more readble than mine. I typically only have one .I file. For Spectre it's hardware I/O macros. That and sparse coding makes it fun resurrecting code I haven't looked at in 6 or 7 years |
|
|
|
Post by mikiex on May 2, 2014 6:48:24 GMT -5
Oh, hai, thanks for the shout-out in credits! I think your code is considerably neater and more readble than mine. I typically only have one .I file. For Spectre it's hardware I/O macros. That and sparse coding makes it fun resurrecting code I haven't looked at in 6 or 7 years Well thanks, I don't think I would of ever started without reading your tutorial. A long time ago in the 80s my brother tried to explain Z80 to me when he was learning it and I didn't really take much in. Back then I really only learned basic , but since that time I've learned many languages and concepts about computers through my work in games (though my jobs is not a programmer). So when I read your tutorial it explained it very clearly and concisely , I thought that actually Assembly really isn't as complicated as I thought it was back in the 80s. Maybe I could actually write something, so thank you for that. Well I'm not sure about neat code, certainly not optimal and there is probably the odd .I file that is not even in the game One thing I didn't want to do is ever go back to the code, so I made sure I finished it |
|
|
|
Post by christophertumber on May 2, 2014 7:54:40 GMT -5
One thing I didn't want to do is ever go back to the code, so I made sure I finished it |
|
|
|
Post by Rapetou33 on May 2, 2014 9:04:41 GMT -5
This thread gives me the opportunity to thank you, Mr Tumber, for your very useful and clear tutorial |
|
|
|
Post by xefned on May 6, 2014 14:24:04 GMT -5
Thank you for sharing. I can't wait till the day when any of this makes sense to me! |
|
|
|
Post by christophertumber on May 6, 2014 14:38:20 GMT -5
Thank you for sharing. I can't wait till the day when any of this makes sense to me! How can we help? |
|
|
|
Post by xefned on May 6, 2014 17:17:48 GMT -5
OMG. That makes my day. I've avoided asking questions up until now to keep from being annoying. So thank you. Next time I get totally stumped, I'll take you up on the offer. Only after I've absorbed both tutorials as fully as possible. |
|
|
|
Post by christophertumber on May 6, 2014 17:31:45 GMT -5
Oh, yeah, def post. Just try to keep questions focused (why is this opcode not behaving like I expect it?) not broad and open ended (how do I program a game?). Since you're just getting started most of your questions sould be really quick and straightforward to answer.
|
|
