domistyle

Not yet, sorry.

Will be in the next version

What you mean with alternate names? What would the external bat file do, for example? This is related to the cut off banlist that is caused by BattlEye. I recommend using DaRT BRS in order to receive a complete ban list.

BRS is the Ban Relay Server DaRT uses in order to request the ban list via TCP to prevent cut off ban lists. BRS however needs to be installed server side and enabled in the DaRT settings in order to use it.

Probably related to the other connecting issue or server is configured wrongly. First: Please read the error message. Disable the BRS or install the BRS. Second: It's normal. Just wait till your server is able to update. Disable BRS in the settings or install it on your server. Which hoster are you using? Since multiple people are reporting it now and it's not DaRT it's probably a hoster issue or a BattlEye issue with the recent updates. Was heißt RCon admin meldung?

IP & Port?

Would you be able to send me your RCon details via PM? I can't recreate those issues on my servers and any other server I tried so far.

Not a problem with DaRT but rather with the server configuration. Contact your server hoster (gtxgaming) about it.

Quick ban works just the same way, but I will add a ban resend + ban verification in the next version for all bans. That is a really good idea. Will be in the next version. Oh, it's not supposed to be enabled yet. I disabled it server side now to prevent further problems. I will enable it sometimes soon, doesn't need a new version, only the server side part isn't done yet. It just syncs your database with the master server. Which will send your list to the server and then retrieve the complete list. Meaning if a few DaRT users do it you probably are going to have all active players in your list. You should check out the Execute button in the lower left corner. ;) Execute -> Manually add a ban Execute -> Manually add multiple bans Yep, a few more shortcuts will come in the next version for example ESC will close any dialog to make everything a little bit quicker. Yeah, will look into that for the next version. The clear button i just a temporary solution. You are welcome. That's the reason why I am doing this after all.

I just uploaded v1.0.1 which contains a hotfix for the crash on startup.

Good to hear.

Oops, good to know. Try again.

Would you be able to provide me with the RCon details for your server via PM so I can take a look at it?

Good to hear. That is possible. Will be in the next version. This can only be done with a GameSpy integration. I may do one for the final version of DaRT but I can't guarantee it. Already planned for the next version.

Nice to hear you like it. You will need to go into some detail about all the problems you are experiencing if you want help. Crash logs? What did you do to crash DaRT? How does it lock out admins? Which server hoster are you using? It's actually on purpose that DaRT logs GUIDs multiple times with every name this GUID used + date. This helps to see which names this player previously used. There will be an option to turn this off in the next version. DaRT will only log players if there is a valid GUD available via RCon. This won't happen if the player is still initializing or the BE master server is down. Do you have by any chance the refresh on player join enabled? This sometimes causes problems because the refresh will occur while the player is initializing, which results in the player not getting logged till the next refresh. This is a problem with how banning with BE works. Because it uses the player id and not the GUID + RCon works over UDP it occurs quite often that the bans are unreliable. The only thing I can do on my side is to execute the ban multiple times and check if it failed. Will probably check on that for the next version. You can also look in using BRS incase the request itself is unreliable too. Will probably add a ban via BRS in the next version which will be alot more reliable. Same as above. BattlEye uses the unreliable UDP protocol. If your connection or the connection of the server is bad the effects of this get even worse. Only thing I can do is to wait for the messages a little bit and resend it if necessary. Will take a look at that for the next version too. This should be fixed with v1.0. Tell me if not. This is an issue with the WINAPI that never got resolved. The only way to fix this on my side would be to leave the console alone till auto scroll is enabled again and then add all the new messages at once.

That's because the DayZ devs do not give out any instance ids anymore. The few remaining servers with public Hive out there are and probably will be the last ones. I would host one though if I could.

Could you try out this version? http://forum.swisscraft.eu/DaRT/DaRT_testing.zip If it crashes again, post the crash report again. Do you have automatic connection enabled?

Investigating now, thanks for the report.

DaRT v1.0 is out. You can download it here. Incase you are having problems with your ban list you can also check out the BRS which will move your ban list requests to a reliable TCP connection. You can download BRS here. Note: BRS needs to be installed on the server, not the client! Detailed instructions are in the readme.

Can you check everything again? If you still have problems contact your hoster about the RCon password. Thanks. v1.0 will be released pretty soon once I got time. Just got my Oculus Rift and I am playing around with it a little bit. ;) The only effective way to create a map is with database access. Of course you could also read through the logs which is pretty ineffective though.

The entered password is incorrect but RCon is running. Check your beserver.cfg if you are using the correct password and also check if you are connecting on the correct port.

There is no map one could do without the information from the database. ;) It does work. What error message do you get?

Good to hear.

You can also try to adjust the other width values. Not sure which of them is the correct one.

You will actually need to adjust your Description.ext: Try increasing the width value.