Slick Forums

Would you as a temporary measure be able to get that running against the development branch? Then I can directly link it at the site as a nightly while I sort my internet out.

_________________
- A free, retro, 2D MMORPG being developed using Slick2D and TWL

_________________
- A free, retro, 2D MMORPG being developed using Slick2D and TWL

For those interested in keeping up with the dev branch, but from Maven, check out https://github.com/nguillaumin/slick2d-maven

It's still a work in progress, comments and feedback welcome on the Maven thread there: viewtopic.php?f=27&t=4647&p=34533#p34533

Cheers,

Nico

So just curious if the website is still being maintained. Looks like some great tutorials started to pop up on the wiki but most are not complete. Is Slick2D still going through active development?

I'm involved in teaching a software development subject at a University and this semester we have assigned the students a task of making an educational game using Slick2D (perfect fit as they know Java and OO but likely no graphics programming experience). To get them started I am having them go through the first 2 Spiegel tutes on the wiki which I think are excellent.

_________________
| Last game

Hey, what kind of bugs does Slick have ?
Is there a list somewhere ?

Except for the weird artifact bug happening even when the image's filter is set to nearest and some minor Shapes issues, I've never met any bugs if I remember well

Using Slick for PC games still allows me to be more productive than LibGDX in my opinion, I wish it was fast and easy to port a Slick game to LibGDX though

I can see these issues: https://bitbucket.org/kevglass/slick/is ... tatus=open

Main issue for me? https://bitbucket.org/kevglass/slick/is ... turns-true
But,.. never find this bug so far

_________________
| Last game

Slick has a growing list of which may never get fixed. The biggest problem with Slick is that it relies on "old school OpenGL" and doesn't port to Android/iOS/Raspberri Pi/WebGL/etc. And since it uses deprecated OpenGL APIs which may be poorly supported by drivers in the coming years, it's not a very "future proof" library.

I like Slick's simple API, and it's good for simple games. But if you ever aspire to make more complex games; maybe those that require better performance or memory management, or maybe something that can port to other platforms, you will inevitably need to use LibGDX or another framework. And IMO your time would be better spent learning that framework from the very beginning; especially since it is not much more difficult to use than Slick (in many areas, I'd argue LibGDX is easier than Slick).

_________________
| Last game

Don't drivers provide backward compatibility with openGL ?

If I'm developping a quite big game going on for PC only (about 20k lines of codes), should I start porting it to LibGDX now, or keep using slick and eventually port it later, when the openGL compatibility really becomes an issue ?