Well I think that if the restrictions don't allow the program to write to some places, there can't be any harm to protections.
But even if people could do anything, would they do it ? Would they risk their freedom ? For example, Casio coders stopped programming image viewers when Casio warned them so I guess people would be reasonable.

In short, I don't really like the word "library" to describe bunch of code you reuse from one project to another.
This is most likely called "toolkit". A library is attended to be distribued and used by others and as far as I can see you're not willing to release it as a standalone library.

Maybe the word "library" doesn't apply yet but it will apply when everything gets released, which willhappen according to this quote (and also according to the several releases we see in the quoted topic).

So I wrote this library which I named nRayC, because it's an Nspire lib about RAYcasting to be used in C

Although this library is mainly focused on raycasting, it's not its only use : I also included a bunch of functions, like pixel, line and even triangle (why not) drawing, tile detection, bitmaps loading and stuffs.

Currently, the library features raycasting rendered by a unique function :

void nRC_rayCasting(int *map, Vector player, ScreenPoint mapDimensions, Vector dir, Vector planeVec, uint16_t *textures, char *buffer)

It also provides two structures as you can see, ScreenPoint and Vector. I don't release anything for now because I don't think it's ready to be released, but I attach a screenshot of what it can do

Hmm... Well it is an app.... Is there another way to create an array other than tilemap?

Creating an array has nothing to do with tilemapping. Tilemapping is just a method to render a world on the screen. So your question should be more "is there a way to have the array outside the app ?", and then the answer is this.

You can't use a variable in a conditionnal comment. It is described in the readme that the argument must be a constant (or a test involving only constants, which is a constant in some way).

It can be useful for example (other examples can be found but I give this one) if you want to make two versions of your program: one for regular 83+ and one for the 15 MHz calcs. Then just do your code like that:

.PROGRAM
XXX→°Model

<put some code here>

...If °Model=83
<put here the code for the regular 83+>
...Else
<put here the code for 15MHz models>
...End

<put some code here>

Then, to compile the 83+ version, replace XXX with 83 and compile, and to compile the 15MHz version, replace XXX with 84 and compile. If °Model=83, only the code for the regular 83+ will be parsed, and the contrary if you put 84.
And since the compiler tests °Model when compiling and not when launching the program, you can't use a variable there.

What takes so much space ? If I remember there are things that aren't specially useful (like the splashscreens ).

Just look at the sizes of the appvars, they have evocative names (for the most part). And the splashscreens only take 1536 bytes.

The 82Stats/83 has 27kB of RAM, that's way more than the 83+.

But it has 0B of ROM (usable ROM I mean) which is way less than the 83+, especially considering Pokemon Topaze takes like 44000 bytes for now.

What do you mean by "water map" ? Like a part of the map where we would have to use Surf to cross the sea ? That would require me to code CTs and CSs (don't know if they are called like that in English and German, I am talking about those objects that allow you to teach attacks to your Pokemons), and CSs like Surf require me to code dialogs with people (so they can give you your CSs), which would take too much memory.

A bigger map is possible, but writing all those hex numbers was already a pain, and I don't really feel like doing this again.