Project

Profile

Help

HostedRedmine.com has moved to the Planio platform. All logins and passwords remained the same. All users will be able to login and use Redmine just as before. Read more...

Feature #743646

Scenarios should be able to have their own luadata.txt, maybe also parser.lua

Added by Marko Lindqvist over 4 years ago. Updated 7 months ago.

Status:
Closed
Priority:
Normal
Category:
General
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)

Description

Currently parser.lua & luadata.txt work at ruleset level. That's not ideal considering that their most natural use would be scenarios for existing rulesets.


Subtasks

Feature #820980: Scenario option to prevent loading ruleset luadata.txtClosedMarko Lindqvist

Actions
Feature #822120: Scenario to load luadata file of its ownClosedMarko Lindqvist

Actions

Related issues

Blocks Freeciv - Task #673656: S3_1 datafile format freeze (d3f)Closed

<a title="Actions" class="icon-only icon-actions js-contextmenu" href="#">Actions</a>

History

#1 Updated by Marko Lindqvist almost 4 years ago

  • Blocks Task #673656: S3_1 datafile format freeze (d3f) added

#2 Updated by Marko Lindqvist 9 months ago

The more important part, scenario specific luadata.txt, has been handled already. Parser.lua part has not been changed.

We currently can have ruleset to define parser.lua, for which there can be scenario specific data in luadata.txt. Is that already good enough for 3.1?

#3 Updated by Marko Lindqvist 7 months ago

  • Category set to General
  • Status changed from New to Closed
  • Assignee set to Marko Lindqvist
  • Sprint/Milestone set to 3.1.0

Marko Lindqvist wrote:

We currently can have ruleset to define parser.lua, for which there can be scenario specific data in luadata.txt.

That's the natural setup (if you would be scripting parser.lua, you can as well script functionality to script.lua without use of luadata.txt)

Also available in: Atom PDF