[quote][…]
Instructions for those who don’t know
Left button = shoot
Right button = move
Spacebar = smartbomb
Left shift = shields
[…]
[/quote]
left button = move
right button = shoot
it’s swapped (only with my setup?)… therefore i said that u should add a swap buttons option ._o
win98se (as u know) + logitech mx300 mouse (i use the shitty logitech drivers + shitty² mouseware) :>
btw is the lwjgl mouse stuff (win32) usin window events (or so) or direct x to get the info? maybe it would help to switch… eg it’s better to use dinput(dx) in quake3 (in_mouse -1) if u r usin a logitech mouse.
btw i like the new version 
the “hinting arrows” doesnt look like i imagined em…but they r helpfull
here r my 2 ideas for an “easy” mode:
-auto shield
each time an enemy or projectile isnt too far away it activates itself
-artificial luck
your hitbox and the “furball” hitboxes r (slightly) smaller… enemy hitbox is (slightly) bigger.
and 2 other thingies:
-if u respawn on an special item u doesnt collect it :x
(btw their boundingboxes could be a bit bigger)
-collision detection (ship) for respawning enemies should be delayed slightly to give the player a bit more time to step away (yes - that’s less accurate but it feels better ;))
and now something completly different…
do u use gl_clamp or gl_clamp_to_edge for the sprites?
in 2 animation frames of the ship there’s a lil dark line on the bottom of the quad.
and there is a error msg on exit (game runs fine):
Runtime error #9301(trap) in JET
Please, contact Excelsior Support Dept. at support@excelsior-usa.com
This application requires a greater alpha depth.
and:
Fatal Error: JNI methodID = 0 (maybe incomplete .usg file)
btw i had problems with the first version… each time i hit ‘esc’ during a game it didnt exit… well my usual mouse cursor appeared but the game graphics were still there… therefore i had to shut my comp down with a key combo (win… up… return… return…).
hadnt tried that with the latest (this) version but i’ll do that later.
Fortunately he’s changing the LWJGL code back to what it used to be so when 0.5.1 is release I should be able to avoid these problems.