... /> 1220 INK 6: LET x=3: LET y=3: LET xo=3 ... : LET hp=8: PRINT AT y,x;CHR$ (144+d): REM character ... +nd)
2010 PRINT AT y,x; INK 6+(hp

... /> 1220 INK 6: LET x=3: LET y=3: LET xo=3 ... : LET hp=8: PRINT AT y,x;CHR$ (144+d): REM character ... +nd)
2010 PRINT AT y,x; INK 6+(hp

... /> 1220 INK 6: LET x=3: LET y=3: LET xo=3 ... : LET hp=8: PRINT AT y,x;CHR$ (144+d): REM character ... +nd)
2010 PRINT AT y,x; INK 6+(hp

... /> 1220 INK 6: LET x=3: LET y=3: LET xo=3 ... : LET hp=8: PRINT AT y,x;CHR$ (144+d): REM character ... +nd)
2010 PRINT AT y,x; INK 6+(hp

... /> 1220 INK 6: LET x=3: LET y=3: LET xo=3 ... : LET w=1: PRINT AT y,x;CHR$ (144+d): REM character ... *w
2010 PRINT AT y,x; INK 6+(hp

... : pc death by hp not attr, bumping into npc wakes them ... /> 1220 INK 6: LET x=3: LET y=3: LET xo=3 ... : LET w=1: PRINT AT y,x;CHR$ (144+d): REM character ... *w
2010 PRINT AT y,x; INK 6+(hp

... /> 1220 INK 6: LET x=3: LET y=3: LET xo=3 ... : LET w=1: PRINT AT y,x;CHR$ (144+d): REM character ... *w
2010 PRINT AT y,x; INK 6+(hp

... /> 1220 INK 6: LET x=3: LET y=3: LET xo=3 ... : LET w=1: PRINT AT y,x;CHR$ (144+d): REM character ... *w
2010 PRINT AT y,x; INK 6+(hp

... /> 1220 INK 6: LET x=3: LET y=3: LET xo=3 ... : LET w=1: PRINT AT y,x;CHR$ (144+d): REM character ...

... /> 1220 INK 6: LET x=3: LET y=3: LET xo=3 ... : LET w=1: PRINT AT y,x;CHR$ (144+d): REM character ...

... /> 1220 INK 6: LET x=3: LET y=3: LET xo=3 ... : LET st=100: PRINT AT y,x;CHR$ (144+d): REM character ...

- moved start-up code to the end. Line 1020 now checks whether the first UDG has replaced the 'A' at CHR$144 to see if the Pre-Game data needs to be loaded

[code]
10 REM zx sporg basic v0pt019 20130228 - next to do = stats system
...

Cheers Morkin! It was good to meet you at Spectrum 30 - a worthy representative of the younger generation of Spectrum fans, with some social skills, to boot!

- Have begun to generalise the character data, so as to specify different characters ...

- got rid of the bug where having the data statements for the udgs too early meant that the program crashed on its second run when trying not to initialise the udgs. Solution - move the udg data statements to the very end of the listing, at line 9900
...

Cheers na_th_an, the quest to reduce initialisation time will continue!

- Now the npc ident gets printed at the bottom of the screen, and the ident and the graphic is colour-coded by the new variable npc, which gives me room for 5 different ...

- Added running hp totals for the pc and npc stats areas
[IMG]http://i1136.photobucket.com/albums/n498/bigjon1684/ZXSporgBASICv0pt023Screenshot.jpg[/IMG]
[CODE]10 REM zx sporg basic v0pt023 20130314 - next to do = stats system
20 REM ...

- have begun work on a simple map, which is initialised and displayed in the bottom right-hand corner by the cumbersome line 9220

[IMG]http://i1136.photobucket.com/albums/n498/bigjon1684/ZXSporgBASICv0pt024Screenshot.jpg[/IMG]

[ ...

... line.
1190 PRINT AT Y,X; PAPER 7;" ": GO SUB status ...

First development in 8 months on this project - changed the mechanics of setting the colour of the walls in line 9720. Instead of one general ink 1 statement, it specifies the ink colour blue for each block printed. This is so I can print black (for a door ...

Actually decided the doors need to be white as the that's the only colour the PC can walk over. Line 9720 is now a bit of a monster as the ink colour needs to be evaluated with [I]INK 1+6*(VAL t$(5)=1)*((j=7)+(j=8))[/I] or similar before each square of ...

Another 9 month hiatus. Made a few false starts because I didn't read this thread properly first! Have changed round the code for a wall to 0 and a door to 1 in the maze map to make it more straightforward to plot as INVERSE 0 or 1 when I draw the map, and ...

... in different colours then use ATTR(y,x) to retrieve the attribute byte ... it's at PEEK (22528+x+(y*32)).
It's value ...

... in different colours then use ATTR(y,x) to retrieve the attribute byte ... it's at PEEK (22528+x+(y*32)).
It's value ...

... in different colours then use ATTR(y,x) to retrieve the attribute byte ... it's at PEEK (22528+x+(y*32)).[/quote]

Have ... it's faster because the ATTR function is very short:

[code]
;; S-ATTR-S
L2580: CALL L2307 ...

... ]

Use the function ATTR(Y,X) to read the attributes before ...

... [b]( 63232 + (y*32) + x )[/b] where x is 0..31 and ... 1
220 LET x=15: LET y=17
230 ... 63032
280 PRINT AT y,x;"A"
290 REM < ... stalled:
530 LET a=ATTR (y,x): IF a0 AND a66 THEN ... PRINT AT y,x;"A"
590 LET k$=INKEY$: LET x=x-(x> ...

... CLS
20 LET x=7: LET y=6: LET x1=1 ... y,x;"\'.";AT y,31-x;"\.'";AT 21-y,x;"\.'";AT 21-y,31-x;"\'."
40 LET x=x ... +x1: LET y=y ... 23693=ATTR (y,x) OR RND>.8 THEN LET x=x-x1: LET y=y- ...

... printed in basic at coordinates x and y?

For example ... x=15: let y:11
20 print at y,x; "K"

X ... will be moving between 0-31 and y ...

... displayed "X, Y" for the ATTR function, where it should have been "Y, X". (MetalBrain ...

... displayed "X, Y" for the ATTR function, where it should have been "Y, X". (MetalBrain ...