Jump to content
Sign in to follow this  
Somerville

addWeapon & addMagazine issues

Recommended Posts

Hi,

I've got a script where somebody chooses a weapon, and it's added to a crate. However, players are complaining that they can't take the weapons from the crate afterwards. They are in the crate, just they're saying they can't take the weapons.

Any thoughts?

Share this post


Link to post
Share on other sites

are you using addWeaponCargo and addMagazineCargo?

Share this post


Link to post
Share on other sites

Hmmm, it may be a locality issue. Are the weapons being added on the server? I don't have time to test solutions anymore sad_o.gif

Share this post


Link to post
Share on other sites

did yuo first remove all weapons from the crate???

<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">clearweaponCargo this; clearMagazineCargo this

Share this post


Link to post
Share on other sites

Yep, all weapons have been removed, as the weapons are showing in the crate, but they cannot be taken out of the crate by the user.

Share this post


Link to post
Share on other sites

I get the same problem at times. Most weapons okay, but sometimes weapons (especially M136) are not able to be removed by players.

Seems to be worse when laggy for some reason.

I tried just adding weaps just on server only, instead of in the crate's init lines, and that just gives empty crates.

I think somewhere that the system is losing track of crate contents in-between the machines connected, therefore when attempting removal of a weapon the system sorta hangs while trying to update the other machines with the 'I am removing this weapon' information. You can close the gear screen, and re-open it, and I think those same weapons remain unavailable. I have noticed that when it's just lag-induced refusal-to-let-you-get-weapon then closing and reopening the gear tab will then allow you to take the weapon.

It seems that there are two separate issues at work here.

ONE is the lag-induced slowness of the gear-removal update notifications, and the OTHER is the possible un-synchronised state of gear-content information-sharing between machines in a more permanent way.

That's how it looks to me, anyway - after examining the behaviour online.. Perhaps that information may be useful in sorting the problem? Here's hoping.

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×