Yeah but I've now the biggest bug I ever had had : I think it is an OS or an Axe bug.
I was compiling my code and all worked perfectly but when I tried to launch my game I saw the "ERR:INVALID" message. Thinking it was an error of the OS I tried firstly to archive more datas to leave more free space, but it don't worked (of course  ). Then I decided to compile as an app an no as a nostub prgm and it worked perfectly 
The problem is to code it is much more easier to be able to compile fastly your code w/o create an app, writing it and always defragmenting after seeing the code is buggy 

Does anyone have encountered this bug or know how I can fix it I can't continue coding with this issue 

Unless it's what Ashbad said, It's because of the 8192 KB code limitation. (this excludes data) You have two choice now:

-Make an APP and put the data outside the source as appvars
-Split the game in multiple sub-programs and use a TI-BASIC launcher running each Axe programs with Asm(prgmNAME) when needed. For example, when you need the menu, the walking engine will store 1 to Ans, exit, then Asm(prgmMCMMENU) would be ran. When exiting the menu, have it store 2 to Ans so the main engine is ran.

I hope you don't kill the project just because you have to compile in app, though. I think you should maybe take the extra 5 seconds to compile as APP and ask more coding help on the forums, maybe. An alternative could be to temporary remove unused code during debugging and continue compiling as program, then when you want to do a major test, put the code back in then compile as an APP. I would hate to see this die just because of that. If you still want to stop working on this just because of that, will you at least release the source code and sprites so someone else can take over?

Okay !! Don't worry I will certainly not stop my project because of an error like that. I though it was only a 16kb limitation for programs but isn't it possible to fix it in the OS like what was do for xlib ? However this project will not die and I'm working on my hatches now but it still remains to me to fix my favourite ennemies
Question : is there other Axe's limitations ? It will be better if I know them And how could I stop doing this after all efforts I made for this game ?

I though it was only a 16kb limitation for programs but isn't it possible to fix it in the OS like what was do for xlib ?

The 8k code limit is a hardware limitation. The xLib problem was just a software glitch in 2.53MP.

edit: ninja'd ;_;

Cool to hear!

Cool, any new screenshot soon?

To avoid to broke the beautifulness of the game I will post screenshots only when I will have fixed my sprites At the moment, Samus always looks at the same direction and hatches too. It will try to fix that soon
After that I will post screenshots !!

To avoid to broke the beautifulness of the game I will post screenshots only when I will have fixed my sprites At the moment, Samus always looks at the same direction and hatches too. It will try to fix that soon
After that I will post screenshots !!

I see, good luck fixing those!