Quest for Ladida

[Adrian]

Thanks everyone for your comments on my game!

I've added the following as a result of the comments:
1. Color
2. Music
3. More hints

Windows build and source code attached.

 

Quest for Ladida.zip

[bplus]

Color usually good, how about different fonts overlaying a screen image of the land of la-di-da :) or image of that mean old and nasty Sphinx. ;-))

[Adrian]

Color usually good, how about different fonts overlaying a screen image of the land of la-di-da :) or image of that mean old and nasty Sphinx. ;-))

haha.....good suggestions bplus, thanks! wanted to do text-only to save time but of course images can be added :)

[bplus]

Text only can still be jazzed up like with Music background as you mention, so too Image Background.

You might like Steves fancy Ole English font, I think it fits your game. I can't remember if that's in Windows or...

Check out @SMcNeill's recent (Jan?) Calendar.

Is every newbie going to start a new thread when they modify a couple of lines in their game or other code? LOL

I love seeing how games or code evolves, looking at the start of the thread and looking a couple pages down maybe a year later, usually a beautiful sight and evidence of progress (or not).

[SMcNeill]

https://www.download-free-fonts.com/details/70399/old-english-text-mt — link to OLDENGL.ttf

[Adrian]

Thanks guys!

Something like this?

Now to figure out how to put it into the program....lol.

[SMcNeill]

Thanks guys!

Something like this?

Now to figure out how to put it into the program....lol.

A quick tutorial on using OLDENGL.ttf.  (Download from the link above if it's not on your machine -- it's included with WORD, so if you use it, it should already be on your system.)

Code: QB64: [Select]

1. SCREEN _NEWIMAGE(1024, 720, 32) '720p screen, which is standard for most things I do
2. font_name$ = "OLDENGL.ttf" 'Don't forget the path, if necessary!
3. font_size = 32
4. font_style$ = "" 'Unless we just HAVE to, we don't want Old English to be a monospaced font.
5. '                 Remember this distinction, as it CAN affect which commands are available for us to use.
6. 'font_style$ = "MONOSPACE" ' <-- IF we have to have it monospaced, we can use this, but I don't recommend it.
7.  
8. font_handle = _LOADFONT(font_name$, font_size, font_style$) 'get a handle for the font, with size and style set
9. _FONT font_handle 'swap to that font handle
10.  
11. PRINT "Hello World" 'print something to the screen.
12.  
13. 'Now, the one important note when dealing with non-monospaced fonts is with the following:
14. LOCATE 10, 100: PRINT "10-100"
15. 'If you look at your screen, you'll see that we're NOT 100 characters right of the screen.
16. 'Since we don't know exactly how wide any one character is going to be, we LOCATE row, PIXEL instead.
17. 'The 10, 100 in the above says LOCATE "10 rows down, 100 pixels right"
18.  
19. PRINT "Font Width: "; _FONTWIDTH
20. 'Also notice that the above will give us a fontwidth of 0.  This is because, once again, we're NOT using
21. 'a monospaced font.  We're using a variable width font, so there's no standard font width to apply.
22. 'Instead, use _PRINTWIDTH to calculate how much screen space your text is going to use.
23.  
24. PRINT "Hello World "; _PRINTWIDTH("Hello World ")
25. PRINT "I eat Cheese"; _PRINTWIDTH("I eat Cheese")
26.  
27. 'Now, as you can see from the above, those two lines have the same number of characters, but each takes up
28. 'a different amount of space to print to.
29.  
30. 'Now, press any key to see what happens when we DO use monospace with OLDENGL.ttf
31.  
32. SLEEP
33.  
34. font_style$ = "MONOSPACE" ' <-- IF we have to have it monospaced, we can use this, but I don't recommend it.
35.  
36. font_handle2 = _LOADFONT(font_name$, font_size, font_style$) 'get a handle for the font, with size and style set
37. _FONT font_handle2 'swap to that font handle
38. _FREEFONT font_handle 'free the old font to release it from memory
39. COLOR _RGB32(255, 0, 0) 'red text to make the comparison very visible
40. LOCATE 2, 1
41. PRINT "Hello World" 'print something to the screen.
42.  
43.  
44. LOCATE 10, 10: PRINT "10-10"
45. 'No issue with LOCATE like normal.  It's row, column just like usual, but look at how the font looks.
46. 'YUCKY!!
47.  
48.  
49. LOCATE , 10: PRINT "Font Width: "; _FONTWIDTH 'here we can get our fontwidth, as all characters are the same size.
50.  
51. LOCATE , 10: PRINT "Hello World "; _PRINTWIDTH("Hello World ") 'as we can see from these.
52. LOCATE , 10: PRINT "I eat Cheese"; _PRINTWIDTH("I eat Cheese")
53.  
54. _FONT 16 'back to the default font
55. _FREEFONT font_handle2 'free the monospaced font I used above
56. COLOR _RGB32(255, 255, 0) 'Yellow for the finish!
57. LOCATE 30, 1: PRINT "That's all folks!"
58. SLEEP
59. SYSTEM
60.  

Also highlights the difference in MONOSPACE style and NON-MONOSPACE.  For OLDENGL.ttf, I recommend to *not* use monospacing, as it tends to stretch the spaces out to an insane level for the majority of the letters. 

[bplus]

Thanks guys!

Something like this?

Now to figure out how to put it into the program....lol.

Oh man! Exactly how I pictured it except for font radiating hazy golden beams. :)

"Now to figure out how to put it into the program."
Wait... how did you get the screenshot? You telepathically photographed my brain?

[SMcNeill]

Oh man! Exactly how I pictured it except for font radiating hazy golden beams. :)

"Now to figure out how to put it into the program."
Wait... how did you get the screenshot? You telepathically photographed my brain?

I was betting it was an issue with font sizing and positioning, which is why I tried to illustrate the differences in monospace vs non-monospace above.  ;)

[Adrian]

Haha, it wasn’t a screenshot, bplus. I edited the image with an image editor and inserted the text (using Steve’s Olde English Font). Getting the image onto the screen in the QB64 program, which should be fairly trivial, is my problem. Need to study QB64 commands more assiduously. Thanks Steve for the fonts tutorial. :)

[bplus]

Getting the image onto the screen in the QB64 program, which should be fairly trivial, is my problem.

No problem,

[bplus]

Do you have the image before you printed on it?

[Adrian]

No problem,

Thanks B+ !

I did try that, and got a similar error message.

[Adrian]

Do you have the image before you printed on it?

Yes.

[bplus]

Thanks B+ !

I did try that, and got a similar error message.

I will bet real money you don't have a bullet next to "Output Exe to Source Folder" under the Run menu.
Click that line or make sure bullet on the left. Image files in source folders will never be found unless you have that clicked. QB64 would be looking in same folder as itself for those images.