HentHighSchool Development Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

collapse
* Recent Posts
More occupant list symbols? by Dragonblood
[Today at 03:21:01 am]


Re: Public source code by kite80
[Today at 02:58:51 am]


Re: Gameplay and design discussion by kite80
[Today at 02:52:50 am]


Re: Public source code by disman
[Yesterday at 03:37:28 pm]


Re: Gameplay and design discussion - Girls' Misc Equip slot by DougTheC
[Yesterday at 03:23:39 pm]


Pages: [1]   Go Down

Author Topic: Quick Question on auto loading  (Read 3985 times)

JilboDaggins

  • Newbie
  • *
  • Offline Offline
  • Posts: 3
    • View Profile
Quick Question on auto loading
« on: January 29, 2018, 12:38:13 am »

I've played with the VEE and have some pretty good results so far.  The main issue is that I'm saving what I create as new ve.xml files so I can easily share later.

I have to use the debugger to load them each time I start or load a game.  Is there a way around this?  If so I've not found it on the forums yet.
Logged

barteke22

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 884
    • View Profile
Re: Quick Question on auto loading
« Reply #1 on: January 29, 2018, 02:24:39 am »

When you make a new event or edit one before starting a new game, there's no need to do anything (until you edit it again). So long as the event is saved in the right place and with right format (if you can run it ingame - it is), it's loaded in like any other game event.

If you edit/create an event and want to add it to an existing save, so long as it doesn't break anything (like states of other events relaying on it - see note at bottom), all you have to do is: Debug -> Reload Events -> Add All Events -> Reload. If you then Save Game, you won't have to reload it until you edit it again.

If you edit frequently you just have to repeat that (except for saving maybe - I only tend to save game when I'm happy with the results of my edits). It's just like 2s once you get used to it.



Breaking states is usually when 'Reload Events' reloads variables of one event (the one you edited) when you have another event that expects those variables to be unchanged.
Example: Event5.ve.xml expects that when you scheduled it, variable reference to Integer in Event1.ve.xml is >= 5, but 'Reload Events' reset it back to the default 0.
- This can be fixed by using the ingame Event Debugger to set the states to what they should be at that point.
- Although in the (far?) future, events might keep their states on 'reload' according to Mantis.
« Last Edit: January 29, 2018, 02:30:09 am by barteke22 »
Logged

JilboDaggins

  • Newbie
  • *
  • Offline Offline
  • Posts: 3
    • View Profile
Re: Quick Question on auto loading
« Reply #2 on: January 29, 2018, 02:32:25 am »

Thanks for the quick reply.

Mostly I'm working on simple things right now.  Random encounters, etc.  Building skills with the VEE.  I suppose I was thrown off by the option that scans the .xml and suggests ones to load.

Is it encouraged to make my work available?
Logged

barteke22

  • Hero Member
  • *****
  • Offline Offline
  • Posts: 884
    • View Profile
Re: Quick Question on auto loading
« Reply #3 on: January 29, 2018, 03:05:35 am »

The scan will show you any file that has been edited since the start of the game and has not been reloaded in the current save.

A small problem (saved game only) might be when you decide that you no longer want an event. Deleting the file isn't enough, as you can't reload a file that doesn't exist.
If you really need to disable the event in that save, either:
1. Disconnect the Try-phase (so it never triggers), Save event, then reload it, Save game. Then you can delete the file.
OR
2. Delete file and use ingame Debugger to disconnect Try-phase, Save game. 1 is usually quicker, but 2 can be good in case you forget and delete it.



No need to take this to heart if you're just getting started, though once you get better, this is nice practice:

- Try to keep your Try-phases either simple, or have the most likely 'fails' first - so if it's gonna fail, it does it quickly. Helps reduce delays.

- Big events (with many branches for variation) are usually better than many small separate events. There's less Try-phases to test (less delay before an event starts). Obviously only if you feel it makes sense.
Example: If you have 5 similar events in the same location, it should be easy to put their contents into 1 big one that simply picks the right branch inside.
Logic inside the Execute is preferred over Try-phase, as it only ever triggers if the Try-phase passes - so less delays while walking around, etc.



As for whether you should publish your stuff, well, that's entirely up to you. If you want to share something - share it, if not - don't :P
If you do, people might give you tips/new ideas on how to do things/improve your stuff etc.

Monybarx

  • Newbie
  • *
  • Offline Offline
  • Posts: 4
    • View Profile
Re: Quick Question on auto loading
« Reply #4 on: September 20, 2018, 06:38:30 am »

Because of this, I have gained a lot more knowledge than I ever received.
Logged
Pages: [1]   Go Up
 


anything
SimplePortal 2.3.3 © 2008-2010, SimplePortal