Messages

This isn't the sub-forum for mod requests.  You want to be posting requests here.

This sub-forum is for modders to get help with making mods.

You're doing good work keeping knowledge alive. 

If this is now fixed, this should probably be unsticked and locked.

Good luck to future modders, RimWorld is a fun game and was fun to mod but I've moved on to new and exciting^* things.

* Depending on your definition

I'm not really modding RimWorld anymore and don't plan on re-uploading this.  The code was written in FreeBasic as a proof of concept (originally) but I never ported it over to C# (actually, I did and people in Discord have seen it and have copies).  In any event, this can be considered dead.

As I am no longer modding RimWorld, I am now opening these mods to anyone who wants to update them.  Feel free to update and upload them, I only ask to be given credit for the original implementation.

fyi, while RawCode figured out the 32-bit detours and the basic methodology behind the process, the code provided is from CCL.  I know this because I'm the one who figured out the required changes for 64-bit platforms further, the code and comments in the code you provide is the code and comments I wrote for CCL.  They are free to use but CCL should be credited for the code you have taken as per it's terms of use and license.

For those who are interested in the original code taken from CCL, you can also see CCLs full github code base here.

Remember, it's better to learn than copy-pasta and always give credit where due, not just to a hand-picked few.

Probably because I ask modders in the modding Slack/Discord.  They're the ones who will discover the errors in a library for modders and mods since the errors would only be visible or detectable by modders using CCL in their mods.    Without any mods using CCL how would one know if there was a bug in it? 

That being said, CCL has example mods that come with the modders release which are used to perform basic testing and I was working on dealing with the issues revealed by those.  However, I still got zero feedback from modders from the first pre-release I put out more than two months ago.

At this point it seems that I was only doing this for myself and the small handful of people who wanted it for the tweaks.

fyi, I had started a mod which would allow for more complex interactions with prisoners but there have been core code changes which made things like doors virtually impossible without massive detours (trust me, I had to do it).  Prisoners don't "see" beyond the room they are in, they won't search beyond the room they are in and they can't access anything that isn't in the same room they are in, regardless of whether both rooms are prison cells and there is a proper door between them.  (By "proper" I mean one that is an actual portal between two regions assigned different room IDs).

Take a look at where I was with this mod and you'll see that just having a door for them to use is a monumental task now due to how the core code has changed.

Anyway, just to get doors to work took several detours in several low level systems which are not even visible to the player (ie, regions, region manager, (regions are not rooms, rooms are made up of regions), etc) as well as the detours to the player visible systems (needs, rooms, etc).

Unfortunately, making prisoners more than they are in the vanilla game has become a lot more work and thus my P&S mod is on hold until the game comes out of alpha.

Mod was abandoned ?

No, be sure to learn how to read one of these days:

That being said, I doubt I will have time to update this mod until A16 at the soonest, more likely not until the game comes out of alpha so that I don't have to keep updating several large mods.

Comparing multiplayer to z levels is like comparing intelligent people to people who keep asking for multiplayer and z levels "cuz sum othur gaem haz dem".  They are completely different and unrelated.  As to the specific challenges involved with either:  Use the bloody forum search feature.  This has been discussed to death dozens of times.

IDEA:  Use the forum search function (this has been asked many times before)

What is happening is infinite recursion which is causing a stack overflow.  You can't detour a method then call the base method because you've detoured the base method and therefore you are actually calling your detour.

Regardless of what has changed between A15 and A16 I have had a lack of testers for the A15 release of CCL which means that things have been slow for CCL.  It basically got halted when I ran into a strange issue and the only person who did help test couldn't reproduce it.

Anyway, CCL will end up jumping straight to A16 it seems but it also may go on a bit of a diet.

The original method is destroyed, it can never be run.  You need to duplicate all functionality into the method which replaces it.  This has been standard for detouring from the beginning.

Once it's defined it can't be undefined.  However, you can use certain tricks to make it inaccessible such as assigning buildings (ThingDefs) to the "None" designation category (see the AncientCrytosleep),  setting ResearchProjectDefs to have themselves as prerequisites (although, they will still be visible in the research menu), removing recipeUsers from RecipeDefs, etc.

An article on platform calling conventions and specific compiler implementations would be more useful.  I don't disagree that every programmer should have a good working knowledge of assembly (not limited to specific opcodes) for the architecture they are working on.  But both this and RawCode's post are rather offtopic.