Beefy Kasplant

Probably best to only work in areas that aren't accessible if your game is online already. You'd most likely already have natural ways to block off players, so just work behind those natural borders and when the new content is finished, edit the maps to make it accessible. (Assuming your world doesn't just end randomly)

Got some feedback, apparently it was too orange? Pah!

Please give feedback:

Ahh, this is nostalgic! What will you be doing? Do you have any concept art? Maps? Plans?

Cool stuff! Hopefully this will be added in the engine soon.

Nope.

Yeah you can have an event that runs on level up. Just add a 'play sound' command

Available in PDF format here: https://kasplant.itch.io/kash-shop-private-repo The Issue How forks currently work with GitHub, when you fork a public repository, you cannot make your fork private. Why is this an issue? Well, when you create a fork from the Intersect repository, the entire code to your game is made public. Not only is this of course a security risk, but any systems and code unique to your game is now available for others to obtain. There Is A Solution! There is no need to worry! There is a work around for this problem! With a few simple steps you can protect your code. This tutorial will walk you through making a making a private fork of Intersect, but still allow you to pull code changes from the Intersect main repository to stay up to date. Getting Started First, we need to do a little setup work. Open Visual Studio as Administrator Open NuGet Package Manager Console Set directory of where you want your project files on your computer. Example: Create A Bare Clone Now that we are looking in the right place, lets setup our private fork. First lets setup a bare clone. This will be deleted later. You should now see a folder named “Intersect-Engine.git” in the directory. Create A Private Repository Now create a private repository through GitHub. This will be where your code will be stored. Log into GitHub Under the “Repositories” tab. Click the green “New” button Set the repository name to the name of your game and mark it as public. Then press the green “Create Repository” button at the bottom. Connect Temporary Clone with Repository This step is where most of the magic happens. We are going to push our clone into our new private repository so GitHub will treat our new private repository as a clone. Back in Visual Studio, move into our clone folder Now push the clone into our new repository Format: git push –mirror https://github.com/<your_username>/<repo_name>.git If you look at your repository on GitHub. You should now see all the Intersect Engine source code in your new private repository. Remove Temporary Repository As mentioned earlier, it is now time to delete the bare clone as it has served its purpose. In Visual Studio, navigate back a folder Delete temporary clone. Type “A” and press the ENTER key. Copying Repository to Local Now its time to pull our source code to our machine. Format: git clone https://github.com/<your_username>/<repo_name>.git You should now see your repository copied into your directory. Preparing for Future Updates Since Intersect is still in development. We want to stay up to date and pull all future changes to the engine. To do this, we have to tell git where to pull from. Open project solution of our new repository. (.sln file) Open NuGet Package Manager Console Create connection to main Intersect Repository Even though we can not push back to the main Intersect repository, lets just disable it anyways. Double check our remotes. Should see something similar, but with your information for the bottom two. Do initializing fetch to the main Intersect repository You did it! You now have a private fork! How To Pull Future Updates Since Intersect is in development, pulling changes and staying up to date is important. Here are the steps to pulling changes into your project. Open the Team Explorer window Press the “Branches” button Make sure you are on the right branch you want to pull changes into. In this case we will stay on the Master (Stable) branch. (Highlighted branch, double click to switch) You will see in your remotes folder; you have two other folders. “origin” is your GitHub repository connection/branches “mainstream” is the GitHub main Intersect repository connection/branches Right click the branch name and select “Fetch” Rick click the branch name again and select “Merge From…” In the “Merge from branch:” select “mainstream/master” in this case since we want to pull changes from master branch in the main Intersect repository. NOTE: Pay attention to the “Commit changes after merging” check box. It is up to you and your current development if you wish to commit not only the changes you just pulled from master, but any changes you may currently have in your solution. Your branch is now up to date with the Intersect main repository! Conclusion Thank you for following along with this tutorial. In this tutorial you have created a private repository/fork of Intersect Engine GitHub source and established connections back to the main repository. It also explained how to pull new changes into your project to stay up to date with the development of the Intersect Engine. Your source code is now protected from unwanted viewing eyes and to keep your development private. Support If you have questions, join our Kash Shop Support discord Our Itch.io Store We are constantly working on new patches and source code updates for Intersect. Check out our store at https://kasplant.itch.io

People! If you push your changes your changes are publicly available. So all your custom code is too! See here how to avoid that: https://kasplant.itch.io/kash-shop-private-repo

FLASH SALE: Item Stack Limits Patch now on sale for 50% OFF!

FLASH SALE: Item Stack Limits Patch now on sale for 50% OFF!

Patches are guaranteed to work on a vanilla Intersect with the version numbers below. All Kash Shop patches are guaranteed to work together unless otherwise stated. Get it here! Built for: Intersect 0.6.1.253 and Intersect 0.6.2.412 Updated once a week to work with the Intersect STABLE branch (Stable branch at the time of creating this patch is 0.6.1.253) Support guaranteed up until the first version of Intersect STABLE 0.6.3 (Guarantee might extend based on the popularity of the patch.) Of course we offer support if you have problems installing the patch! Just reply to this topic! Disclaimer: The patch might work on later versions of Intersect, but be careful with updating when you are using Kash Shop patches. The patch is only guaranteed to work on the version the patch was built for. Patch description: Stops players from being able to open two instances of your game on one pc. 1. Apply patch 2. Change "YourGameName" to your game name or whatever you want 3. Compile NOTE: AS ALWAYS, MAKE A BACKUP BEFORE ADDING ANY PATCHES

Patches are guaranteed to work on a vanilla Intersect with the version numbers below. All Kash Shop patches are guaranteed to work together unless otherwise stated. Get it here! Built for: Intersect 0.6.1.253 and Intersect 0.6.2.412 Updated once a week to work with the Intersect STABLE branch (Stable branch at the time of creating this patch is 0.6.1.253) Support guaranteed up until the first version of Intersect STABLE 0.6.3 (Guarantee might extend based on the popularity of the patch.) Of course we offer support if you have problems installing the patch! Just reply to this topic! Disclaimer: The patch might work on later versions of Intersect, but be careful with updating when you are using Kash Shop patches. The patch is only guaranteed to work on the version the patch was built for. Patch description: Adds an argument which can be set in game launchers like Steam. This stops the user from launching the game outside of the game launcher and effectively makes it only possible to launch one instance of the game on a PC. If you have no clue what this patch is about, you probably don't need it (yet). NOTE: AS ALWAYS, MAKE A BACKUP BEFORE ADDING ANY PATCHES

The mod was made to stop people from carrying infinite numbers of any stackable item, but not to stop people from having more than X of an item in their inventory. Think of magazine sizes for survival games or stack sizes for different crafting materials. At the moment the patch does not include any hard item limits, but I will propose it as an add-on to the system! Thanks for the feedback

There is a known bug that will be fixed: If you don't set any map type, the client will crash when interacting with NPC's. Make sure you set the map type in every map until then!

Patches are guaranteed to work on a vanilla Intersect with the version numbers below. All Kash Shop patches are guaranteed to work together unless otherwise stated. Get it here! Built for: Intersect 0.6.1.253 and Intersect 0.6.2.412 Updated once a week to work with the Intersect STABLE branch (Stable branch at the time of creating this patch is 0.6.1.253) Support guaranteed up until the first version of Intersect STABLE 0.6.3 (Guarantee might extend based on the popularity of the patch.) Of course we offer support if you have problems installing the patch! Just reply to this topic! Disclaimer: The patch might work on later versions of Intersect, but be careful with updating when you are using Kash Shop patches. The patch is only guaranteed to work on the version the patch was built for. Patch description: Stackable items can now have a max value! In the item editor is a new box in which you can state the maximum amount of that item can stack up in one inventory slot. Existing stackable items will have an automatic limit of 99. Currency is unaffected Patch features: - Set max stack size for an item - When an item stack exceeds the max size, it will create a new stack in the inventory - Taking and giving items automatically takes or give from multiple stacks if needed NOTE: AS ALWAYS, MAKE A BACKUP BEFORE ADDING ANY PATCHES

Pretty sure this means that you made the playerbox 1920x1080 big, so anywhere you try to click, the game will think you're clicking the playerbox and not the screen

Could you post the json? Also, if you follow the advice in that topic, you basically made a big invisible wall that you can't click through. So don't follow that advice. If you really want to separate the two you'd need to edit the source files and split the vitals and give them their own window

I think Gibier is saying the mod is working with and without the other mod. Have you managed to get the mod working on your version?

Fixed an issue where NPC's would all end up in the top left corner. The updated patch and instructions to update if the patch was already applied can be found when re-downloading the patch.

What's the issue exactly and your version number? Have you tried it with the reject command?

Good to see it works! Will pass on the bug report. Thanks!

If it doesn't work for your version we will fix it up for you

How do you want it to explode? Its possible to do this with events to a certain extent

Patches are guaranteed to work on a vanilla Intersect with the version numbers below. All Kash Shop patches are guaranteed to work together unless otherwise stated. Get it here! Built for: Intersect 0.6.1.253 Updated once a week to work with the Intersect STABLE branch (Stable branch at the time of creating this patch is 0.6.1.253) Support guaranteed up until the first version of Intersect STABLE 0.6.3 (Guarantee might extend based on the popularity of the patch.) Of course we offer support if you have problems installing the patch! Just reply to this topic! Disclaimer: The patch might work on later versions of Intersect, but be careful with updating when you are using Kash Shop patches. The patch is only guaranteed to work on the version the patch was built for. Patch description: Items can be assigned "Loss Prevention" which protects the keeper/wearer from losing items on death, but is destroyed after having died and "used" it. Patch features: - Item of Loss like in TIBIA - Prevent the loss of items upon death - Only activates when equipped if set to an 'equipment' type item - Activates when in the inventory when set to any other type of item NOTE: AS ALWAYS, MAKE A BACKUP BEFORE ADDING ANY PATCHES