First what are you looking for? The sprite data (tiles) or the X/Y attributes?

I am acually looking for SPRITE DATA (Tiles) and for your info i am looking for:

• The KOOPA data
  

and

• **The random color data for the ''Ice Block Sprite''
  

** = the block which looks like a CYAN (Super Light Blue) brick. But when you pick it up, a brick sprite with random colors will be there!

BTW: I want the Ice block sprite (with random colors) to be yellow instead of random colors!

I meant Tracing as in ''Looking for DATA'' not ''Taking stuff and putting it in another source''!

"Tracing" is kind of short for "code tracing".  As in you make a log of code that executes, then read it and follow it (ie, "trace" it) to see how it does what it does.  There's no real tricks to tracing... other than being able to decipher the code well, which comes from time and experience.

FCEUXD has a tracelogger and a debugger.  Fire up the tracelogger and make the debugger snap when the game loads the data you want it to load and follow the code until you find what you're looking for.  There's nothing else really to it.

Usually, a page ($100 bytes) of memory containing the sprite data (X,Y, mirroring, tile number) is DMA'd to SPR-RAM through register $4014. I'd start off setting a write breakpoint for that register. From there, you can poke various bytes in that page and probably find what you're looking for.

Grab a copy of Yoshi's NESTECH if you haven't already and read up on, among other things, the way sprite data is stored.