I have been making my own compatibility mod for Angels-Bobs-SpaceAge and for some reason, only with rso installed, tungsten ore keeps showing up on nauvis.
I have been trying to stop it from doing that very unsuccessfully.
So now I'm here trying to ask for help.

It's a bit of conflict - thats due to bob's having a tungsten ore so when it's present it is configured to be placed on nauvis. I think it might need some additional conditions there but I'm not sure atm if moving it away won't make bob's set problematic with Space Age.

If it's just bobs I'm not entirely sure, but as far as I can tell angels lets you make tungsten ore through sorting.
Also additionally, with space age installed you can't even mine the tungsten that generates since it requires the mining drills from vulcanus.

That being said, the main question I have, since I am making my own mod, [how] would I be able to overwrite that for the time being?

At this point this is an entry in bob's mods config inside RSO so it can't be easily overwritten. And with Angels it will get actually mineable because you will be able to sort it out most likely. So it really depends on what kind of mod is used to make bob's work with Space Age and how it handles this.

Well part of it is that I'm trying to make a mod to make bobs and angels compatible with space age.
Though since I'm making it mostly for myself I would have just disabled it in the map generation settings, but it doesn't show up there for some reason.
And turning off the tungsten ore on vulcanus only gets rid of the ore on vulcanus.

Did you try to use this one:
https://mods.factorio.com/mod/omniab-space-age-compat
I used it but also had Space is Fake so not sure how well it would work with full Space Age.

I did try all that I could find, including that one, though I found they didn't quite do what I wanted, which is why I started making my own.

Best way to do this would be to adjust bobs config in a separate config that I could add for your new mod - then it would be active only with your mod present and could do exactly what needed for it.

I'm not sure what to adjust in the bobs config since without rso it doesn't spawn tungsten on nauvis.
At least while angels ores are present I imagine.

I'm guessing that without RSO bob's has some additional conditions on tungsten that RSO is not detecting properly. I'm mainly checking if ore has an autoplace but taht has gotten complicated with SA so it might not be working correctly. If tungsten is defined in bob's config for nauvis it will spawn there - so removing it from separate config added when your mod is present would drop it.

I'll see what I can find, but probably not tonight.

A possible fix. RSO 7.0.26 (resourceconfigs/bobores.lua is the same in 7.1.4), bobores 2.1.2, Space Age 2.0.77.

Since bobores 2.1.0, Bob's tungsten uses the name tungsten-ore, the same as Space Age's. Bob's only gives it an autoplace on Nauvis when Space Age is not loaded (create_autoplace in bobores/prototypes/tungsten-ore.lua). In RSO, checkOre() in bobores.lua asks only whether an entity named tungsten-ore has an autoplace. With Space Age it passes on Space Age's own tungsten, whose autoplace is for Vulcanus, so line 120 adds tungsten-ore to the Nauvis table.

The smallest change is to follow Bob's rule on line 120:

if checkOre("tungsten-ore") and not script.active_mods["space-age"] then

I tried it with Space Age on a new map (seed 140140, all settings at their defaults), counting every resource entity in the 49 by 49 chunks around the origin of each planet. With Bob's alone, with Bob's and Angel's, and with Bob's, Angel's and MadClown's, tungsten-ore on Nauvis went from 420, 986 and 847 to none. Vulcanus, Gleba, Fulgora and Aquilo had the same counts as without the change. The other Nauvis ores shift, since each region rolls from a table with one entry fewer, but none of them went missing. Without Space Age the line behaves as before.

I haven't tried it with SpaceAgeWithoutSpace, which puts tungsten on Nauvis on purpose and requires Space Age. From the source, its entry is set before fillBoboresConfig() runs, and at the moment Bob's entry replaces it. With the guard, that mod's own entry should stay.

One more result from the same test, which makes the extra Nauvis entry more than an extra ore. In a modpack with Bob's, Angel's, MadClown's and Space Age (RSO 7.0.26, seed 140140, default settings), I counted every resource entity in the 97 by 97 chunks around the Nauvis origin:

• without RSO: clowns-ore1 19,451, tungsten-ore none
• with RSO as it is: clowns-ore1 none, tungsten-ore 4,491
• with RSO and the guard on bobores.lua line 120: clowns-ore1 641, tungsten-ore none

So with tungsten-ore in the Nauvis table, one of MadClown's ores is not placed at all on that seed. On seed 307307 it is placed with RSO as it is (428), so it depends on the seed. clowns-ore1 has the smallest allotment in clownsores.lua (10), so I guess it loses the region rolls that the tungsten-ore entry now takes, but I haven't traced that in the code. The guard fixes both.

I will try to take a look this week - that allotment of 10 sounds very small. From what I recall gold in bobs has one of the very low ones and it was around 40. That already makes it very hard to find sometimes so 10 will make it extremely rare.

It is possible that clowns-ore1 missing or not have nothing to do with the guard, but only a result of the rarity. I did not re-run with more chunks, as the tungsten-ore is the issue I was really looking at.
I appreciate you taking a look when you have the time.