In order to deploy a bomb, the following requirements must be met: Nuclear Bombs are deployed onto specific provinces.
The final technology, Nuclear Bombs, allows the country to produce and stockpile nuclear bombs. Built nuclear reactors provide the state with enriched uranium for use in nuclear weapons, but have no effect without the requisite technology to make nuclear bombs. The second technology, Nuclear Reactor, unlocks the state level building titled "Nuclear Reactor" which can be found in the Construction screen. The first technology, Atomic Research, gives a +4% research speed bonus. If you spot a mistake, please help with fixing it.ĭeploying nuclear bombs needs the right technologies from Engineering technology, special resource, and specific aircraft to deliver the bombs. \.\Binaries\autoexec.This is a community maintained wiki. It could be that it will tell you the exact error for the lines. It outputs the engine return messages for config executes. Launch.txt is a very valuable source of information for testing configs. I'll play around with autoexecs soon, if I find anything interesting I'll let you know.Įdit: You may also want to take a peek at the log file in MyDocuments/my games/UnrealEngine3/ShooterGame/Logs/Launch.txt I haven't played around with migrating configs to autoexec though I'm planning to soon, but my best guess would be that one or more of these elements are restricted for some reason (execution ones perhaps?).īest route of action would be to create a new autoexec and slowly add more and more lines trying to find which ones are restricted. If a server won't let you in because of your autoexec, 99% of the time it's because a command in your autoexec is restricted or banned, for example 'show particles', 'show levelcoloration' etc. And my seemingly only other option "HUDWidgetSet_" cannot be used in an autoexec.
#Best dirty bomb config file code
I'm guessing these are remnants of old code being injected due to some kind of bug in the commands (which is further hinted at by the appearance of "Skew=0", since that hasn't worked for a long time).Īnybody else have some luck getting this to work?Įdit: it seems like the "Set" command is blocked on servers. It even adds HUD elements that aren't normally listed, like "WeaponInventory", "GameStateNotification" and "ChatLog" (the chat log is actually called ConsoleMessageLog right now). Upon investigating the ShooterUI.ini file it would seem like the console commands change more than I'm specifically listing.
I'm including empty HA="",VA="" and other normally useless code like PixelOffset=(X=0,Y=0) because when setting these through the console you're not clearing old settings, and by not including them old PixelOffset values will remain. Quick joining just gets stuck and if I try to join through the server browser I get an error saying that I lost connection to the server.
#Best dirty bomb config file Offline
All commands go through and the HUD looks exactly like it should in offline mode (tutorial+showdebughud), but for some reason I cannot connect to a server with it. I'm trying to migrate my custom HUD entirely to console commands to be ran through an autoexec file.
0 kommentar(er)
