I'll be more specific.
Doger is a tutorial. It's there to help people get a leg up, a super-simple project that puts the basics of rb+ in the context of a simple working project. The idea is to read through all the tutorials and view Doger as a simple demonstration of the things you read about previously, then maybe use it to play around with things, chop it up, change things around, see how your alterations affect the game as it is played - a bit of a simple sandbox project to fanny around in.
What Doger isn't is a project to cut & paste without understanding any of it, swap the assets out of and claim it as your own game.
If you had worked through the tutorials and gained even a very basic understanding of what the simple routines in Doger actually do, your issue would stand out like a sore thumb and there would be no time wasted making youtube videos and making posts, you'd be on with making "your" game.
I find it quite sad and somewhat disheartening to see you here asking such questions, posting the project including .BAS file that demonstrates that I was correct in thinking that you'd done nothing much to the code other than managing to break collision detection and introduced other issues... and now you're back here wanting people to write the game for you.
Well that's just not in the spirit of things, is it?
You've now sold 8 copies of "your" game on eBay at $20 each. I have a solution.
Cancel that listing. Promise to not be a dick anymore and not sell other people's work as your own. Take that $160 and donate it to the ACLU. Post the receipt here.
A short while after you do all that, I'll post the fixes to "your" game and you'll be able to have 2 frogz running around the screen.
I'm not being a dick.
Honestly dude do you think I'm out on the beach right now eating caviar with supermodels from Frogz 64 DEMO sales?
If it's such a simple game, Why are you so offended by me using it as a starting point for something BETTER?
You are right it is a tutorial at heart. Which makes it BROKEN as a game. I intend to fix it. It was your collision that was off that I also intend to fix.
Guess what? The tutorials aren't very helpful AT ALL. They even say in the text they are not very technical. I would think that the people responsible for creating RB+ would be a bit more friendly to people wanting to use it for their projects? Let me be a little more specific... Dude do you want ME TO PAY YOU FOR THE BROKEN DOGER GAME BEFORE GOING ON?????
Since I have had to hear about your blood, sweat and tears over this thing I am trying to improve you say I added nothing... It took 7 hours to make that intro sequence and then several days to incorporate it into this game. I have gotten many compliments on the intro and am even helping another AA member make their own intro now.
I'm sorry to say this sh3-rg but I have learned a lot. You see RB+ doesn't have that magic swap assets button you seem to be under the false impression that it does.
There is nothing wrong with asking questions, isn't that how you learn? Did it say anywhere that we were NOT allowed to use the tutorials as a starting point for our own projects? I mean shit maybe I'm just stupid, maybe I need you to upload a RB+ rulebook.
It can start out like this
Rule #1
we will show you a little bit how to do stuff, but do NOT copy our method come up with your own!
Rule #2 we will insult you if you ask too many questions or plan to ever make any money
One more thing:
' ****************************************************
' * REMAINING GLOBAL VARIABLES USED IN DOGER GAME *
' ****************************************************
DIM p1delay% : p1delay=0 ' player 1 movement delay
DIM p2delay% : p2delay=0 ' player 2 movement delay
DIM framecounter% : framecounter=0
framecounter++ ' Add 1 to the frame counter. It ticks over as screen refreshes.
p1delay++
p2delay++
VSYNC
I wont make the mistake of "coming around here asking for help" anymore
Edited by Jeffrey_Bones, Tue Feb 14, 2017 2:14 PM.