Leaderboard

Fix added: Let me know if its better now

Due to apparent trouble from somewhere called Russia they're thinking of bringing back conscription in the UK. I jumped straight in, I've always wanted to dye for my country, but I've been rejected, apparently 'purple is out'? I offered myself to the SAS, and was told you need to have incredible skills, well those of you who played against me know that? My cv describing my Call of Duty experience was laughed at. Does my dedication and mouse finger not count in the defence of my country? I feel slighted, so I ask you all (Basil excepted) to tell the UK government that Rob is an asset, not an ass which they described me as Can the older members not remember the posters 'Your Country needs you'? I'm gutted I can't fight

Added a new feature to the Stats page https://www.xtremeidiots.com/stats/stats.html You can now click up to 10 people and directly compare stats again each other

Hi All, I stupidly fell 8 foot out of the loft after my ladder gave way yesterday braking my left arm, ankle damage and various bruising, i was quite lucky thinking about it (guess im not as young as i think) so no gaming for at least 4 weeks and no job for 6 weeks minimum as im a nights delivery driver yup banned from driving too even though i drove to hospital with a broken arm (auto car) anyways i will pop on server to see you all from time in spec will move if busy. Cheers all

Matamata

INDEED... @NinjaBazZa made me say that.

A segmentation fault (often shortened to segfault) is a specific runtime error that occurs when a program tries to access a memory location that it is not allowed to touch. [1, 2] When this happens, the computer's hardware detects the illegal access and alerts the operating system. To prevent the rogue program from corrupting data or crashing the entire system, the OS step in and immediately terminates the program, usually displaying a message like Segmentation fault (core dumped). [1, 2, 3] Common Causes Segfaults are incredibly common in lower-level programming languages like C and C++ because they give developers direct control over computer memory via pointers. The most frequent culprits include: [1, 2] Dereferencing a Null Pointer: Trying to read or write to a pointer that points to NULL or nullptr (nothing). Out-of-Bounds Array Access: Attempting to read or write to an index that doesn't exist (e.g., trying to access array[100] on an array that only holds 10 items). Using Uninitialized Pointers: Using a pointer that was declared but never assigned a valid memory address. Use-After-Free (Dangling Pointers): Trying to access a block of memory after you have already freed or deallocated it. Stack Overflow: Exhausting the program's stack memory, which is usually caused by

thats one I never seen before!!lol