Hi Guys

Just pushed an experimental update to git.

Re did the naming of the packets so we don't have to rely on binkd to
rename them - but don't call maintenance more than once a minute.

Added a league number, so a node can participate in multiple games.

Added a node number, this is used when making a packet name.

It's experimental and I haven't tested it yet, going to wait a until
tomorrow to see if it works.

Andrew

--- WWIV 5.3.0.development
* Origin: System 17 - andrew.homeunix.org:2025 (21:1/188.2)

RE: Galactic Dynasty Update
BY: Apam #1 @1

It's experimental and I haven't tested it yet, going to wait a until tomorrow to see if it works.

Actually I decided to test it right away, it works now so I made a
release.

https://github.com/apamment/galactic-dynasty/releases/tag/v0.2.0-alpha2

Andrew

--- WWIV 5.3.0.development
* Origin: System 17 - andrew.homeunix.org:2025 (21:1/188.2)

RE: Re: Galactic Dynasty Update
BY: Apam #1 @1

Actually I decided to test it right away, it works now so I made a
release.

https://github.com/apamment/galactic-dynasty/releases/tag/v0.2.0-alpha
2

If you downloaded before this message, might want to download again,
found a silly bug that didn't rear it's ugly head while testing :)

Andrew

--- WWIV 5.3.0.development
* Origin: System 17 - andrew.homeunix.org:2025 (21:1/188.2)

On 03/16/17, Apam pondered and said...

Actually I decided to test it right away, it works now so I made a release.

https://github.com/apamment/galactic-dynasty/releases/tag/v0.2.0-alpha2

So is this V3?

What's the best way to update? Do I copy all files over the top of what's
in the dir? And should I just do a reset each time or is that not needed?

Can I distribute these updates via FSX_SOFT? If you add a file_id.diz and
point folks to this echo for support etc. that might be the way to go? Also keep the file name the same and when we hatch it out it the 'replace' verb could just swap out the latest version for the last older one on BBS that
honor that when file tossing.... just a thought :)

Best, Paul

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

RE: Re: Galactic Dynasty Update
BY: Avon(21:1/101)

What's the best way to update? Do I copy all files over the top of wha
t's
in the dir? And should I just do a reset each time or is that not need
ed?

Just copy the files over the top. You will need to reset if you haven't
since I added protection.

You will also need to update your BBS.CFG file to have a LeagueNo and a
NodeNo

LeagueNo is the same for every BBS in the game, and NodeNo is different
for each BBS in the game.

Have a look at example.cfg for an example :)

Andrew

--- WWIV 5.3.0.development
* Origin: System 17 - andrew.homeunix.org:2025 (21:1/188.2)

On 03/17/17, Apam pondered and said...

You will also need to update your BBS.CFG file to have a LeagueNo and a NodeNo

LeagueNo is the same for every BBS in the game, and NodeNo is different for each BBS in the game.

I did thanks. Can we extend things a bit?

In the case of fsxNet lets say there are nodes in differing NETs like
21:2/123 and 21:1/456 and they want to play this using their HUB systems 21:2/100 and 21:1/100 as the place to send their interBBS files to.

Currently node numbers are 1-99 so if a node wanted to use their /123 address they are scuppered. Equally if to nodes in different nets want to use /123
you can't tell if it's 21:1/123 or 21:2/123 at the moment.

I can see how most nodes could set their HUB to send interBBS files to and
the HUB would have all it's nodes as links in the config file to pass traffic on to. In the case of differing NETs like 21:1/xxx and 21:2/xxx I'm wondering if a routing rule can be added to Galactic Dynasty (GD) to ensure packets
find their way to a nominated node in the config (like a HUB) that will be
able to pass on traffic to the correct system?

Best, Paul

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

RE: Re: Galactic Dynasty Update
BY: Avon(21:1/101)

I did thanks. Can we extend things a bit?

Ok, I lied a little bit, it's really 0-255 as it uses 2 hex characters
in the filename.

The node number is just used to ensure no collisions with packet files,
I can't make it bigger and maintain 8.3 filenames.

I'm not sure how things would work with more than 255 players anyway -
actually I'm not sure how it would work with more than 2 :P

If you really want to make the node number correspond with the fsx node
number, why not -100 from the 1 net and as is for the 2 net.

Andrew

--- WWIV 5.3.0.development
* Origin: System 17 - andrew.homeunix.org:2025 (21:1/188.2)

On 03/18/17, Apam pondered and said...

I'm not sure how things would work with more than 255 players anyway - actually I'm not sure how it would work with more than 2 :P

:)

If you really want to make the node number correspond with the fsx node number, why not -100 from the 1 net and as is for the 2 net.

It's an idea... but you're right it's really just a case of numbering each system upwards from 1 onwards depending on who arrives first etc. Perhaps I make the HUB system 1 and go up from there.

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

On 03/27/17, Flynn pondered and said...

All updated here as well...

Thanks Ron.

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

Hi apam

System Name = 2nd Choice Core (21:1/152)
League Number = 21

You want Node Numer = 6

Thank you for this and done.

Ian 2nd choice Core Nz

--- Mystic BBS v1.12 A31 (Windows)
* Origin: 2nd Choice Core|New Zealand (21:1/152)

Hi Paul

League Number = 21
Node Number = 2

Hi Ian this bit ^^^^^ should be node 6 :)

Andrew did point this out to me thank you and hope all things going well
with thae game now

Ian 2nd Choice Core NZ

--- Mystic BBS v1.12 A31 (Windows)
* Origin: 2nd Choice Core|New Zealand (21:1/152)