0000821: Ensuring ACS scripts are received (Clientside)

Chat on our Discord Server Get the latest version: 3.2
Source Code

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0000821

Zandronum

[All Projects] Suggestion

public

2012-04-27 20:13

2012-04-28 13:23

Reporter

MediumTank

Assigned To

Priority

normal

Severity

feature

Reproducibility

N/A

Status

closed

Resolution

no change required

Platform

OS Version

Product Version

98d

Target Version

Fixed in Version

Summary

0000821: Ensuring ACS scripts are received (Clientside)

Description

From what I recall reading, Skulltag uses UDP connections, I don't know about if it uses TCP/IP.

Now this may be due to lag, but there was one script that didn't fire due to lag on the testing computers end. It ran everything else fine, but I assume there was packet loss on triggering of the command. This could be possibly just a glitch, or maybe it was bad coding and I messed up.

Therefore: Does skulltag check to see if the transmission of ACS is received? I don't know if packets are sent back saying "yes we received this", if there's not and it's possible that an ACS command could be dropped on it's way to the client... is there a way to add a feature in to prevent this from happening (like maybe trying to send the command again to the client who dropped it every 35 tics or so if it failed in a stack of things to send?)

If Skulltag already has support for this, might as well close this.

Attached Files

Relationships

Notes
(0003475) Dusk (developer) 2012-04-28 09:07	Skulltag seems to have a sort of packet loss handling system but I haven't taken a deeper look into how it works.

(0003476) Torr Samaho (administrator) 2012-04-28 13:22 edited on: 2012-04-28 13:22	Skulltag resends lost packets (intentional exemption: commands sent using UnreliablePacketBuffer) and ensures that the clients process the packets in the correct order. So what you are asking for is already done.

**Issue Community Support**
This issue is already marked as resolved. If you feel that is not the case, please reopen it and explain why.
Supporters:	No one explicitly supports this issue yet.
Opponents:	No one explicitly opposes this issue yet.

Issue History
Date Modified	Username	Field	Change
2012-04-27 20:13	MediumTank	New Issue
2012-04-28 09:07	Dusk	Note Added: 0003475
2012-04-28 13:22	Torr Samaho	Note Added: 0003476
2012-04-28 13:22	Torr Samaho	Note Edited: 0003476	View Revisions
2012-04-28 13:22	Torr Samaho	Note Revision Dropped: 3476: 0001874
2012-04-28 13:23	Torr Samaho	Status	new => closed
2012-04-28 13:23	Torr Samaho	Resolution	open => no change required

Questions or other issues? Contact Us.

Links

Doom and Doom II are the property of id Software.