nex
nex
Explore posts from servers
CDCloudflare Developers
Created by nex on 8/18/2023 in #general-help
Unable to open live chat
Hey, so I've been trying to open a live chat and keep getting this error:
There was a problem opening your chat. Please refresh your browser and try again.
Is this a known issue? I've been experiencing it for the past week or so. Thanks.
6 replies
CDCloudflare Developers
Created by nex on 2/8/2023 in #workers-help
Hitting memory limits again?
Hey, so a couple months ago when we started using workers for delivering game content (using R2 as a cache layer), we ran into an issue where files that were larger than 128MB caused the request to fail at 127.99MB. We solved this by better utilising response.body.tee(), but the issue is back again as of this morning. Nothing has changed with our workers code, we essentially left it as-is once we got it working how we wanted it to, including serving files in the 300MB-800MB range. This is the code that we currently use for delivering the response, the same code that this is supposedly failing with:
// get two streams for the body (one for R2, one for responding)
const tee = response.body?.tee()

// if the response status isn't 200, respond with the status code given by the upstream
if (response.status !== 200) {
console.log(`Got HTTP ${response.status} from upstream: ${url}`)
return new Response(null, { status: response.status })
}

// attempt to put the upstream data into R2
try {
await R2_BUCKET.put(key, tee[0])
console.log(`Successfully put object ${key} into R2`)
} catch (err) {
console.log(`Error while putting ${key} into R2:`, err)
}

// return the response from upstream
return new Response(tee[1])
// get two streams for the body (one for R2, one for responding)
const tee = response.body?.tee()

// if the response status isn't 200, respond with the status code given by the upstream
if (response.status !== 200) {
console.log(`Got HTTP ${response.status} from upstream: ${url}`)
return new Response(null, { status: response.status })
}

// attempt to put the upstream data into R2
try {
await R2_BUCKET.put(key, tee[0])
console.log(`Successfully put object ${key} into R2`)
} catch (err) {
console.log(`Error while putting ${key} into R2:`, err)
}

// return the response from upstream
return new Response(tee[1])
It's worth noting that I cannot tail the worker as it's getting too much traffic (250+ invokes per second) so getting logs are out of the question. If there's anything here that can be improved, I'd much appreciate it if you could point it out. I'm not very familiar with streams so it's possible that I've made a mistake here. Thanks 🙂
21 replies
RFRSM.GG ~ Freeroam
Created by nex on 9/30/2022 in #📞|support
Failed to connect after 3 attempts
For those of you that are currently getting this error message, use this post to discuss it
181 replies
RFRSM.GG ~ Freeroam
Created by nex on 9/23/2022 in #📞|support
Pure Mode - a.k.a 'The server you are joining does not allow modified game files.'
We have re-enabled pure mode on server #2 with the intention to stop cheaters from modifying their game files to boost their damage, increase their fire rate, shoot through walls, and more unfair advantages that they are abusing it for. We do not intend to enable it on server #1 unless Cfx.re makes the necessary changes to support a wider range of legitimate mods that pure mode will impact! What is "pure mode", and what does it do? Pure mode is an optional feature that servers can enable to block modified game files from being loaded into someone's FiveM session. As partially mentioned above, the most common way to cheat nowadays is by modifying relevant files to unload props and models, change weapon properties, and material data to be able to shoot through surfaces that you otherwise wouldn't be able to shoot through. Pure mode is made to combat this type of cheating by validating files and ensuring only the vanilla content is being used. Why are my files getting blocked when they are legitimate? Due to the nature of pure mode, legitimate files (such as those related to QuantV) can and will end up being blocked by this, but Cfx.re has announced that this will be changing once they move to a PKI to allow client mod authors to 'sign' their mods and allow them to be used depending on the level of pure mode used by servers. We don't intend to use the most aggressive level of pure mode, and we likely never will - the current level of pure mode is the 'lightest' level that allows common audio files and known graphic mods (such as Natural Vision Evolved, or "NVE") to be used. Why not make your own anti-cheat detections for damage boosting and fire rate? The reality is that anti-cheats that work this way are often a detriment to your FPS, especially in highly populated servers such as ours. We've tried going down this route ourselves and not only is it difficult to maintain, but it is also extremely inefficient and inaccurate. Pure mode is intended to stop these types of file edits, and we fully support it. If no one used pure mode because it blocked their favourite (and legitimate) client mods, then the feature will gain no traction and will take even longer to get those mods validated for it. How do I get my mod validated for pure mode so I can use it on servers that enforce it? In the June 2022 community update post, Cfx.re encouraged people to open bug reports for any issues that they may have with it. You can see this post here to read up on it: https://forum.cfx.re/t/cfx-re-community-update-june-2022-edition/4866955 You can open a bug report here, which is the same link given in the above post: https://forum.cfx.re/c/general-discussion/bug-reports/28 Before opening a bug report on the Cfx.re forums, make sure that you state which mod is being blocked, why you are using it, as well as the files for it so it can be looked into. We are only telling you what to do based on what was said in the above community post. This is not a feature of RSM, so opening a bug report here will be pointless, nor can we 'whitelist' your mod for you!
4 replies
RFRSM.GG ~ Freeroam
Created by nex on 9/14/2022 in #📞|support
Support Rules & Guidelines (READ FIRST)
Hello, and welcome to the new Support forum channel! 🙂 In order to ensure that everyone is treated fairly and receives a quick and clear response to their issues, we have some rules and guidelines here that we expect everyone to follow. Please keep in mind that support isn't guaranteed and is on a volunteer-basis. Furthermore, staff members are here to moderate, not to provide support, so don't expect them to provide it either. We do expect members of our community to engage and help others here, and you may receive the <@&877231868611809320> role depending on your activity and willingness to help others here. If you see other members asking for support in other channels, please direct them to this support forum so that they can search for their issue before opening a new support post (see Guideline #1).
3 replies