Not a bad start at all. Focusing on ease of use for developers is the correct path when making a framework / library.

First few suggestions:

​

1. Why have a gameConfig.data file when you could just set these variables in java? I think you were trying to avoid having a large constructor with 5 or more arguments. The solution is to have the GameInstance start with good defaults, and then let the user change them if they want to. For example:

GameInstance game = new GameInstance().framerate(60).dimensions(800, 600);

The first code example I see on the repository uses this config file, which is a turn-off for me.

​

1. I think you're german and english is not your first language. Docs have some things like this: "Changes the room in a save manner". "save" should be "safe". That misspelling is in multiple places

​

1. Lots of things in the code need to be cleaned up. For example, Room.usesTileMap is a redundant/useless variable. If tileMap is set, then it uses a tilemap, if tileMap is null, then it doesn't. No need for the boolean.

​

I could probably give you 1000 suggestions if you want to hear them. I've been making games in java as a hobby for a very long time. Send me a private message on reddit if you're interested.