Apoc
-
Content count
290 -
Donations
0.00 EUR -
Joined
-
Last visited
3 Followers
About Apoc
-
Rank
Underboss
- Birthday December 4
-
To clarify: Please post the server .rpt and the client .rpt. You need both of those to diagnose issues with a script such as this. I'd recommend dropping them both into pastebin (separate ones!) to make life easier for all who may try to help.
-
This kind of makes me think that the parameters for the ExAd functions were changed. That's one potential possibility. What needs to happen is to clear out all of the ExAd references and use Exile functions.
-
OK, so apparently when people updated ExAd, they made the dubious blunder of changing/removing old function definitions. This has in turn broken scripts based on some of that core functionality. Though, in the interest of keeping code efficient (and clients running as smooth as possible), it was the right choice to remove deprecated functions. I've updated the github repository so that the missing function is defined within the app. I think this will fix the issue. If someone would test this and let me know if it sorts you, that'd be appreciated. I'd like to be able to commit to revising the entire repository to fit the new Exile update and break off from the ExAd definitions altogether, but I'm not sure when I'd actually have time to sit and do that. ** OH, and in my editing of my post I forgot to attribute the fix to Frontliner. He spotted the problem and sent me a message a while ago, but I failed at taking a look at that time and sending this fix off. In reality, I bet your clients are throwing an error in the logs about the missing function.
-
Both of those approaches should be deprecated with the latest Exile update including apps. But no, the infistar approach breaks the terms of the license for the code, given that it must be open source.
-
So, I'm guess there's an issue with the data type of the variable. Alsoooo, I don't think the functions are robust, or possibly even functional, for the respect options. I thought* that this was tested ages ago. I just updated the github with some changes that might have an effect, though I kinda doubt it. I don't have a test setup these days, so you'll need to let me know if they have an effect. If you're savvy, the underlying code is in the functions.sqf. You could place some log markers in there (you'll see some of mine for testing) and trace when the variable switches from a number to "any".
-
Argh. Well that sucks a bunch.
-
Yikes, @NFGCaboose-1, alas I've not been messing with Exile in quite a while. No, unfortunately I did not set up the framework of the previous system for the slides and all of that business. I'd wait until the ExAd creator updates all of the base stuff to get instructions. Sucks I know. If you look at it, you can probably port it fairly easily if you look at how the new default apps are created and the structure of the ExAd apps.
-
No, the AI for the airdrop are not spawned by DMS. I think you could set that second DMS config to "TRUE" and it would ignore the airdrop AI and not freeze them. If you set the first value to "TRUE" then you will not have any AI freezing on your server. In that case you could see some performance impacts depending on the number of AI you are running on your server.
-
You're running DMS no doubt. DMS is freezing the AI. Have the drop spawn within your AI freeze zone. Either modify that parameter within the airdrop script, or extend out the range of the freeze effect on your DMS install. Personally, I'd do the latter. If you're not running a full server (not sure many of those exist in Exile these days) you shouldn't see a huge effect by having a bigger unfreeze radius.
-
Nothing in the server RPT? You could just add it to the loot rewards and leave the AI with standard gear.
-
Yeah, this is a typical issue. I think DMS is ignoring the variable saying to ignore the supply drop AI.
-
The system is already in the code, but I'm guessing at some point in the updates it no longer has the same variable names.
-
As for things not showing in the list, try breaking it into multiple groups to see if there is a list length limitation. I didn't see an error in your formatting. As for respect, you'll have to sort of dig and see what Exile is telling you in regards to any errors in reading the client respect, and comparing it to the value it pulls from your drop list.
-
I'd recommend auto-locking the server and kicking players before the restart. Also, lock the server after the restart until it is fully booted up. This sounds like problems related to stuff not getting set in the database properly around restart, as well as variables not being fully loaded in when the player tries calling an airdrop.
-
