• Check out the results of the Techtree Contest #19!
  • Listen to a special audio message from Bill Roper to the Hive Workshop community (Bill is a former Vice President of Blizzard Entertainment, Producer, Designer, Musician, Voice Actor) 🔗Click here to hear his message!
  • Read Evilhog's interview with Gregory Alper, the original composer of the music for WarCraft: Orcs & Humans 🔗Click here to read the full interview.
  • Create a void inspired texture for Warcraft 3 and enter Hive's 34th Texturing Contest: Void! Click here to enter!
  • The Hive's 22nd Icon Contest: Creep Abilities is now concluded, time to vote for your favourite set of icons! Click here to vote!

High Resolution Loading Screens

Does this not work in ultrawide resolutions? This seems to be what I get when I try to make them 21:9 or 21:10:
It's limited to 16:9

For anyone who thinks 3840x2160 resolution is for fools: Yes, fortunately 2560x1440 is also supported.
You can use lots of options,
640x360
854x480
1024x576
1280x720
1920x1080
2560x1440
3840x2160
5120x2880
7680x4320
10240x5760
15360x8640
30720x17280
etc


On multiplayer, 1080p makes the most sense, as 4k+ file size is pretty hefty, although we now have 512mb file size limit
If you're making a single player campaign, or want to utilize local files/separate asset installer, you can use higher quality ones
 
I'm working on a map using typescript and I've found that using the 'LoadingScreen.mdx' file linked in this guide seems to cause a build issue.

npm run build > [email protected] build > ts-node --transpile-only scripts/build.ts [2025-09-24 05:47:17] info: Modifying tsconfig.json to work with war3-transformer... [2025-09-24 05:47:17] info: Transpiling TypeScript to Lua... [2025-09-24 05:47:19] info: Creating w3x archive... Error: ByteStream: readInt32: premature end - want 4 bytes but have 3

I'm certain it's the 'LoadingScreen.mdx' file causing the problem, as I tested changing only this file and it is the difference between running successful and unsuccessful builds.

Not sure if anyone else who has used W3TS to also develop maps has also run into this issue?

Are there alternative ways to add a custom load screen to my map that I can try?

Edit: The issue doesn't seem to be anything to do with this guide. Even when I try to simply add text (without a custom image) to a loading screen, then save my map, then run npm run build, I get the same error.
 
Last edited:
Back
Top