Railworks America

I'm trying to help a member out by modifying the xml by adding some different assets to the list. It is OK to just copy and paste them from one xml to another isn't it? I haven't changed anything but adding assets and pretty careful to make sure and not screw up the syntax.

I really would do that in the TS editor itself.
On the other hand I never got problems when removing some unnecessary entries.

buzz456 wrote:I'm trying to help a member out by modifying the xml by adding some different assets to the list. It is OK to just copy and paste them from one xml to another isn't it? I haven't changed anything but adding assets and pretty careful to make sure and not screw up the syntax.

yes you can but erase the id numbers and just leave the ("") marks. When I'm at my game computer later I can explain better with pictures if need be.

JohnS wrote:

buzz456 wrote:I'm trying to help a member out by modifying the xml by adding some different assets to the list. It is OK to just copy and paste them from one xml to another isn't it? I haven't changed anything but adding assets and pretty careful to make sure and not screw up the syntax.

yes you can but erase the id numbers and just leave the ("") marks. When I'm at my game computer later I can explain better with pictures if need be.

John is quite right. I've done it numerous time with another twist - re the ID no. I keep the number but alter it by an increament!!!

*** By the way, this prodedure can be applied to any .bin file - whether a scenery object or any rolling stock. The only danger, while you do a cut-paste is to forget to grab a line or two of code; thus «code abc» to «\code abc» must be grabbed inclusively. Since human error is always a possibility, always make a backup of the original .bin file

Is there any rule for numbers like must they be ascending or anything like that?

Maybe not a rule of sorts, but if you look at how other things are number sequenced within the .xml files, they are mostly based on the hex decimal system and use a base 16, or powers of 16 for the sequencing of the numbers. So, take your first ID number add 16 and you have the next ID number in the sequence. I believe those numbers are called UUIDs.

RailWanderer wrote:Maybe not a rule of sorts, but if you look at how other things are number sequenced within the .xml files, they are mostly based on the hex decimal system and use a base 16, or powers of 16 for the sequencing of the numbers. So, take your first ID number add 16 and you have the next ID number in the sequence. I believe those numbers are called UUIDs.

Yep! that's exactly how I proceed and never had any problems.

They just have to be unique in the blueprint.