GVovkiv wrote: ↑Fri Mar 05, 2021 5:14 pm Well, for huion h430p it returns nothing

The Huion Inspiroy H430P looks like an alternative for a mouse input; so more like a graphics tablet than a tablet computer. Try https://love2d.org/wiki/love.mouse.isDown and https://love2d.org/wiki/love.mouse.getPosition.

Nice design :) I found it a bit confusing that the "10" timer starts at "9" and stops after "0". This happens because you round down. If you round half away from from zero (commercial rounding) then the timer feels better: line.button.text = math.floor (time+0.5) .. ' s...

Please upload a .love of your game. Then we can take a look at what is going on here. Without seeing how the different classes interact we can only guess what the problem may be.

Just a simple example: The game will be an image moving around with the arrow-keys. client (LÖVE): love.keypressed() for the arrow keys (send these to the server) gamestate x- and y-position (get these from the server) the image love.draw() (draw the image at the x- and y-position) server (pure lua)...

Or is it possible somehow with the networking libraries to do that? This is completely possible with the networking libraries of LÖVE. You just need a way to send input from the players computer to the server and respond with a new gamestate. Why should the networking libraries of LÖVE not work for...

But how does it work exactly? Isn't the game file only accessible by the hosting server during runtime? I will test it out soon, but from what I saw, you basically have a game.js and game.data file. It seems like the content of the code is located in the game.data file, but why would that be availa...

If you are afraid that someone will look at the source-code of your game, then do not give it to them. The concept is called Cloud Gaming. The drawback is the increased complexity and the cost of the server(s).

Yes, that is the formula to calculate the angle. But that is the easy part. Calculating the point on the border is harder. But I found a simpler in my sleep (simpler than what I thought of yesterday): calculate_intersection.jpg The first step is to find out which screen-border the pointer needs to b...

There are many ways to do this. It depends on what you want. I can see two possibilities: A simple approach, where you just point in the approximate direction: simple.jpg Hereby you determine in which part of the playing field the object/enemy (X) is relative to the player (P): the number shown. Her...

Personally: I do not know. Can you expand on this: What do you want to achieve? I mean, like: somewords=love.graphics.newText(...) somewords=somewords:setf(wraplimit), not include using a new text to replace original text. or just: somewords=love.graphics.newFormatText(...) Okay, that I understand....