Print

Liero v1.0 – 100lt
IP: 37.205.11.54
Game Mode: Death Match
Lives: 7
Max Kills: 15
Version: OpenLieroX 0.58 rc3

Players:

Liero v1.0 – 100lt
IP: 91.156.42.210
Game Mode: Death Match
Lives: 5
Max Kills: 20
Version: OpenLieroX 0.58 rc3

Players:

Cruel v0.96 – 50lt
IP: 69.255.183.244
Game Mode: Death Match
Lives: 5
Max Kills: 0
Version: OpenLieroX 0.58 rc3

Players:
iRod(0 lives, 0 kills)
[CPU]I'm Not A Human(5 lives, 0 kills)
[CPU]I'm Not A Human(5 lives, 0 kills)

Liero v1.0 – 100lt
IP: 87.100.156.35
Game Mode: Death Match
Lives: 6
Max Kills: 0
Version: OpenLieroX 0.58 rc3

Players:
[bkS] Perkele(5 lives, 1 kills)
heikki(5 lives, 1 kills)

[Sakmongkol]

ForceLX56Aim sounds interesting, but shouldn't there then be an option to force some other aim settings also? Otherwise that doesn't sound quite fair to me. Of course I see that you are only trying to please the older players here, but I personally think forcing newer players to use LX56 aim is not very nice. That is basically what would happen if newer players wanted to play with older ones. And the serverlist filter you mentioned would probably only cause more separation between old and new players.

[joni]

Though.. the filter would be nice, general filter not only for versions.
Like for different settings and most visited servers...

Let's say you put server filter to categorize different betas and it'd show them as this:

> 0.56
  - Server 1
  - Server 2
  - Server 3

> Beta 1
  - Server 1
  - Server 2
  - Server 3

And same for an example countries.

[albert]

Though.. the filter would be nice, general filter not only for versions.
Like for different settings and most visited servers...

What I am implementing right now is only about settings, nothing else (country, version, whatever could be implemented later but is not planned yet, not sure if even that interesting at all).

Well, forceaim could be optional setting.
So if the host want's to people use 56 aim, they will be forced and told about it.

It's exactly like that.

ForceLX56Aim sounds interesting, but shouldn't there then be an option to force some other aim settings also?

I thought about that in the beginning, also suggested that earlier. Of course, this also could be done. However, the reasons I did just a ForceLX56Aim for now are:

- It was more simple to understand as a setting.
- It was more simple to implement in a somewhat clean way.
- There is no way to get always a different aim behaviour, depending on what server you visit. There is only either the LX56 aim or your custom aim (if that is different). This is somewhat also what others have complained here. (Whereby of course you could just filter out stupid aim settings via the server filter.)
- Those people who like to have custom aim settings (and thus can make it as fast as they want to have it) probably don't care anyway if also others can use their custom aim settings (and can maybe also have it slower if they prefer that).

And the serverlist filter you mentioned would probably only cause more separation between old and new players.

It would make it only more easy for people who want to seperate anyway from servers with non-LX56 like settings.

You don't really have to use the filter. When you start OLX for the first time, there wont be any filter selected by default, the serverlist will just be unfiltered.

I personally probably will never filter out any servers. And I also like to play on LX56 settings.

So basically it allows for more open people to just play both LX56 kind of settings and also some experimental settings or more Liero like settings.

And for more close people it allows to just concentrate on the LX56 settings.

[Sakmongkol]

However, the reasons I did just a ForceLX56Aim for now are:

- It was more simple to understand as a setting.
- It was more simple to implement in a somewhat clean way.
- There is no way to get always a different aim behaviour, depending on what server you visit. There is only either the LX56 aim or your custom aim (if that is different). This is somewhat also what others have complained here. (Whereby of course you could just filter out stupid aim settings via the server filter.)
- Those people who like to have custom aim settings (and thus can make it as fast as they want to have it) probably don't care anyway if also others can use their custom aim settings (and can maybe also have it slower if they prefer that).

Oh yes, that sounds reasonable. Do that!

I'm still a little sceptical about the serverlist filter though. But perhaps we'll see how it works sometime after it's implemented.

[Rakkula]

In case you have anyway the LX56 aim settings yourself (as most oldschoolers probably have anyway), you will never see any different aim settings on any server.

Bear in mind that old schoolers really don't form the majority of the gaming community. I among dozens of others will see a huge difference.

For those with custom non-LX56 aim settings, who really don't want to go on a server which forces LX56 aim: The server list filter can hide such servers away from you.

Filters are bad, like said before.

[albert]

In case you have not seen the release notes: I just made a release (0.59beta9) now with most of these options implemented. Read here for more details:
http://www.openlierox.net/forum/index.php/topic,12826.msg210636.html#msg210636

[Lodur]

Kay I downloaded it and tried it.

I really liked all the options to make the server strafe and faster-aim free area ! Thank you for them.
Physics were OK. Much better than in the last 20 betas but for some reason it still didnt feel so smooth as it does in 0.56 when we talk about sliding with rope on roofs and floors but good work anyway as that is something I can get used to.

Perhaps before registering the host you could choose whether you host a server that will play Gusanos mods and levels or just LX so the most stubborn people that wont update their versions could join the server.

Me, T-Bag and Joonazz just played in Perkeles old LX server and found out this:
For example if I hit T-Bag so much that he loses 100hp in my screen but in his screen he only loses 95% and then T-Bag would disappear from my screen 'till he respawns. Even Perkele was gone time to time 'tho he was using old LX.

[albert]

Thanks for trying it out.

Physics were OK. Much better than in the last 20 betas but for some reason it still didnt feel so smooth as it does in 0.56 when we talk about sliding with rope on roofs and floors but good work anyway as that is something I can get used to.

Physic is not really that much different to any 0.58 or 0.59 version. The only difference in the LX56 settings preset in this release is a change in NinjaropePrecision. I left LX56PhysicsFPS as it was before (84). Maybe you have played with different FPS earlier in LX56. This also has some huge effect on the sliding behaviour. Make the FPS lower and you can slide easier.

Perhaps before registering the host you could choose whether you host a server that will play Gusanos mods and levels or just LX so the most stubborn people that wont update their versions could join the server.

No need to select the level/mod before starting the server. You can also change them later on. OLX doesn't do any compatibility check for the map/mod anyway because it's not really needed - old clients simply will not have the incompatible map/mod.

However, only >=0.58 clients can connect anyway (we have dropped the old LX compatibility). The whole point of introducing this LX56 stuff is also not to provide better gameplay with LX56 but to get old people to update.

If there are still any issues for any old players, we would rather solve those issues instead of thinking about ways to make it compatible again to LX56.

Me, T-Bag and Joonazz just played in Perkeles old LX server and found out this:
For example if I hit T-Bag so much that he loses 100hp in my screen but in his screen he only loses 95% and then T-Bag would disappear from my screen 'till he respawns. Even Perkele was gone time to time 'tho he was using old LX.

Oh, that seems to be some bug. Though not really that important as it works with all the new versions. But I will look at that later. Somebody should post this in the bug tracker so it will not get forgotten.