Mcadams

Spritesheets and tilesets are dynamic, you can make them basically any size you want, just know for spritesheets they'll be split vertically and horizontally 4 ways, you make sure your length/width is a factor of 4

You're gonna want to make an event to serve as the npc. Then add a command and under "dialogue" do "shows options"

When mapping the top parts of trees, use the "Fringe" and/or "Fringe2" layers to make those tiles able to be walked under.

You can set player spawn points for each class using the Class Editors.

Updated the main post a bit and fixed some of the missing gifs. Also, the marker animations are now free to use, uploaded them to an imgur album for those interested to download.

ass

the

Ended up finishing all the faction sets. Need to work on some of the colors but pretty happy with how most of the shapes turned out.

if you dont vote for marsh you are incorrect

Yeah I tend to make 2h weapons comically big sometimes, I made them a bit smaller, looks better I think.

i had no internet for like an hour so i made another set, 3 tiers of chest armor and 2h weapons

made some early game/mid game/end game armor for fun, and worked some more on the village interior tileset

Yes, you can edit the xml files to add more slots and change the order in which paperdolls render.

Just make a variable that determines what faction you are and then make a Quest Start Requirement for the faction-only quests be that you're apart of that faction

Yes, just delete the 5th page (Completed) of the marker event. Once you turn in the quest it will go back to the CanStart animation.

I believe that event spells can be tied to players only and are uncastable by NPCs, I've tried the same thing before.

On "Is" set it to "On Task", and set the "Task" to the first step in the quest (which is gather supplies.) This is so that the event knows you're in the middle of doing the quest, but you're not on the last step. By "First Task" I mean the first of the two tasks in the quest, which is to gather supplies. I edited the post to make that part clearer.

I just took the screenshots and made this guide today in Beta 4.5.

Early Christmas present.

Updated November 1st, 2023 This guide assumes you know how quests work in Intersect. If you don't, check out EVOLV's step-by-step quest guide. I. Animations 1. You'll need three different animations to show quest progress: - To show that there is a quest available - To show that there is a quest in progress - To show that there is a completed quest to turn in You can use these animations that I've created. If you're going to make your own, make sure that there is suitable offset provided in the graphic, so that the animation appears above the event. 2. Once you have the three .pngs in your animation folder, open up the Intersect Editor and add them as three separate animations. Follow the image below if you're unfamiliar with how to do so. Repeat this process until you have three separate animations. II. Quest 1. For this example quest, we're only going to have two steps. The first step will be to interact with a nearby event, and the second step will be to return to the quest giver to complete the quest. I made these both event driven tasks in the quest editor. You can include any amount of tasks in your quest, as long as you have all of the stuff you do before you turn in the quest, and then a task to go back and turn the quest in. III. Quest Giver Event 1. For the quest giver event, we're going to utilize two key features: pages and spawn/execution conditions. Place an event on the map where you want the quest giver to be. 2. In the event editor, section 1 shows your options for pages. 2 will show what page you have selected and what pages are available, and 3 is where you edit spawn conditions for your event. 3. Go to Entity Options and double click the empty gray box to select the sprite or tileset piece for your event. I chose JC's sprite for mine. Make sure the Animation right below is set to None. 4. Go back to the top where your page options are and press "Copy Page". 5. Create three new pages. 6. Go to each page, and press "Paste Page" on each page. This will leave you with four pages, each with your selected sprite/tileset piece with no animation. IV. Page 1, the available quest page 1. Each page acts as a different state of the event. This first page will be the quest giver NPC before you start the quest, and the quest is available to be started. 2. Set the Animation to the yellow exclamation point. This signifies that this NPC has a quest. 3. Click on the Spawn/Execution Commands tab and create a new list. 4. Add a condition to the list that the player Can Start Quest and select your quest. This will cause this page to activate when the player meets the requirements to start the quest. 5. Create the dialog and quest start commands for your quest. Mine simply gives two options; that the player is interested in a quest, or nothing. Be sure to include the Start Quest command. IV. Page 2, the quest-in-progress page 1. Go to page 2 of the event. 2. Set the Animation to the grey question mark. This symbolizes that the quest has been started, but it's still in progress. 3. Click on the Spawn/Execution Commands tab and create a new list. 4. Add a condition to the list for Quest in Progress, select your quest, and then select Before task, and pick the last task of the quest. This will make it so as long as you still have stuff to do in the quest, the question mark will stay gray. 5. You can also add a different set of commands to this page. In this state, the quest has been started, but not completed. You could have, for example, the NPC explain what the player has to do, or ask how their progress is going, etc. Separating the event into pages allows for more dynamic and realistic conversation, since the NPC can do different things based on it's current state. V. Page 3, the completed tasks page 1. Go to page 3 of the event. 2. Set the Animation to the yellow question mark. This symbolizes that all steps of the quest have been completed and it is ready to be turned in. 3. Click on the Spawn/Execution Commands tab and create a new list. 4. Add a condition to the list for Quest in Progress, select your quest, and then select On Task, and then select the last task of your quest (which should be to turn in the quest/return to the NPC who gave you the quest). 5. Go to the Commands section and setup your quest turnin dialogue. Here, I just have the NPC congratulate the player on doing well, and then add Complete Task command to complete the last task of the quest, which completes the quest entirely. VI. Page 4, the post-quest page Note: if you want the quest to be repeatable, you can just delete this page and skip this step. 1. Go to page 4 of the event. 2. Keep the Animation set at none. This will tell the player that there isn't a quest here for them anymore, since they already completed it. 3. Click on the Spawn/Execution Commands tab and create a new list. 4. Add a condition to the list for Quest Completed and select your quest. This will cause this page to activate only when the quest has been completed. 5. Go to Commands and setup dialogue for the NPC's post-quest completion state. You can have the NPC do whatever, but also be under the assumption that they have done this quest for them. They can be nicer to the player, thankful, give them access to a shop they previously didn't have access to — whatever. If you followed all these steps correctly, your event should work something like this!

Very carefully.

You need to use the same autotile on the same layer and it should automatically continue the autotile for you.

Holy necro, Batman!