4.2 works like a charm with Mitsu build
Advertisement
Urban Terror 4.2 RC on LAN 2k12 in Paris
#42
Posted 30 May 2012 - 12:06 PM
FrozenSand guys wouldn't it be cool to finish and include to 4.2 release Revolution by QueenBee and WetWired? author's permission inside this thread
#44
Posted 30 May 2012 - 12:41 PM
One thing that haven't been stated at that time (even if Majki already pointed it out), is that all current 'custom builds' will work on this release. It was my main concern when I tried 4.2 in QA team. Not that I'm the ikalizer kinda guy, but I couldn't really play without raw mouse motion e.g.
Aside this... I can say that if you look forward to play this version... you're totally right. ;) #teasing
Aside this... I can say that if you look forward to play this version... you're totally right. ;) #teasing
#45
Posted 30 May 2012 - 12:59 PM
Nice Job barbapute.
i want to do an LMS!!!!
Nice for Allowchat 3 and a updated the UI ,g_ctfUnsubWait,removal vulnerabilities and "when a team mate requests a medic his name flashes on the mini scoreboard" like this and any others.
In new cfg, u add an option for auto serverrecorddemo all ? and define the path ?
a better optimization for 64bit linux servers with ioUrTded.x86_64 is made or not? or planned.
same question for cpu multicores (core i3 i5 i7)?
i want to do an LMS!!!!
Nice for Allowchat 3 and a updated the UI ,g_ctfUnsubWait,removal vulnerabilities and "when a team mate requests a medic his name flashes on the mini scoreboard" like this and any others.
In new cfg, u add an option for auto serverrecorddemo all ? and define the path ?
a better optimization for 64bit linux servers with ioUrTded.x86_64 is made or not? or planned.
same question for cpu multicores (core i3 i5 i7)?
Advertisement
#48
Posted 30 May 2012 - 02:35 PM
I'm happy there's something new to add some life into UrT. I would like some feedback on whether the server build improvements I've mentioned can be added. With a whole new build, it's a great opportunity to address some shortcomings since bot authors would expect potentially to have to do some refactoring anyway -- i.e. no need to be overly concerned with backwards compatibility with respect to rcon commands and output.
I would also like to lobby heavily for a more meaningful timestamp for log entries. The 4.1 timestamp was virtually worthless.
Also, timestamps in qlog would be great. Come to think of it -- why not merge the logs? I've tried to think of a rational basis for there being two separate logs, but it doesn't make sense. If I'm a server operator and I've elected to have additional logging, splitting it doesn't help me much.
Lastly -- more verbose and informative logging for rcon commands -- who, what and when type stuff. Example: if there's an rcon tell, log what was said.
I would also like to lobby heavily for a more meaningful timestamp for log entries. The 4.1 timestamp was virtually worthless.
Also, timestamps in qlog would be great. Come to think of it -- why not merge the logs? I've tried to think of a rational basis for there being two separate logs, but it doesn't make sense. If I'm a server operator and I've elected to have additional logging, splitting it doesn't help me much.
Lastly -- more verbose and informative logging for rcon commands -- who, what and when type stuff. Example: if there's an rcon tell, log what was said.