![]() |
|
|
|
#1
|
|||
|
Having worked with eqemu now for a bit, I think a big problem for classic mechanics, as opposed to classic data changes in the DB, is that you're basically stuck recompiling the server for every era, then having to deploy that whole new batch of binaries to "implement" the era. It's a pretty big headache.
(Idea for the p99 devs): This is the reason I went with a Docker approach for my little test server, since you can just build multiple docker images of the code with whatever compile time constants you want, then deploy them on the fly just by changing the image tag. Takes like 60 seconds. If you wanna see how I do it: https://github.com/dbsanfte/eqemu-server-docker You can use Docker build-args to pass in compile time constants to the compiler (admittedly I haven't put these in the Dockerfile yet but it's trivial), then do something like: docker build --build-arg era=0 -t eqemu-server:march-1999 . docker build --build-arg era=1 -t eqemu-server:april-1999 . docker build --build-arg era=2 -t eqemu-server:may-1999 . Etc. | ||
|
Last edited by Dolalin; 02-21-2020 at 03:32 AM..
|
|
||
|
#2
|
|||
|
/offtopic reply - Oof, nice work Dolalin!
Yeah I'm using rusty halberds on my enchanter pet on green (level 15 currently) until charm becomes viable. Imagine a hasted pet with a weighted axe (https://wiki.project1999.com/A_Weighted_Axe)... might be worth spinning up a test eqemu server just to find out [You must be logged in to view images. Log in or Register.] (assuming the "no pet equip" is set in the database rather than in 20 year old c/c++ spaghetti code). Incidently, did anyone actually use that axe on Live? For pvp? For pull agro? | ||
|
|
|||
|
#3
|
||||
|
Quote:
| |||
|
|
||||
![]() |
|
|