Page du magasin
RimWorld
Tous Discussions Captures d'écran Créations de fans Diffusions Vidéos Workshop Actualités Guides Évaluations
RimWorld >  Workshop > Workshop de Proxyer
141 évaluations
Deep Scanner Patch
Description Discussions1 Commentaires53 Notes de changement
   
Récompenser
Ajouter aux favoris
Favoris
Retirer des favoris
Mod, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6
Taille du fichier
Publié le
Mis à jour le
902.047 KB
2 mai 2020 à 15h39
23 aout à 13h16
17 notes de changement ( voir )
Créé par
Proxyer
Hors ligne
Voir les 1725 collections créées par Proxyer et d'autres personnes (certaines peuvent être cachées)
16,740 Visites uniques
5,315 Abonné(e)s
528 Favoris actuels

S'abonner pour télécharger
Deep Scanner Patch

Dans 1 collection faite par Proxyer
Proxyer's RimWorld Japanese Mods
235 objets
Description
Description :
Expand the range size of resources that can be scanned by the ground-penetrating scanner. Underground resources will be discovered more extensively.

This mod does not change the vanilla ore discovery rate. Only the size of the vein when it was discovered by the ground-penetrating scanner is changed.


If you want to increase the discovery probability as well as the ore range, you may use this my friend mod.

Mod name: 富矿（Bonanza） Mod Author: 岸岛柔乃子
https://steamcommunity.com/sharedfiles/filedetails/?id=2082091494


Mod list order :
This mod is a patch mod, so always place it at the bottom of the mod list.


Existing save data :
Since this mod only add patch operations, it can be safely installed in existing save data. You can also safely remove the mod at any time.


Mod Compatibility :
Compatibility with mods that have mining resources that can extend the scan range.

A RimWorld of Magic : Arcalleum

Titanium+ (continued) : Titanium

Rimlaser : Crystal

Expanded Materials - Metals : Fossil, Coal, Iron, Lead, Tin, Copper, Tungsten, Chromium, Titanium, Lithium, Germanium.

[LITE]Expanded Materials - Metals : Fossil, Coal, Iron, Lead, Tin, Copper

GravTech : Gravitonium

Glitter Tech : Titanium, Alpha-Poly, Beta-Poly


　
Discussions populaires Tout voir (1)
0
15 mars 2024 à 20h14
BuckUp Link
Proxyer
53 commentaires
< >
Proxyer  [créateur] 23 aout à 13h20 
Update : 24 Aug, 2025
v1.6.3
- Added compatibility patch for Glitter Tech (Titanium, Alpha-Poly, Beta-Poly).
Proxyer  [créateur] 23 aout à 11h53 
Hello Askesis. I'll check it.
Askesis 23 aout à 10h16 
Could you consider adding support for Glitter Tech please? :-)
https://steamcommunity.com/sharedfiles/filedetails/?id=2558099206
Proxyer  [créateur] 13 aout à 14h17 
Update : 14 Aug, 2025
v1.6.2
- Hot fixed : GravTech patch.
Proxyer  [créateur] 13 aout à 13h35 
Update : 14 Aug, 2025
v1.6.1
A patch that increases deep lumpsize range of GravTech Gravbitonium has been added to 1.6.
- The following mods (materials) are now compatible with 1.6:
Titanium+ (continued)
Rimlaser
Expanded Materials - Metals
[LITE]Expanded Materials - Metals
Proxyer  [créateur] 9 juin à 21h17 
Update : 10 Jun, 2025
v1.6.0
- Added 1.6 tag preliminarily for new DLC.
Proxyer  [créateur] 30 mai à 6h50 
Good. If you understand xml patching, you can easily get the results you want. If you do it wrong, you'll get a black screen of death. :lunar2019laughingpig:
Nicoman 30 mai à 5h12 
Yeah. I'm a muppet. Turned out I was the culprit. Whack me. I did a couple of changes on this mod for my own personal use. I messed up an XML line in the process. Of course everything works as intended now.
Proxyer  [créateur] 30 mai à 4h45 
Hello Nicoman.
Many resource mining mods (e.g. drill mods) may not be compatible because they re-modify parts changed by this patch in DLLs.

If you have installed those mods, patches may not work properly. Also, if there are multiple patches that change the same element, the patch of the mod placed higher in the mod list will be processed first, and the patch of the mod placed lower will be ignored. This is the specification of the RimWorld game client.
Nicoman 30 mai à 4h34 
Unfortunately, adding the mod to my heavy modded game throws all kinds of errors. A fast read through the error log did not reveal a possible solution. Maybe in 2 weeks I got the time to look deeper into the problem. Just wanted to give a heads up.