@DarkComplicated
Quote: "lol it happened to be unused images and models and 1 song never used in my game that took up more then 100Mb of space so now my games only 43Mb but it still having trouble posting"
Be aware that when you create a final exe, that everything in the directory is going to be compiled into that exe whether it's used or not. That includes things like text files, word documents, junk, previously made exes with different names, even the .tmp file that may be made when using DarkEdit to code your source - everything!
A good practice might be to make sure the directory is absolutely clean of everything except what you need for the game. Then, to avoid compiling anything extra (like the tmp file), use the command line to create the exe from the source:
COMMAND LINE COMPILER
If you prefer to use an external editor to edit your programs, you can use the command line compiler. The command line compiler allows you to compile, run and build executables without entering DarkBASIC.
1. Compiling Externally
DB.EXE -c test.dba
2. Running Externally
DB.EXE -x test.dba
3. Building An Executable Externally (no media)
DB.EXE -b "small.exe" test.dba
4. Building An Executable Externally (with media)
DB.EXE -f "large.exe" test.dba
5. Using Relative and Absolute Paths
C:\Program Files\Dark Basic Software\Dark Basic\DB.EXE -f "d:\mywork\large.exe" test.dba
When using relative paths, ensure your current directory is the project directory containing the DBA program. Your current directory will be used to write the final executable and DBCompile.LOG file. You can override this behaviour by using Absolute paths when asked for a filename in the command line. The DBCompile.LOG file contains any error messages, or completion strings returned by the compiler. The file will also include the line number at which the syntax/runtime error occurred.
Enjoy your day.
