#ColAndreas open.mp Component
42 messages ยท Page 1 of 1 (latest)
Yo, sounds good but what difference does it make ?
It's just a component now instead of legacy plugin, to be used by now more advanced NPC components we are currently making
tuff
components are loaded through server.cfg?
good job btw!
Lol thanks, have to adjust that ๐
Loading component ColAndreas.so
Failed to load component: /usr/lib/i386-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by components/ColAndreas.so).
Loading component ColAndreas_static.so
Failed to load component: /usr/lib/i386-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.32' not found (required by components/ColAndreas_static.so).
Try installing required libraries for 32-bit compatibility
dpkg --add-architecture i386 && \
apt-get update && \
apt-get upgrade -y && \
apt-get install -y \
libstdc++6:i386 \
libatomic1:i386 \
@low ore doesn't work for sampctl:
Your pawn.json is wrong, as it says "Pottus" instead of "Knogle" and doesn't target the right files
Also, maybe you should separate versions like 1.5.0 and 1.5.0-omp so there's no confusion between the components and the old plugin
Thanks, also thank you regarding the pawn.json, didn't even know what it is for!
Can the ci.yml still compile dlls for the old plugin on the master branch ? Or is it only made to compile omp components ?
only for the omp components
If you only plan to maintain the component, you might wanna merge your omp branch on master so sampctl gets it from there
@low ore
After all of my attempts to make your repo work with sampctl, we came to the conclusion that it would be better to just have everything in the master branch
I don't have the pipelines to create the plugin anymore though, maybe you should make a release with the same assets from Pottus/ColAndreas for the v1.5.0 version and then do the following releases on v1.x.x-omp
ah alright, so you say, merging the new branch into master?
and keep maintaining it on master?
yep, check this out: https://github.com/San-Andreas-Online/ColAndreas/
I added the old release for the 1.5.0 plugin, so sampctl can find it if somebody ever needs to switch to it for some reason
and then I kept on going with omp releases
Would you mind to continue maintaining it maybe? Because tbh, i just wanted to port it to omp, and that's it
I have no skills in C or whatever it is you did in the pipeline lmao
I just did the sampctl thing
ok^^
though I don't mind if you transfer ownership of the repo to San-Andreas-Online
i can fix that
The pawn.json looks alright, and the version number shouldn't create conflicts and whatnot anymore
But I can't try it out with sampctl right now, I'm not at home
I'll let you know tomorrow if I can find some time
There are two branches, which version should I download? 
Damn I thought I had answered
So I made the tests Sunday and it was all good for the download but I had runtime problems with my game mode, I don't think it was related to CA
The one in releases