Matrix Games Forums

Forums  Register  Login  Photo Gallery  Member List  Search  Calendars  FAQ 

My Profile  Inbox  Address Book  My Subscription  My Forums  Log Out

Just what the editor needed!(lol)

 
View related threads: (in this forum | in all forums)

Logged in as: Guest
Users viewing this topic: none
  Printable Version
All Forums >> [New Releases from Matrix Games] >> War in the Pacific: Admiral's Edition >> Scenario Design and Modding >> Just what the editor needed!(lol) Page: [1]
Login
Message << Older Topic   Newer Topic >>
Just what the editor needed!(lol) - 3/2/2019 3:28:18 PM   
m10bob


Posts: 8623
Joined: 11/3/2002
From: Dismal Seepage Indiana
Status: offline
I use the editor a lot for implementing units to the game with much research done.(I've been retired now for some time, so time is what I have more than most.
I love the advances Sid has made in his RHS mod and wanted to add them to my data without "printing over" the data I had created.
The solution was obvious!..I just went to the scenario files and copy pasted the .dat files of particular scenarios, (122 and 123 in my case into a separate folder on the desktop, and after installing newer updates to RHS I will then just copy paste my stuff back to the scenario I am using.


UPDATE!!!!! In a prior post I suggested you might need to open two separate WITP editors..This is NOT correct!

Instead, create two folders on your desktop...Then, go to your scenario folder within the game itself and locate the scenario .dat files where you made all your mods..(In my case, I used scenario 122..Copy paste all of those to one of the folders you just created on your desktop..
Next, locate all the .dat files in the same game scenario folder where you want the modded files to appear...For instance, scenario 123...Now, copy paste all of the .dat files from scenario 123 to that other folder on your desktop...
(Be sure you give a name to both of those desktop folders!

Now, go to the modded folder and rename all of those .dat file names to whatever scenario they will be going to.
(In my case it was 122 which I was going to move to 123, so I named the modded 122 files to 123...Next, I copy pasted those renamed files to the main scenario folder in the game..(It will ask if you wish to over-ride the existing files)..Jut say "yes" and move to the next re-named .dat files..repeat.
Remember...you have already SAVED al the stock 123 .dat files to that 2nd desktop folder if you ever want to go back.

In my mods, I have added some Chines planes, removed some older Hawks which were already gone by the time of Pearl Harbor...I marked all my USN replenishment CVE's with an "R" behind the ships name(so I will remember them at a glance), I listed the Sangamon class CVE's as CVL's to remember they carried much more fuel and plane capacity than true CVE's.(Sangamon's were converted tankers, not AK's...and could support more ships over a longer distance.)
I also increased a few base sizes to match research done ref places like Exmouth Aus.
I also renamed the USMC Rgt's back to the "type" of units as RGT's, instead of RCT's.
(The U.S.Army used RCT's, not the Gyrenes, and not all army divisions used them, just some.
Further..theterm Regimental Combat Team did not refer just to the nomenclature, but to the mission as well, and was part of the official title of the unit...Gyrnes worth their salt will always brag of which Regiment they belonged to, but will NEVER allude to a "regimental combat team.")

Army Rangers (like myself) will generally not allude to themselves as paratroopers...but to "Ranger"..(which nowadays are all airborne qualified to the best of my knowledge.)

I suggest before you do this...ALWAYS check to make sure the slots you will be placing them to are still open/empty slots because Sid has a habit of adding things to his revisions, lol


For modders like Sid, this is not complex whatsoever, but a country bumpkin like me...well, the idea did not come to me "naturally"...

< Message edited by m10bob -- 3/3/2019 12:36:45 PM >


_____________________________



Post #: 1
RE: Just what the editor needed!(lol) - 3/3/2019 12:53:51 PM   
m10bob


Posts: 8623
Joined: 11/3/2002
From: Dismal Seepage Indiana
Status: offline
Bumped just so folks interested might re-read my original post with new info...

_____________________________




(in reply to m10bob)
Post #: 2
RE: Just what the editor needed!(lol) - 3/9/2019 2:52:45 PM   
el cid again

 

Posts: 16540
Joined: 10/10/2005
Status: offline
You may do as many scenarios as you wish in the SAME folder so long as you
understand what they need? IF you just do scenario (SCEN) files, AND IF
none of them have locations that differ from other scenarios, no problem.
But, for example, if you mix stock and RHS with different map systems,
you may STILL put everything in the same folder. Just be sure to change
the map related files if you change folders. That includes the three
pw...dat files and map art. For RHS users this is routine - we change
these files at the start of every season (Winter, Spring, Monsoon and Fall).
This permits special effects - construction, deconstruction, effects of
weather on rivers, lakes, oceans, trails, etc. To some extent we show this
on maps. There are different maps for these seasons, and markings on the maps
to remind players of things like a "Winter ice bridge" or "Trails in brown
(that is, in Monsoon affected climates) disappear in Monsoon" in all seasons.
And yes, RHS pwhexe.dat files have all trails defined. This so that movement
and supply will tend to channel along historical (and geographically favorable
routes).

(in reply to m10bob)
Post #: 3
Page:   [1]
All Forums >> [New Releases from Matrix Games] >> War in the Pacific: Admiral's Edition >> Scenario Design and Modding >> Just what the editor needed!(lol) Page: [1]
Jump to:





New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts


Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI

0.105