I am not making fun. I just cannot see why you had TWO(!) Wii U's die on you because of "forced shut down" and other people here have over 800 forced shut downs (man, what do you do to make that number...) and haven't had a single brick.
you do the math.
I just explained like twice on this gbatemp. i can sell you my 2 broken fucked up Wii U if you're that desperate. Seriously what's wrong with you. You're getting on my nerves and i'm always chill here. I'm only saying what happen to me, and you're like ''how can that be??'' like OKAY???? I'M WRONG???? what do you want from me??? It literally happened to me and i'm only saying what happen to me and warning others cause i care and hope it doesnt brick other wii us, if you don't wanna listen FINE. god. ''but the loadiine website too perfect to brick Wii U Hhhhmppphh" I'm sorry but fuck off
Oooooooooooooo I suck at math cause apparently what I said is make believes.
To find your crash number; you'll want to run a CFW with wupserver and connect up with wupclient. Change into /vol/system_slc/logs and download the directory. From here is really whatever you want to do; I personally grepped for "life time" in the log files and visually scanned for the highest number of crashes. Remember that the highest-numbered log is not necessarily the latest.
I'm actually on the lookout for spare Wii U consoles; got some interesting leads lately that I'd like some trash systems to investigate on. eBay Australia won't go lower than $150 on a good day; so if that's a serious offer it'd be great if we could get in touch.
Oh, they aren't bad numbers. The reason it changed was because I initially went with the highest numbered log in /vol/storage_slc/logs (99.log) but I later realized that the counter wraps around; so I updated it with the actual number from the latest log (8.log).
That makes sense. I wasn't questioning the change in the numbers, just questioning what caused the jump.
While your point about a forced reboot not incrementing that number is correct; you didn't see the context - I'm a homebrew developer. The vast majority (I'd even wager all) of the fatal errors on my system are a result of homebrew code that's in development or whatever. When this occurs, the error falls through to MCP (thanks OSFatal) and the console locks up, requiring me to force a shutdown by holding the power button.
Ah, you have the advantage of knowing what you were doing at the time. Kind of an important detail , and one that the poster can't eloquently define.
There are few, if any, other situations where a fatal error would be logged - installation issues and sigpatches pop up an error, but the console continues to operate. These, therefore, are not fatal errors and should not contribute to the counter.
00:14:36:996: Cleaning /vol/storage_mlc01/usr/import/crash
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Installation Failure detected
- Error value: -262208
- Package:
</vol/mcp_rawpkg/install/funkybarnup_rptik>
- Title: 0005000e-10118400 (0x0010)
- AppType: 0800001b
- Platform: Cafe
- Target dev: mlc01
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Installation failure log will be stored with error code '162-0000'
00:14:40:739: MCP: life time number of fatal errors - 362
00:14:40:740: MCP: storing current logs as '/vol/system/logs/63.log'
00:14:41:379: MCP: Finished storing current logs as '/vol/system/logs/63.dsc'
00:15:51:190: Cleaning /vol/storage_mlc01/usr/import/crash
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Installation Failure detected
- Error value: -262208
- Package:
</vol/mcp_rawpkg/install/funkybarnup_rptik>
- Title: 0005000e-10118400 (0x0010)
- AppType: 0800001b
- Platform: Cafe
- Target dev: mlc01
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Installation failure log will be stored with error code '162-0000'
00:15:54:462: MCP: life time number of fatal errors - 363
(forced a shutdown here to see if it counted, which you acknowledged it doesn't)
00:01:03:063: Cleaning /vol/storage_mlc01/usr/import/crash
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Installation Failure detected
- Error value: -262208
- Package:
</vol/mcp_rawpkg/install/funkybarnup_rptik>
- Title: 0005000e-10118400 (0x0010)
- AppType: 0800001b
- Platform: Cafe
- Target dev: mlc01
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Installation failure log will be stored with error code '162-0000'
00:01:05:638: MCP: life time number of fatal errors - 364
00:01:05:639: MCP: storing current logs as '/vol/system/logs/65.log'
00:01:06:182: MCP: Finished storing current logs as '/vol/system/logs/65.dsc'
Another log - can't reach update server
DRMAPP: error code 1054207
DRMAPP: post error state 19
DRMAPP: Patch: scene state: 13 -> 40
00;03;16;928: ErrEula: thread=0x100457e0, stackSize= 63 KB, stackBase=0x1069b138, stackEnd=0x1068b140 (ErrEulaAppearError)
00;03;16;928: ErrEula :ErrorCode = 1054207
00;03;16;935: ErrEula: thread=0x11beaee8, stackSize= 16 KB, stackBase=0x11beaed8, stackEnd=0x11be6ed8 (ErrEulaDrawTV)
00;03;16;935: ErrEula: thread=0x11bef778, stackSize= 16 KB, stackBase=0x11bef768, stackEnd=0x11beb768 (ErrEulaDrawDRC)
00:03:17:073: CSC: Product Code: WUP-N-HASE, Title Version (major): 13
00:03:17:074: CSC: Repaired: FALSE, Wagon: FALSE
00;03;16;943: ErrEula: thread=0x100457e0, stackSize= 63 KB, stackBase=0x1069b138, stackEnd=0x1068b140 (ErrEulaCalc)
00:03:17:079: CSC: InitialLaunch stage: 2
00:03:17:083: CSC: USB Storage Connected: TRUE, Device Type: NAND
00:03:17:104: CSC: RCA Enabled: FALSE, KeepAlive Enabled: TRUE, ParentControl Enable: FALSE
00:03:17:108: CSC: Check : /vol/storage_mlc01/usr/boss/00050010/10040100/user/common/ (-196631)
00:03:17:109: CSC: Check : /vol/storage_mlc01/usr/boss/00050010/10040100/user/80000006/ (0)
00:03:17:110: CSC: Boss Storage Exist: TRUE, NetworkID Assigned: FALSE, System Network Connected: TRUE
00:03:17:135: CSC: NIC Type: WIFI, DNS obtained by DHCP: TRUE, IP obtained by DHCP: TRUE
00:03:17:141: CSC: TV Port: HDMI, TV Aspect Ratio: 16:9
00:03:17:146: CSC: TV Resolution: TV_1080P
00:03:17:147: CSC: CODE: [HASE-0252-5375]
2017-02-28 01:02:07 - log collection event from pid 21
00;03;17;027: (1)5.5.1 U
00;03;17;027: (2)WUP-101(02)
00;03;17;027: (3)FW114860859
00;03;17;027: (4)HASE-0252-5375
00:03:17:151: MCP: life time number of fatal errors - 365
00:03:17:152: MCP: storing current logs as '/vol/system/logs/66.log'
00:03:17:674: MCP: Finished storing current logs as '/vol/system/logs/66.dsc'
DRMAPP: Finding package with titleId=0005000e10178f00, mediaType=2
DRMAPP: manage state 7 -> 11
DRMAPP: Patch: scene state: 7 -> 11
DRMAPP: kick task: 7
DRMAPP: manage state 11 -> 13
DRMAPP: Patch: scene state: 11 -> 13
DRMAPP: Error Code: 1054207
DRMAPP: manage error occurred:
DRMAPP: error code 1054207
DRMAPP: post error state 19
DRMAPP: Patch: scene state: 13 -> 40
00;04;12;467: ErrEula: thread=0x100457e0, stackSize= 63 KB, stackBase=0x1069b138, stackEnd=0x1068b140 (ErrEulaAppearError)
00;04;12;467: ErrEula :ErrorCode = 1054207
00:04:12:609: CSC: Product Code: WUP-N-HASE, Title Version (major): 13
00:04:12:611: CSC: Repaired: FALSE, Wagon: FALSE
00:04:12:616: CSC: InitialLaunch stage: 2
00:04:12:620: CSC: USB Storage Connected: TRUE, Device Type: NAND
00:04:12:640: CSC: RCA Enabled: FALSE, KeepAlive Enabled: TRUE, ParentControl Enable: FALSE
00:04:12:642: CSC: Check : /vol/storage_mlc01/usr/boss/00050010/10040100/user/common/ (-196631)
00:04:12:643: CSC: Check : /vol/storage_mlc01/usr/boss/00050010/10040100/user/80000006/ (0)
00:04:12:644: CSC: Boss Storage Exist: TRUE, NetworkID Assigned: FALSE, System Network Connected: TRUE
00:04:12:669: CSC: NIC Type: WIFI, DNS obtained by DHCP: TRUE, IP obtained by DHCP: TRUE
00:04:12:675: CSC: TV Port: HDMI, TV Aspect Ratio: 16:9
00:04:12:681: CSC: TV Resolution: TV_1080P
00:04:12:681: CSC: CODE: [HASE-0252-5375]
2017-02-28 01:03:02 - log collection event from pid 21
00:04:12:682: MCP: life time number of fatal errors - 366
This means that the number of fatal errors recorded by MCP is a pretty good indicator of how many times the console has crashed and thus been force restarted. Remeber we're talking fatal errors here - by definition, the console must crash when one occurs.
I agree that it's probably a good indicator for you, if you haven't played around with tickets, regions, updates and all that. Regarding what fatal means, you may have to bow to Nintendo's definition here, which seems to be 'something inconvenient happened', and certainly, the console must crash when one occurs is false in this realm.
For a bit of fun, here's a recent crash log off my system - 7.log (8 was a boring FSGetMountSourceFailed, which required a force reboot nonetheless). My current project sets up some code in the 0x60000000 area and you can see that's where the problem lied. A more recognizable log comes in the form of 98.log; where you can see a more standard homebrew exception handler gets in and causes the panic (again, thanks OSFatal). Every time something like that happens a force reboot is needed.
In 98 it's easier to see why the console is locked, but in 7, the OS still seems pretty much in control. I suppose on an actual dev unit, that you'd have active debugging at that point? Anyway, interesting read, and I understand why you drew the conclusion you did, even though I think it's apples and oranges compared to the poster's situation. Thanks for the details.
My first Wii U (which I bought using Youtube money uvu) was bought near launch date. Modding wasn't big back then. I just had Usb Loader on vwii. One game crashed and i thought ''eh it happens.'' But it broke my Wii u. Error code 160 1400. rip 2015 just got nintendont. Got a new Wii U free from a friend and it was outdated so I was able to use loaddiine. 5.5.1 couldn't at the time. Everything was peachy but I had bad internet one day so when loading loadiine in browser my Wii U crash. Turned it back on. Error code 160 1400. Rip 2016 LOL BE AFRAID. Wii U can brick just from a crash and no mistakes. Like I said before bought a used Wii U for 99 bucks and it's actually brand new as in it was bought wasn't used much and sold. 6 months old. Didn't came with gamepad or cables but I had those already. Wii was stronger than Wii U
u've got some bad luck with consoles. I actually own 2 wii-u's, both plugged in. my 5.3.2 system, or was 5.3.2, (now 5.5.1) was used for homebrew (loadiine before usb loading was possible), and my main console on 5.5.1 as well has been used for homebrew on both the wii u and vwii. both have crashed testing things before. neither has bricked.
u've got some bad luck with consoles. I actually own 2 wii-u's, both plugged in. my 5.3.2 system, or was 5.3.2, (now 5.5.1) was used for homebrew (loadiine before usb loading was possible), and my main console on 5.5.1 as well has been used for homebrew on both the wii u and vwii. both have crashed testing things before. neither has bricked.
He happened to kill TWO consoles and others who forced a shut off nearly one thousand times (800+) never even bricked a single one... I am not saying his wii Us didn't die. I am just saying: it is HIGHLY unlikely it was loadiine or nintendont or whatever....
I've not insulted u. if that's what happened, that's what happened. I will admit that there r a number of people here who do insult people who've bricked, usually the wii u and the 3ds, but I'm not one of those people. both r attributed to user error rather than hardware failure which is likely what happened to u.
Yeah, that's the big one. Quark's activity wouldn't be causing writes at the time of the panic (although some files might be open). We'll never know exactly what was being written on Kirby's at the time of the crashes, or what else was going on. Too many unknowns. Bad power pack used on both units? Marginal Wifi causing the wifi cards to draw more power than most peoples systems do? On and on.
Yeah, that's the big one. Quark's activity wouldn't be causing writes at the time of the panic (although some files might be open). We'll never know exactly what was being written on Kirby's at the time of the crashes, or what else was going on. Too many unknowns. Bad power pack used on both units? Marginal Wifi causing the wifi cards to draw more power than most peoples systems do? On and on.
yes, but it was certainly not homebrew or just bad luck TWICE! and other people having luck at over 800 instances? that kinda luck is not from this world.
so: as long as this is not scientifically cleared, I don't buy it.
That makes sense. I wasn't questioning the change in the numbers, just questioning what caused the jump.Ah, you have the advantage of knowing what you were doing at the time. Kind of an important detail , and one that the poster can't eloquently define. Should not, but they do:
00:14:36:996: Cleaning /vol/storage_mlc01/usr/import/crash
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Installation Failure detected
- Error value: -262208
- Package:
</vol/mcp_rawpkg/install/funkybarnup_rptik>
- Title: 0005000e-10118400 (0x0010)
- AppType: 0800001b
- Platform: Cafe
- Target dev: mlc01
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Installation failure log will be stored with error code '162-0000'
00:14:40:739: MCP: life time number of fatal errors - 362
00:14:40:740: MCP: storing current logs as '/vol/system/logs/63.log'
00:14:41:379: MCP: Finished storing current logs as '/vol/system/logs/63.dsc'
00:15:51:190: Cleaning /vol/storage_mlc01/usr/import/crash
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Installation Failure detected
- Error value: -262208
- Package:
</vol/mcp_rawpkg/install/funkybarnup_rptik>
- Title: 0005000e-10118400 (0x0010)
- AppType: 0800001b
- Platform: Cafe
- Target dev: mlc01
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Installation failure log will be stored with error code '162-0000'
00:15:54:462: MCP: life time number of fatal errors - 363
(forced a shutdown here to see if it counted, which you acknowledged it doesn't)
00:01:03:063: Cleaning /vol/storage_mlc01/usr/import/crash
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Installation Failure detected
- Error value: -262208
- Package:
</vol/mcp_rawpkg/install/funkybarnup_rptik>
- Title: 0005000e-10118400 (0x0010)
- AppType: 0800001b
- Platform: Cafe
- Target dev: mlc01
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Installation failure log will be stored with error code '162-0000'
00:01:05:638: MCP: life time number of fatal errors - 364
00:01:05:639: MCP: storing current logs as '/vol/system/logs/65.log'
00:01:06:182: MCP: Finished storing current logs as '/vol/system/logs/65.dsc'
Another log - can't reach update server
DRMAPP: error code 1054207
DRMAPP: post error state 19
DRMAPP: Patch: scene state: 13 -> 40
00;03;16;928: ErrEula: thread=0x100457e0, stackSize= 63 KB, stackBase=0x1069b138, stackEnd=0x1068b140 (ErrEulaAppearError)
00;03;16;928: ErrEula :ErrorCode = 1054207
00;03;16;935: ErrEula: thread=0x11beaee8, stackSize= 16 KB, stackBase=0x11beaed8, stackEnd=0x11be6ed8 (ErrEulaDrawTV)
00;03;16;935: ErrEula: thread=0x11bef778, stackSize= 16 KB, stackBase=0x11bef768, stackEnd=0x11beb768 (ErrEulaDrawDRC)
00:03:17:073: CSC: Product Code: WUP-N-HASE, Title Version (major): 13
00:03:17:074: CSC: Repaired: FALSE, Wagon: FALSE
00;03;16;943: ErrEula: thread=0x100457e0, stackSize= 63 KB, stackBase=0x1069b138, stackEnd=0x1068b140 (ErrEulaCalc)
00:03:17:079: CSC: InitialLaunch stage: 2
00:03:17:083: CSC: USB Storage Connected: TRUE, Device Type: NAND
00:03:17:104: CSC: RCA Enabled: FALSE, KeepAlive Enabled: TRUE, ParentControl Enable: FALSE
00:03:17:108: CSC: Check : /vol/storage_mlc01/usr/boss/00050010/10040100/user/common/ (-196631)
00:03:17:109: CSC: Check : /vol/storage_mlc01/usr/boss/00050010/10040100/user/80000006/ (0)
00:03:17:110: CSC: Boss Storage Exist: TRUE, NetworkID Assigned: FALSE, System Network Connected: TRUE
00:03:17:135: CSC: NIC Type: WIFI, DNS obtained by DHCP: TRUE, IP obtained by DHCP: TRUE
00:03:17:141: CSC: TV Port: HDMI, TV Aspect Ratio: 16:9
00:03:17:146: CSC: TV Resolution: TV_1080P
00:03:17:147: CSC: CODE: [HASE-0252-5375]
2017-02-28 01:02:07 - log collection event from pid 21
00;03;17;027: (1)5.5.1 U
00;03;17;027: (2)WUP-101(02)
00;03;17;027: (3)FW114860859
00;03;17;027: (4)HASE-0252-5375
00:03:17:151: MCP: life time number of fatal errors - 365
00:03:17:152: MCP: storing current logs as '/vol/system/logs/66.log'
00:03:17:674: MCP: Finished storing current logs as '/vol/system/logs/66.dsc'
DRMAPP: Finding package with titleId=0005000e10178f00, mediaType=2
DRMAPP: manage state 7 -> 11
DRMAPP: Patch: scene state: 7 -> 11
DRMAPP: kick task: 7
DRMAPP: manage state 11 -> 13
DRMAPP: Patch: scene state: 11 -> 13
DRMAPP: Error Code: 1054207
DRMAPP: manage error occurred:
DRMAPP: error code 1054207
DRMAPP: post error state 19
DRMAPP: Patch: scene state: 13 -> 40
00;04;12;467: ErrEula: thread=0x100457e0, stackSize= 63 KB, stackBase=0x1069b138, stackEnd=0x1068b140 (ErrEulaAppearError)
00;04;12;467: ErrEula :ErrorCode = 1054207
00:04:12:609: CSC: Product Code: WUP-N-HASE, Title Version (major): 13
00:04:12:611: CSC: Repaired: FALSE, Wagon: FALSE
00:04:12:616: CSC: InitialLaunch stage: 2
00:04:12:620: CSC: USB Storage Connected: TRUE, Device Type: NAND
00:04:12:640: CSC: RCA Enabled: FALSE, KeepAlive Enabled: TRUE, ParentControl Enable: FALSE
00:04:12:642: CSC: Check : /vol/storage_mlc01/usr/boss/00050010/10040100/user/common/ (-196631)
00:04:12:643: CSC: Check : /vol/storage_mlc01/usr/boss/00050010/10040100/user/80000006/ (0)
00:04:12:644: CSC: Boss Storage Exist: TRUE, NetworkID Assigned: FALSE, System Network Connected: TRUE
00:04:12:669: CSC: NIC Type: WIFI, DNS obtained by DHCP: TRUE, IP obtained by DHCP: TRUE
00:04:12:675: CSC: TV Port: HDMI, TV Aspect Ratio: 16:9
00:04:12:681: CSC: TV Resolution: TV_1080P
00:04:12:681: CSC: CODE: [HASE-0252-5375]
2017-02-28 01:03:02 - log collection event from pid 21
00:04:12:682: MCP: life time number of fatal errors - 366
I agree that it's probably a good indicator for you, if you haven't played around with tickets, regions, updates and all that. Regarding what fatal means, you may have to bow to Nintendo's definition here, which seems to be 'something inconvenient happened', and certainly, the console must crash when one occurs is false in this realm.
In 98 it's easier to see why the console is locked, but in 7, the OS still seems pretty much in control. I suppose on an actual dev unit, that you'd have active debugging at that point? Anyway, interesting read, and I understand why you drew the conclusion you did, even though I think it's apples and oranges compared to the poster's situation. Thanks for the details.
Well, there you go, looks like I stand corrected on a few things. Nicely done!
As a minor aside, log 7 is a proper crash, it's just that my exception handler didn't catch it (was it kernelmode? Don't remember the exact bug) so the final log looks a bit different. Being a homebrew guy, I don't get the privilege of a dev unit (signing a NDA would be suicide) so all this is happening on an EU retail unit. I'd assume you're right about dev units and debugging though.
I'm also going to be looking at these logs a heck of a lot more if they catch kernelmode exceptions.
yes, but it was certainly not homebrew or just bad luck TWICE! and other people having luck at over 800 instances? that kinda luck is not from this world.
so: as long as this is not scientifically cleared, I don't buy it.
yeah tbh i crashed my wiiu hunderds of times i was the main tester of fix94 nintendont stuff on wiiu my vwii crashed like 40 times a day while testing stuff and i had to literaly pull the plug hunderds of times and dont get me started on browser hax so manny forced shutdowns i lost count and my wiiu is just fine same with other peoples, my guess is he has some defective part or his wiiu gets some power surges or something or like someone sugested a defective power supply cord that damages stuff.
Even knowing my stuff I still avoid installing coldboot haxchi since it is risky. Even with legit dr kawashima game from eShop I just use normal haxchi so no accident could brick my system.
I wonder why so many people are jumping feet first to the abyss - so readily and with so many disastrous results...
You're needlessly scared, if you follow the guide exactly as is written, it will work properly. I did it a few months ago, read everything carefully, took my time, and it worked flawlessly, was a very quick process and as long as you do exactly as it says it's actually a very simple process as well.
It's the first Nintendo Switch firmware update of 2024. Made available as of today is system software version 18.0.0, marking a new milestone. According to the patch...
Emulator takedowns continue. Not long after its first release, Suyu emulator has been removed from GitLab via a DMCA takedown. Suyu was a Nintendo Switch emulator...
After a couple days of Nintendo releasing their 18.0.0 firmware update, @SciresM releases a brand new update to his Atmosphere NX custom firmware for the Nintendo...
Today, April 8th, 2024, at 4PM PT, marks the day in which Nintendo permanently ends support for both the 3DS and the Wii U online services, which include co-op play...
Hello, GBAtemp members! After a prolonged absence, I am delighted to announce my return and upgraded form to you today...
Introducing tempBOT AI 🤖
As the embodiment...
Yet another casualty goes down in the never-ending battle of copyright enforcement, and this time, it hit a big website which was the host for many fangames based and...
The highly popular and accurate FPGA hardware, MisterFGPA, has received today a brand new update with a long-awaited feature, or rather, a new core for hardcore...
The 2nd biggest technology company in the world, Apple, is being sued by none other than the Department of Justice of the United States, filed for antitrust...
With Apple having recently updated their guidelines for the App Store, iOS users have been left to speculate on specific wording and whether retro emulators as we...
The romhacking community is always a source for new ways to play retro games, from completely new levels or stages, characters, quality of life improvements, to flat...
It's the first Nintendo Switch firmware update of 2024. Made available as of today is system software version 18.0.0, marking a new milestone. According to the patch...
Today, April 8th, 2024, at 4PM PT, marks the day in which Nintendo permanently ends support for both the 3DS and the Wii U online services, which include co-op play...
Hello, GBAtemp members! After a prolonged absence, I am delighted to announce my return and upgraded form to you today...
Introducing tempBOT AI 🤖
As the embodiment...
Emulator takedowns continue. Not long after its first release, Suyu emulator has been removed from GitLab via a DMCA takedown. Suyu was a Nintendo Switch emulator...
With Apple having recently updated their guidelines for the App Store, iOS users have been left to speculate on specific wording and whether retro emulators as we...
After a couple days of Nintendo releasing their 18.0.0 firmware update, @SciresM releases a brand new update to his Atmosphere NX custom firmware for the Nintendo...
The 2nd biggest technology company in the world, Apple, is being sued by none other than the Department of Justice of the United States, filed for antitrust...
The time has finally come, and after many, many years (if not decades) of Apple users having to side load emulator apps into their iOS devices through unofficial...
Yet another casualty goes down in the never-ending battle of copyright enforcement, and this time, it hit a big website which was the host for many fangames based and...
Nintendo has recently announced through their social media accounts that a new Indie World stream will be airing tomorrow, scheduled for April 17th, 2024 at 7 a.m. PT...
