Port 4901 or 4091?
Closed this issue · 6 comments
It seems in the latest version, the gameport = 4901 was changed to 4091. Is this correct or is this a typo. This would certainly cause issues in connection if it's the case.
I'm not exactly certain what you mean by latest version, but we've been running with 4091 for a couple of years now I believe. I know it was a purposeful change from the old port in lich mainline, I don't remember the reasoning anymore.
It should be noted that the port that actually matters if I'm remembering correctly is the 11024 port for DR.
OK, I confirm that the port 4901 and 4091 are irrelevant. I noticed that the 4901 on line 10561 has been updated to reflect the port 11024. This works.
Next question, when running frostbite, there's a repo update that happens after startup that seems to revert lich back to 4.6.49:
[repository: Lich has been updated to version 4.6.49.]
[repository: Changes will take effect next time you start Lich.]
[repository: downloading map database...]
I'm using the 4.6.49 data files with this fork of the .rbw
Yeah, that will happen if you haven't switched to this fork via dependency.lic. You can manually disable the repository update of lich with something like ;repository unset-lich-updatable
I finally got this to work! FYI I'm working on Mac OSX Mojave 10.14.3
- Installed lich 4.6.49
- Cloned this Git repo and pulled the .rbw out and overwrite the 4.6.49 version.
- Changed port back to 4901. (not sure this did anything)
- Updated Ruby to 2.3.0 and 'set rbenv local 2.3.0'
- Reinstalled sqlite3: 'sudo gem install sqlite3'
- Start lich: 'sudo ruby ./lich/lich.rbw --dragonrealms --frostbite
- Download license file ;repository download dependency.lic
- Trust Dependency failed, but I think it doesn't matter: ;trust dependency
- Install dependency. This took about 5 minutes. : ;dependency install
- Use fork: ;e use_lich_fork
- Restart Lich
- I had to repeat step 2 because the Lich had replaced with 4.6.49 on first startup
- After restart, Lich used the new fork and updated properly.
Step 4 was critical. Before this it kept opening the ruby script in a separate exec terminal and wouldn't run unless I clicked the exec window repeatedly.
As a P.S. comment, GTK2 was causing problems on Mac because it was opening the executable terminal window separately which required the executable window to be active in order to function. Uninstalling GTK2 and running Frostbite solved the problem.