SAPP

[PaulusT]

I would LOVE it if you could add the following:
- The ability for clients to set the exact no lead amount e.g. in milliseconds. Perhaps to a maximum absolute value of 500ms. In this case, any automatic adjustment of the lead amount (e.g. based on client's ping) should be disabled and the specific value (set by the client) should be used instead.
- Make the no lead option enabled by default (for those servers that don't really get maintained, but will still get automatic SAPP updates). Not so important: Perhaps reduce the effect, so that clients still have to lead a bit (to avoid causing reverse-leading) and rely on clients to adjust their no lead amount manually if they wish.

[sanni]

Here are two more ideas freshly out of my retard brain ;D

Option to disable collision detection between team mates on public servers
- often in a public server people walk very close to you and make you lag. My guess is it's because of the collision detection.
Also more than once I experienced team mates blocking ladders or pathways etc. Or hogs driving over you, when friendly fire is off making you fly and lag like 10 feet ahead.
Disabling it would basicly allow you to walk through them or close to them without interference. This is something already in place in a lot of other games and it works there great.

More options for friendly fire
- it would be nice if there was an additional option for friendly fire which would allow damage to team mates until their shields are depleted but not further, so you couldn't drop their health and kill them. Just the (over)shield.

Dangercanyon Glitch protection should be on by default because most server operators are to retard to figure out how sapp works.

[Btcc22]

1) Not really possible without modding the client too.
2) Already exists. Teamplay options > friendly fire > shields only.

[supersniper]

I still feel the no lead mod needs to be adjusted... It has major hit detection problems and seems to work better for higher pinged players than it does lower pinged players.

to me when I play in servers that give me 300 ping I have way better detection than in servers with 67 ping.

[sanni]

I think the nolead part of SAPP improved very much between 5.x and 6.x.
Right now with 6.1 I would say it is spot on. Shooting on a 25 ping server feels really good. Much less random as it was with 5.x.

So yeah, thumbs up from me. I have no clue what sehe did change but it works way better now.

[sehe]

Thx Btcc to maintain this forum while I was away. ^^

So, to clarify some stuffs: There are no CE to PC map converter exists. Such converter would require almost changing Halo PC code to Halo CE.

Other:
Just like everything in sapp, no-lead is optional feature therefore it's disabled by default, and I don't want to change on this. There are plenty servers on no-lead mode already.

Also, I did not edit anything in no-lead mode since I made it. As Btcc says, Halo had always bad, "random" reg, and no-lead mode just made it more obvious. It's not only about your ping but the quality of the connection between you and the server, such as jitter. And no, no-lead is made for players with 200+ ping in the first place, so I wont exclude them from it, that's pathetic.

And finally; I was thinking about adjusting no-lead mode like set 33-66ms etc. for yourself since I created it. It's possible just no-one was requesting it so I forgot about it. I will try to add it to the next release if it really works as it supposed to be. Note that you still can't set higher ping than yours.

If you have other other feature request or bug report, post it ASAP, because uni starts soon. :P

[sanni]

Quick feature request and bug report:

We have the /events command to display a list of the events. But if there are many events you only get shown the last few. So a "/events 1" to show the first page of events and "/events 2" to show the next page and so on would be nice. I don't know exactly how many lines Halo displays in the chat but i think its 7 or so. So a page should be 7 entries.

There is a bug that temporarily removes a players admin rights on a server. Changing your IP by reconnecting your router gives you admin again next time you join the server.

[sehe]

Btw. 6.2 is out with custom lead and other stuff, and 6.3 is coming soon whit some fixes and built with VS 2013 RC.

[PaulusT]

Wow this is fantastic. Excellent work.

It is so nearly perfect for me now. However, I found that I was still consistently needing to lead by an extra few ms (tested using my client-side tool). When and if you get time, please please please could you allow clead to be slightly higher than your "ping". I feel like a little leeway is needed. I am not sure what the value is. Perhaps 50ms? I know this technique could allow intentional reverse leading, but I think the benefit outweighs the small chance of exploitation. And anyway, even though the exploit would allow you to shoot someone a "long" time after they run behind a wall, it would also mean you have to wait longer before you can shoot when someone is running out from behind a wall (at least, they could start shooting you sooner). So I don't think there is a huge issue, especially if the leeway is not too big.

Thanks for your great work.

Edit: In fact, I think I would prefer it if clead was simply restricted to be between say, 0-500ms, or some suitable upper limit, instead of involving ping at all. Then a negative value could mean "use ping" or something like that.

[sehe]

The extra lead can come from bullet speed, random factor, jitter or the unsync of the client and the server thread, or these together.

The clead command is restricted technically, not because I decided so. If you really want, you can hook the sendto function and delay packets on the client side.

Edit: 6.3 is out now.