Knowledge Base

I wanted to try to make some code changes to Darkflameserver Lego Universe, which of course necessitates compiling the application.

I cloned the repository and made a branch, and wrote my changes. Of course I used the main branch, instead of whatever commit would have been the last tag. Once I got the compilation process working, my database was migrated to the latest schema.

While my changes worked, I learned that some interim commits which haven't been noticed yet broke the bananas and mermaid head item drops. They do not work at all! That is, none of those items drop, which will completely break the storyline missions. So I then reverted to the correct commit for whatever the last tag was, but my database had already been migrated. Apparently the project changed the datatype for a column for character id. And rather than trying to restore from backup (which I did have), I figured it would be easier to just rebase my commit on top of the commit that had updated that database schema change. That commit came before any of the faffing around with the bananas.

And all this took quite some time, to iterate and realize the problem, and decide the path to rollback.

So the next time I want to implement changes for myself in any project, I will work more carefully with commits.