New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How do i change difficulty? #60
Comments
Easy in coop is much harder than easy in regular RTCW |
that it is and it does make sense, but how do we reduce it. for example in old svencoop you would change config file and reduce the health of enemies or increase damage on weapons. how do we do it here? i have searched for cvar to change difficulty but i can not find it. say if two inexperienced players want to have a go at it, the easy in coop is too hard. for me it is actually a good setting. |
a cvar has been added in 1.0.3beta that allows you to use the old ai accuracy, as i have to admit currently in 1.0.2 the ai are verging on super human with their ability to spot you from miles off and get accurate shots on you instantly you tend to spend more time diving for cover. really the difficulties should reflect rtcw defaults and a extra difficulty should be added for godlike difficulty |
I remember having the very same issue with the difficulty many years ago, while playing rtcwcoop with a friend. The ai was superhuman, like having aimbots or something. I tried to compile build 4bd1b6a on Windows 11 using msys2, so that I could test using the old ai for bots. I successfully compiled rtcwcoop and all that, following the instructions included for compiling, but I got a black screen & game crash after opening RTCWCoop.x64.exe in my RTCW folder (the v1.0.2 release from August 23, 2017 works though). |
1.0.2 works but it has the superhuman bug still, there are a number of
bugfixs that have been added but not included that fix a lot of the issues
you have to look through the git page to find them and add them in yourself
and then compile, it would be best to add them to the 1.0.2 source as the
latest build is rather buggy. i did do a 1.0.2 source with all the bugfixes
and was working on some other things that i found wrong with the 1.0.2
build, but it all got pushed to one side quite some time ago as i had other
projects to do.
…On Thu, 16 Nov 2023 at 5:28 pm, Gagert ***@***.***> wrote:
I remember having the very same issue with the difficulty many years ago,
while playing rtcwcoop with a friend. The ai was superhuman, like having
aimbots or something. I tried to compile build 4bd1b6a
<4bd1b6a>
on Windows 11 using msys2, so that I could test using the old ai for bots.
I successfully compiled rtcwcoop and all that, following the instructions
included for compiling, but I got a black screen & game crash after opening
RTCWCoop.x64.exe in my RTCW folder (the v1.0.2 release from August 23, 2017
works though).
—
Reply to this email directly, view it on GitHub
<#60 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A5IQCCFVDKHDTAMWNOMH533YEZEKFAVCNFSM5BIXOG72U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBRGQ4TAOJVHE3Q>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
i think it is 1.0.2 that is the stable release it has been quite a long
time since i looked at this.
…On Thu, 16 Nov 2023 at 5:50 pm, Darren Davis ***@***.***> wrote:
1.0.2 works but it has the superhuman bug still, there are a number of
bugfixs that have been added but not included that fix a lot of the issues
you have to look through the git page to find them and add them in yourself
and then compile, it would be best to add them to the 1.0.2 source as the
latest build is rather buggy. i did do a 1.0.2 source with all the bugfixes
and was working on some other things that i found wrong with the 1.0.2
build, but it all got pushed to one side quite some time ago as i had other
projects to do.
On Thu, 16 Nov 2023 at 5:28 pm, Gagert ***@***.***> wrote:
> I remember having the very same issue with the difficulty many years ago,
> while playing rtcwcoop with a friend. The ai was superhuman, like having
> aimbots or something. I tried to compile build 4bd1b6a
> <4bd1b6a>
> on Windows 11 using msys2, so that I could test using the old ai for bots.
> I successfully compiled rtcwcoop and all that, following the instructions
> included for compiling, but I got a black screen & game crash after opening
> RTCWCoop.x64.exe in my RTCW folder (the v1.0.2 release from August 23, 2017
> works though).
>
> —
> Reply to this email directly, view it on GitHub
> <#60 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/A5IQCCFVDKHDTAMWNOMH533YEZEKFAVCNFSM5BIXOG72U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBRGQ4TAOJVHE3Q>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***>
>
|
Thank for the reply; I'll try just that later. I should manage easily to add the required fixes to the 1.0.2 source, in my case the non-superior ai difficulty. I didn't thought about just editing the 1.0.2 source and then compile. |
Now I added the lines from commit 2cd3af6 to the 1.0.2 source & compiled it. The game works now. After that I added the line seta g_ignorescriptedaccuracy "1" in wolfconfig.cfg. I used the console in rtcwcoop, and g_ignorescriptedaccuracy is "1" or default as the console tells me. Does that seem right? I just did a quick test for maybe 2 minutes in game, and I actually managed not to die after encountering 3 enemies. |
if it works it works for more fixes look for commits by duko
…On Thu, 16 Nov 2023 at 6:53 pm, Gagert ***@***.***> wrote:
Now I added the lines from commit 2cd3af6
<2cd3af6>
to the 1.0.2 source & compiled it. The game works now. After that I added
the line seta g_ignorescriptedaccuracy "1" in wolfconfig.cfg. I used the
console in rtcwcoop, and g_ignorescriptedaccuracy is "1" or default as the
console tells me. Does that seem right? I just did a quick test for maybe 2
minutes in game, and I actually managed not to die after encountering 3
enemies.
—
Reply to this email directly, view it on GitHub
<#60 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A5IQCCBXGMRZTTIVGPODTFTYEZOMHAVCNFSM5BIXOG72U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBRGUYDIMZWGE4Q>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I haven't been with my head in this source code since my last commit. What exactly is wrong with the latest git version of the source code ? |
As far as i remember it is mostly fine with duko's fixes. And I think you
fixed a few issues with your latest, I was trying to sort out log filing so
you could use different file names. Apart from that it has been quite while
since I looked at this so I myself can't remember much either sox
…On Thu, 16 Nov 2023, 8:32 pm fretn, ***@***.***> wrote:
I haven't been with my head in this source code since my last commit. What
exactly is wrong with the latest git version of the source code ?
—
Reply to this email directly, view it on GitHub
<#60 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A5IQCCBWBOU42KAWENFPSL3YEZZ5JAVCNFSM5BIXOG72U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBRGUZDMOBXGMZA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Changing difficulty to easy via menu does not reduce the difficulty it seems. How do we do it? What are the commands?
The text was updated successfully, but these errors were encountered: